I have the linksys ea8500 hardware with master snapshot, my build. It is working great. But since last sysupgrade, the wifi works great but I can't use ethernet wired, seems to be connected but I can't open LuCi or ssh. When I clear my browser with ctrl+shift + R, I see for a sec on the left screen '' LuCi-lua configuration'' as we see before the openwrt loggin page appears but nothing happens, only my browser with no connection, idea?
I tried many things, reseted my network setup on my pc, reset router, etc.
I tried my second router and this one is working with wired...
What version of OpenWrt were you using previously and what did you upgrade to? It seems likely that you had the "keep settings" option selected during the upgrade, correct?
If you were on OpenWrt 19.07.x and then upgraded to 21.02.x, you will need to reset your router to defaults and start fresh with the configuration. This is because of major changes to the way that the ethernet hardware is addressed (swconfig > DSA).
21.02.2 is available for your router. Unless there is a specific reason to use master/snapshots, you will usually find that the stable releases are more reliable.
Try using failsafe mode to see if the ethernet ports work as expected. If they do, go ahead and reset to defaults and configure again.
Fair enough. It might be worth trying the standard stable build to see if the problem exists there. In the default config, if the standard stable build does exhibit the issue, there is a bug. If the problem is only present on your build, it could be one of three things: an issue with your specific build, a problem with the current snapshot, or a configuration error.
or... there could be a hardware issue (bad port, bad cable, etc.)
I'm not pointing blame at your build, just identifying quick ways to determine where the error may be so you can concentrate error's in the right place.
Have you updated your .config for fw4? I recently lost all connectivity (wireless and wired) with my "own" build and make distclean plus redoing the .config from a minimal version i keep around got it back.
Of course, the fact that my toolchain was kernel 5.15, I was building kmods for 5.10.100 while using a 5.10.9x on the device and I've been doing builds with dsa and swconfig might have also had something to do with it but check the packages in your .config regarding iptables/nftables if you have not done so recently.
(Also fw4/nftables does not use /etc/firewall.user)
I did what I saw on your link, set to 4, the gmac2.
refresh my .config too, sysupgraded from ssh and for the fisrt time ever, I lost completely my hardware... no more lights or boot. Look at the end, first time I see that kind of error
But you can load a firmware (either the OEM or an openwrt "factory" image) and get your wifi back correct?
Regardless forget trying to build/load an NSS build and just focus on loading a stable build as @psherman suggested and trouble shoot from there.
Out of curiosity, did you click solution for my post by accident or did a fresh .confing work for you? No worries either but it will help those trying to help you understand what you have tried.
Last, try not to worry. I use an ipq8064 based system and they seem pretty robust to flashing errors - just be careful to follow the instructions for the ea8500.
About loading factory image, I did not try cause if I dont keep my setting and can not use wired connection, It will be impossible to load some settings and wifi.
Also, it seems that everytime I load something on the second partition, it is not available.
I tried another openwrt image, OEM Linksys and openwrt factory, no.one loads
If your wired ethernet might not be working, be sure to have a serial connection ready for debug. Obviously if it is a full hardware failure, it may not matter much (since you'd probably be looking at buying a new device).
Remember -- the default OpenWrt config has wifi disabled (which you probably already know, but a useful reminder), so if you think there is a driver bug with ethernet or some other issue, you'll be unable to connect to the device except by serial.
At this point I think you will need to spend some time looking through the EA8500 forum threads to see if and how others have recovered from similar conditions. Presumably you have a partially functional (openwrt NSS or is it OEM?) image on one partition and the other partition isn't responding to flashing. Also I see that the EA8500 has two variants (US and Hong Kong) and that they may be different so be careful to identify what you have what other users posts are referring to device wise.
I don't have an EA8500 and this thread is marked solved, so try posting in an open active EA8500 thread for installation troubleshooting. Again, try not to worry, your more likely to make good decisions and recover the device if your calm.
but check the packages in your