Extend dynamic DHCP range on the backbone network
At the moment there is a fairly low limit on the number of DHCP clients
handled on the backbone network. The limit made sense when our backbone
network was 10.0.2.0/23, but now that it is 10.0.0.0/8 it does not.
I propose to extend the dynamic range significantly, to allow sites to
have more than around 400 clients to 4000 clients. I suspect 4000
clients would work out of the box with the new LDAP configuration, and
picked this as a good new range size. If I got it right, this patch
will implement the change.
--- debian/changelog (revisjon 75152)
+++ debian/changelog (arbeidskopi)
@@ -4,6 +4,10 @@
* Extend the dynamic DHCP range on the thin client network from 200-
253 to 20-243, to handle more thin clients without any
+ * Extend the dynamic DHCP range on the backbone network from
+ 10.0.2.100-10.0.3.242 to 10.1.0.20-10.1.15.254 (aka 10.1.0.0/20),
+ to handle more clients without any changes to the configuration.
+ This allow around 4k clients to get IP addresses out of the box.
* Fix wrong IP address for gateway GOsa object.
[ Mike Gabriel ]
--- ldap-bootstrap/dhcp.ldif (revisjon 75151)
+++ ldap-bootstrap/dhcp.ldif (arbeidskopi)
@@ -50,7 +50,7 @@
-dhcpRange: 10.0.2.100 10.0.3.242
+dhcpRange: 10.1.0.20 10.1.15.254
To make it easier to use network access lists to control such DHCP
clients, I propose to put all of them in a separate netblock
(10.1.0.0/20), where the netblock is fairly randomly choosen to be the
at the start of the next /16 after the addresses already used for
This change would allow sites like Narvik with 1400 clients to be able
to use the default backbone network setup out of the box with Squeeze.
Is /20 enough? Should we put it somewhere else in 10.0.0.0/8? Last,
perhaps? Or perhaps 10.0.16.0/20 which is the next /20 after