Vandergraff
Regular Contributor
In the last couple of days I have started having issues with the wired LAN ports on my RT-N66U.
Devices/switch that having been working perfectly for years are now losing connectivity.
I was running John's latest fork (which I updated to also a couple of days ago). Went back to John's earlier version, did a factory reset and then tried Merlin's latest version - but the issue doesn't change with the firmware.
Looking in Tools LAN 2 and 4 have 'Down' as their link state. Strangely devices connected to then (directly or through switches) seem to get IP addresses from the router (reported in the client network set up) but cannot get Internet connectivity. The clients are also not listed as connected clients by the router.
Clients I have tried include Blu-Ray Players, DirecTV Set Top Boxes, Ooma etc
Any ideas for other things to try - does it sound like a hardware issue with the router?
The 2 things I did around the time the issue started was force an IP change on Comcast by changing the router WAN MAC address (since changed back to default) and upgraded to John's latest fork (however issues remains there with other firmware so seems like a coincidence).
Devices/switch that having been working perfectly for years are now losing connectivity.
I was running John's latest fork (which I updated to also a couple of days ago). Went back to John's earlier version, did a factory reset and then tried Merlin's latest version - but the issue doesn't change with the firmware.
Looking in Tools LAN 2 and 4 have 'Down' as their link state. Strangely devices connected to then (directly or through switches) seem to get IP addresses from the router (reported in the client network set up) but cannot get Internet connectivity. The clients are also not listed as connected clients by the router.
Clients I have tried include Blu-Ray Players, DirecTV Set Top Boxes, Ooma etc
Any ideas for other things to try - does it sound like a hardware issue with the router?
The 2 things I did around the time the issue started was force an IP change on Comcast by changing the router WAN MAC address (since changed back to default) and upgraded to John's latest fork (however issues remains there with other firmware so seems like a coincidence).