Device providing addresses beyond its DHCP scope
Device providing addresses beyond its DHCP scope
A rogue DHCP simply means the first responder gets to allocate the IP address to the device, leaving it unclear who actually receives the assignment when the lease ends.
I'm not used to this router, but I've noticed more of them assigning separate DHCP ranges for Wi-Fi and wired connections. The configurations are often hidden and hard to distinguish, which can make it tricky to identify. Usually, it's a rogue DHCP server.
I believe the rogue DHCP server has become even more reliable. My computer was experiencing this issue again today, so I performed a network inspection. Using AngryIP, I discovered a device running a web server on my network that I couldn't reach. It wasn't listed in the router table, and its MAC address belonged to Shenzen Trolink. I reviewed all my network equipment but couldn't identify it, so I blocked it from accessing the network. After executing /release /renew on my desktop, I was able to obtain the correct IP address. It seems the problem has been resolved.
The only device I own is a garage door opener, with no smart bulbs or plugs elsewhere. It appeared on my list of connected devices, confirming it wasn’t there. That feeling was unsettling, and my router even labeled it as a camera—adding to the unease. Since I blocked this device from my network, I haven’t experienced any problems.