My GL-SFT1200 (Opal) connects to my ATT home router (model 5268AC FXN) and Asus router (RT-AC86U) that sits behind the ATT router via ethernet with no issues. However, my GL-MT3000 (Beryl AX) (kernel version 5.4.211) with the same ethernet cables as the Opal will only connect to the Asus router. Another poster fixed their issue by getting a replacement unit since the first one was defective. However, after getting a replacement Beryl AX unit, I am still unable to connect to the ATT router via ethernet.
Why will the Opal router connect to both the ATT and Asus router without any issues? Whereas the Beryl AX router will only connect to the Asus router?
What other information can I provide to resolve this issue as I don’t want to request another replacement unit.
Have you tried power cycling the ATT unit before switching the GL devices? I’m wondering if it locks onto the MAC of the downstream device for some reason.
@bring.fringe18 I previously power cycled the ATT router, but performing another power cycle did not solve the problem. And before power cycling, I cleared the “device list” on the ATT router to ensure the only ethernet connection to the ATT router was the home Asus router.
I am unable to assign a static IP because the GL-MT3000 is unable to complete the handshake with the router at the ethernet interface level. The ATT router has to assign a dynamic IP address before a static address can be assigned. Unfortunately, it is not possible to assign a static IP address using the mac address of the Gl-MT3000.
Doing a factory reset of the GL-MT3000 made no difference. However, a brief moment, I caught a screenshot of the GL-MT3000 attempting to connect via ethernet without any success – see image. That is the one and only time I saw the GL-MT3000 attempting to connect to the ATT router over ethernet.
Unlike the ATT router, the GL-MT3000 continues to have no problem connecting to the Asus router via ethernet.
Some compatibility issues were reported with certain devices while attempting to establish a link on the GL-MT3000 factory firmware WAN port.
Please try these workarounds:
Option 1:
exchange wan and lan port, by run command:
uci set network.@device[2].name='eth1'
uci set network.wan.device='eth1'
uci set network.@device[0].ports='eth0'
uci set network.@device[1].name='eth0'
uci set board_special.network.wan='eth1'
uci set board_special.network.lan='eth0'
uci commit network
uci commit board_special
reboot
@hansome I went with Option 1, which seems to work by switching the WAN to the LAN port. While looking positive, I need to do more testing before I can confirm the issue resolved.
And as noted in the screenshot, despite the ethernet connection working, the dashboard states it is not. That makes sense since the LAN and WAN ports got flipped.
In the meantime
Is the plan to have this issue fixed in a future build? And if so, will I need to back out these changes?
If I want to revert the changes do I simply reverse the commands you provided above so they look like this?
uci set network.@device[2].name=‘eth0’
uci set network.wan.device=‘eth0’
uci set network.@device[0].ports=‘eth1’
uci set network.@device[1].name=‘eth1’
uci set board_special.network.wan=‘eth0’
uci set board_special.network.lan=‘eth1’
uci commit network
uci commit board_special
reboot
Yes. Using the commands above successfully switched the WAN to the LAN port to restore WAN ethernet connectivity. I will run a few more tests, but it is looking good.
And to be clear, I used the commands from @hansome
Option 1:
exchange wan and lan port, by run command:
uci set network.@device[2].name='eth1'
uci set network.wan.device='eth1'
uci set network.@device[0].ports='eth0'
uci set network.@device[1].name='eth0'
uci set board_special.network.wan='eth1'
uci set board_special.network.lan='eth0'
uci commit network
uci commit board_special
reboot
@hansome The workaround appears to work with certain limitations that are not a show stopper for me. Others need to be aware that switching the WAN with the LAN port means the LAN port only pushes 100 mbps based on my limited tests.
What are the steps that need to be taken to reverse the change?
I tested it’s normal to show the wan status and the speed is 1Gbps. Maybe you can reset firmware and run that command again.
To reverse the changes:
uci set network.@device[2].name='eth0'
uci set network.wan.device='eth0'
uci set network.@device[0].ports='eth1'
uci set network.@device[1].name='eth1'
uci set board_special.network.wan='eth0'
uci set board_special.network.lan='eth1'
uci commit network
uci commit board_special
reboot
This is for certain switch/modems that cannot link to the 2.5G WAN port(not very common case actually), so it won’t merge to a permanent fix.
