ipconfig /all. Look at the DHCP Server line. If the IP address does not match your primary router (e.g. shows 192.168.0.1 instead of 192.168.1.1), a rogue device is responding faster than your router!
2) In Wireshark, apply display filter: bootp.option.type == 53. Send a release/renew.
3) Inspect the Source MAC address of the rogue DHCP Offer packet and look it up on your switch port table or Wi-Fi client list to disconnect it physically.
4) On managed switches, enable DHCP Snooping and designate only your primary router's port as Trusted.
How Rogue DHCP Servers Cause Network Chaos
In standard DHCP (RFC 2131), client devices broadcast a DHCPDISCOVER packet to destination 255.255.255.255. Whichever DHCP server responds first with a DHCPOFFER wins the negotiation (a classic race condition). If an old router plugged into the switch has an active DHCP server, half your devices will receive the rogue gateway, losing all WAN internet routing.
Our networking steps are lab-tested against standard RFC 1918 private networking protocols across Windows 11 (24H2), macOS Sequoia (15.1), iOS 18, and Android 15. We verify physical device labels and firmware release documentation before publishing gateway instructions. Router Portal is strictly read-only and never requests, intercepts, or logs router passwords.