DHCP giving old subnet mask
-
6 weeks ago we had to expand a subnet from /26 to /25 to accommodate unexpected growth. Last night we started having clients randomly renew with the /26 mask instead of /25 which is taking them offline. Where can I fix whatever variable is still stuck? Right now I have 2 out of 47 devices not getting the right mask.
-
Did you also change the available range? That's right below the subnet mask.
-
@jknott yes sir I definitely did because I needed the extra addresses. I set all my devices to fixed dhcp and leave a scope for anything added without my knowledge. Originally the subnet was 10.2.0.0/26 and a scope between about 50-59 so I modified the range to 70-80 and started doing fixed addresses in the 50s. I don't understand how it took so many weeks for it to start giving the wrong netmask and it started after a new guy unsafely rebooted the router.
-
The computers on this interface randomly switch between subnet masks. A computer that works will stop working hours later when it obtains the old netmask. Then hours later it'll suddenly come back online. Could anyone point me in the direction where I'd find corrupt settings for the netmask?
-
@centaur5
have you verified that there is only 1 dhcp-server on your network? (is it pfsense handing out the bad subnet or something else)a packetcapture when a client gets the wrong subnet would probably show a light
