expanding my ip pools
Simon Hobson
dhcp1 at thehobsons.co.uk
Wed Nov 18 19:40:56 UTC 2015
Leandro <ingrogger at gmail.com> wrote:
> My concern is that the request ip source is not included in those segments , but should be enought that new segments are declared under a shared network statement.
Correct
> Other question is , after add those lines and restart service , already granted ips will be released ?
No, existing leases will remain unaffected.
> And here is my current share network setting:
>
> shared-network Public {
> subnet 10.10.0.0 netmask 255.255.240.0 {
>
> #10.10.1.0/24
> pool {
> range 10.10.1.2 10.10.1.254;
> option broadcast-address 10.10.1.255;
> option subnet-mask 255.255.255.0;
> option routers 10.10.1.1;
> }
>
> #10.10.2.0/23
> pool {
> range 10.10.2.2 10.10.3.254;
> option broadcast-address 10.10.3.255;
> option subnet-mask 255.255.254.0;
> option routers 10.10.2.1;
> }
>
> #10.10.4.0/22
> pool {
> range 10.10.4.2 10.10.7.254;
> option broadcast-address 10.10.7.255;
> option subnet-mask 255.255.252.0;
> option routers 10.10.4.1;
> }
>
> #10.10.8.0/21
> pool {
> range 10.10.8.2 10.10.15.254;
> option broadcast-address 10.10.15.255;
> option subnet-mask 255.255.248.0;
> option routers 10.10.8.1;
> }
> }
> }
You seem to be mixing things up a bit here. Is there a specific reason for having the clients subnetted like that ?
If it's because there's a 10.10.0.0/24 in use somewhere, then really it's not right to include that in the DHCP config.
I'd suggest it's more "correct" to describe it thus :
shared-network Public {
subnet 10.10.1.0 netmask 255.255.255.0 {
pool {
range 10.10.1.2 10.10.1.254;
option routers 10.10.1.1;
}
}
subnet 10.10.2.0 netmask 255.255.254.0 {
pool {
range 10.10.2.2 10.10.3.254;
option routers 10.10.2.1;
}
}
}
and so on.
More information about the dhcp-users
mailing list