DHCP IP range changes when static IPs are assigned
Posted: Wed Jan 22, 2020 9:26 pm
First, my network details:
Subnet Mask: 255.255.0.0
DHCP Range (in the configuration interface, at least): 192.168.1.2-192.168.1.128
Groups of static IPs on:
192.168.10.x
192.168.11.x
(...)
And the router's IP is 192.168.1.1.
This is done to facilitate easier-to-read network documentation as well as easier-to-remember quotas.
If I don't have any static IPs set, the DHCP range sets correctly. However, if I add static IPs, the interface still says: https://pasteboard.co/IRdVXg8.png, but the actual range is 192.168.0.2-192.168.0.128. This is also reflected in the auto-generated dnsmasq configuration file.
This wouldn't ordinarily be an issue, except that I had a strange configuration gremlin in the form of my WAN being on 192.168.0.x. That caused problems. Fortunately, since the WAN is also under my control, I was able to change it over to 10.0.0.x, which made my system functional. (though, to be fair, if that wasn't practical, I could have changed my gargoyle system instead..) I'm not sure if this is a bug or not, however, if it isn't, it isn't documented anywhere that I could find. Is there a reason that it isn't possible to change the 3rd byte of the IP range for DHCP?
Subnet Mask: 255.255.0.0
DHCP Range (in the configuration interface, at least): 192.168.1.2-192.168.1.128
Groups of static IPs on:
192.168.10.x
192.168.11.x
(...)
And the router's IP is 192.168.1.1.
This is done to facilitate easier-to-read network documentation as well as easier-to-remember quotas.
If I don't have any static IPs set, the DHCP range sets correctly. However, if I add static IPs, the interface still says: https://pasteboard.co/IRdVXg8.png, but the actual range is 192.168.0.2-192.168.0.128. This is also reflected in the auto-generated dnsmasq configuration file.
This wouldn't ordinarily be an issue, except that I had a strange configuration gremlin in the form of my WAN being on 192.168.0.x. That caused problems. Fortunately, since the WAN is also under my control, I was able to change it over to 10.0.0.x, which made my system functional. (though, to be fair, if that wasn't practical, I could have changed my gargoyle system instead..) I'm not sure if this is a bug or not, however, if it isn't, it isn't documented anywhere that I could find. Is there a reason that it isn't possible to change the 3rd byte of the IP range for DHCP?