Thanks for the suggestion. I rolled back to 3.203 and have the same problem as before. Also I tried 3.102 and the same problem exists as well.
Interestingly, during the router’s startup sequence the modem’s LAN indicator light shows some activity but after the router boots up the light goes dark indefinitely. I may need to look into what kind of options the microuter’s ethernet controller’s driver has to see if tuning any of them will get it working, or maybe it’s a cabling issue and for that I’ll have to wait until I get some new cables delivered to debug.
I noticed there were lots of changes to the mtk_eth_soc driver from Linux 4.14 to 5.4 (and even more to 5.16) so I attempted to install plain openwrt 21.02.1 from OpenWrt Firmware Selector . Once I installed it and configured the ethernet port for WAN usage, it was able to properly detect the cable modem as a working ethernet connection and get a public IPv4 address over DHCP so this seems to indicate that the old version of the ethernet driver just had some bugs or missing capabilities. The internet is not working yet but that might just be an incomplete OpenWrt configuration issue on my part or a problem on the ISP side. I’ll see if I can get it to work correctly.
I also have applied the 3.211 fw to the AR150 and it stops detecting the eth cable also, so It looks like the AR150 is having the same 3.211 issue.
I’ve to rollback to 3.203 this weekend, since the remote mgmt is broken.
@alzhao Why is the firmware for the N300 much more buggy then for other GL iNet routers? Of all my GL iNet products, the N300 has had the most firmware issues, and has cost me more time then all my other GL iNet routers put together.
The upstream router is a Linksys AC5400. I’ve connected in AP mode the GL-AR150, but as soon as it automatically updated into the 3.211, it stop detecting the ethernet cable. It took me some time to find out that the issue was firmware related, but, as soon as I rolled back the router to the previous firmware version (3.203) it get back to work immediately.
Yes, I’ve connected the GL-AR150 in AP mode (in settings → network Mode) to extend my wifi coverage. The router have been working fine until the update to fw 3.211, which makes the router stop detecting the ethernet cable. I’ve changed the cable, and also the modem but the error continues. Once I rolled back to the 3.203 fw, the modem get back to work normally.