DHCP static IPs sometimes not working
Posted: Mon Jul 02, 2018 3:08 pm
Alright, get ready. This is gonna be a weird one.
I've probably got something misconfigured, but I'll be darned if I can work out what.
My setup is as follows:
Quotas set up to regulate groups of devices such as:
192.168.10.x
192.168.11.x
etc.
Netmask is set to 255.255.0.0 to allow this to work.
Each person in my house is assigned one of these groups of addresses, and when someone gets a new device, I set it a static IP within the DHCP config page. The unfortunate part of this has always been that for some reason, the DHCP addresses that are given before the devices have static ones just don't work. They *should* be within the netmask (192.168.0.x), but from those, I can't access the internet, can't even get to 192.168.1.1 to change the IP. That's been alright, mostly. Every so often, a device would get the wrong address for some reason, and I'd have to refresh the DHCP lease.
However, recently, devices seem to be getting the .0.x addresses a lot more over the space of a few weeks, until now when it's come to where I've had to set static IPs on the devices. This isn't feasible as a long-term solution, due to the number of different access points to this network.
I'm running Gargoyle 1.9.1 on a TP-Link TL-WDR4300.
I've probably got something misconfigured, but I'll be darned if I can work out what.
My setup is as follows:
Quotas set up to regulate groups of devices such as:
192.168.10.x
192.168.11.x
etc.
Netmask is set to 255.255.0.0 to allow this to work.
Each person in my house is assigned one of these groups of addresses, and when someone gets a new device, I set it a static IP within the DHCP config page. The unfortunate part of this has always been that for some reason, the DHCP addresses that are given before the devices have static ones just don't work. They *should* be within the netmask (192.168.0.x), but from those, I can't access the internet, can't even get to 192.168.1.1 to change the IP. That's been alright, mostly. Every so often, a device would get the wrong address for some reason, and I'd have to refresh the DHCP lease.
However, recently, devices seem to be getting the .0.x addresses a lot more over the space of a few weeks, until now when it's come to where I've had to set static IPs on the devices. This isn't feasible as a long-term solution, due to the number of different access points to this network.
I'm running Gargoyle 1.9.1 on a TP-Link TL-WDR4300.