Hi,
I have been having some confusion in starting to use separate subnets and DHCP relay for client configuration.
Currently, the setup we have is basically all our hosts plugged in to a lot of daisy-chained switches in to one large LAN and the DHCP server happily spits out IPs for, well, basically one large subnet.
Now we are getting to the point where we need to start using separate subnets so I am now starting to connect systems to a separate interface on our router (happens to be SonicWall) so where before everything was on a single LAN interface (called "X0"), we will have several LAN interaces (called "X3" and "X4").
So I've got different subnets going on. The X0 is 10.1.128.0/17 and X3 is 10.1.5.0/24 (and lets ignore X4 for now). I've added the new subnet with a pool on the DHCP server and configured the router's IP Helper option to relay DHCP requests to the original DHCP server.
The problem is that existing systems when they request IP info over the new interface, they request their old IP address and the DHCP server happily send an ACK back even though they are now on the wrong subnet. The only way so far that I can get the DHCP server to not ACK the client on the old IP address / subnet is to disable the pool / range the client is in, kick dhcpd, release / renew on the client, then re-enable that range and kick dhcpd again.
This is the relevant section from my DHCP config with options like ntp servers etc omitted:
PHP Code:
# Manufacturing LAN
subnet 10.1.5.0 netmask 255.255.255.0 {
option routers 10.1.5.1;
option subnet-mask 255.255.255.0;
option broadcast-address 10.1.5.255;
default-lease-time 7200;
max-lease-time 7200;
pool {
range dynamic-bootp 10.1.5.100 10.1.5.200;
}
}
# Workstation / General LAN
subnet 10.1.128.0 netmask 255.255.128.0 {
option routers 10.1.128.1;
option subnet-mask 255.255.128.0;
option broadcast-address 10.1.255.255;
default-lease-time 7200; # 2 Hours ! STUB !
max-lease-time 7200; # 2 Hours ! STUB !
pool { # General Pool(s)
range dynamic-bootp 10.1.128.100 10.1.128.200;
range dynamic-bootp 10.1.129.100 10.1.129.200;
}
}
Is there some better way to make the DHCP server force clients comming in on the new interface on to a new IP address?
Thanks in advance,
- Dominic