Hello everyone. I've done a fair bit of searching, but cannot figure out a new behaviour I'm noticing from my GL-MT6000. I've had the device for months, but just yesterday it started to assign DHCP addresses in a very strange way. For many devices, but not all, it's assigning a 172.XXX address with a 172.XXX gateway, despite the fact that my LAN is set to 192.168.2.XXX since the day I configured the router.
I've trouble shot this with a half dozen devices by manually setting IPs, but cannot figure out why the router might be assigning zombie IP addresses.
Has anyone seen such a behaviour before? I'd rather not completely reset the device, but will do so if I can't get to the bottom of this.
First of all, it can be clarified that unless the user sets the router LAN gateway to 172.x.x.x, the router will not DHCP offer this IP.
Please check the device you are connecting to Flint 2, for example if there are other routers connected by LAN-LAN, or if there are other DHCP servers?
In addition, if the client device network cable is re-plugged, will the IP 192.168.2.x be obtained normally?
You can capture the network packets through "WireShark" on your PC and check who offer 172.x.x.x.x through DHCP.
Bruce, than you so much! i don't know why I didn't think of getting wireshark to point out the problem.
Turns out, my Ooma VOIP box is not playing nicely with my new router (for some reason) and was acting like a DHCP provider in the 172 range. Booting it from the network has restored normal behaviour.