From 43d42e6f15fb8a10bdc77555436b83ffb9178309 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Thu, 11 Jun 2015 18:01:28 +0100 Subject: [PATCH] Update docs for default -iprange --- site/ipam.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/site/ipam.md b/site/ipam.md index c2b4856f..15591a38 100644 --- a/site/ipam.md +++ b/site/ipam.md @@ -5,9 +5,11 @@ layout: default # Automatic IP Address Management -Weave can automatically assign unique IP addresses to each container -across the network. To make this work, weave must be told on startup -what range of addresses to allocate from, for example: +By default, weave automatically assigns unique IP addresses to each +container across the network. To make this work, weave must know on +startup what range of addresses to allocate from - if you don't +specify a range then it will use 10.128.0.0/9, but you can choose your +own range, for example: host1# weave launch -iprange 10.2.0.0/16 @@ -55,7 +57,7 @@ then you can run all containers in the 10.9.0.0/16 subnet, with IPAM using the lower half and leaving the upper half free for manual allocation. -The subnet parameters are written in [CIDR +The range and subnet parameters are written in [CIDR notation](http://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing) format - in this example "/24" means the first 24 bits of the address form the network address and the allocator is to allocate container