pool range utilization
Yannick CHAMPS
yannick at viti.pf
Thu Apr 30 00:06:40 UTC 2015
Hi all,
do you know why the 1st pool range (172.16.128.1 to 172.16.135.255) is
not used at all even if all pool ranges share the same configuration ?
What is the dhcpd's criteria to load balance leases upon pool ranges ?
shared-network Network-nat {
option domain-name "acme.com";
option domain-name-servers 8.8.8.8,8.8.4.4;
default-lease-time 360;
max-lease-time 360;
subnet 172.16.128.0 netmask 255.255.192.0 {
option subnet-mask 255.255.192.0;
option broadcast-address 172.16.191.255;
}
pool {
range 172.16.128.1 172.16.135.255;
range 172.16.136.1 172.16.143.255;
range 172.16.144.1 172.16.151.255;
range 172.16.152.1 172.16.159.255;
allow members of "lte_internet";
}
}
#dhcpd-pools -c /etc/dhcpd.conf -l /var/lib/dhcpd/dhcpd.leases
Ranges:
shared net name first ip last ip max cur
percent touch t+c t+c perc
Network-nat 172.16.128.1 - 172.16.135.255 2047 0
0.000 0 0 0.000
Network-nat 172.16.136.1 - 172.16.143.255 2047 9
0.440 0 9 0.440
Network-nat 172.16.144.1 - 172.16.151.255 2047 92
4.494 10 102 4.983
Network-nat 172.16.152.1 - 172.16.159.255 2047 223
10.894 3 226 11.041
--
Yannick
More information about the dhcp-users
mailing list