I had gradually lost connection to Wireless connection in repeater mode. I have done multiple reset, firmware downgrade, upgrade, etc, but no difference.
What happens is that in GL.iNet admin panel it does find Wifi network and try to connect but always end up in “Connection failed, will retry later…” in LuCi Wireless overview, if I try to “Wireless Scan” it end up “Session expired A new login is required since the authentication session expired.” in a matter of few seconds.
Any suggestion is greatly appreciated.
Here is the log.
Sat Nov 1 10:18:33 2025 daemon.info lua: (.../ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:897) Switching...
Sat Nov 1 10:18:33 2025 daemon.info lua: (.../ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1360) prepare connect 'AndroidShare_5378(16:b5:89:23:c6:fd)', WPA2PSK/TKIPAES channel 11
Sat Nov 1 10:18:33 2025 daemon.info lua: (.../ipkg-mipsel_24kc/gl-sdk4-repeater/usr/sbin/repeater:1458) connecting 'AndroidShare_5378 16:b5:89:23:c6:fd'...
Sat Nov 1 10:18:33 2025 daemon.notice netifd: Wireless device 'mt7628' is now down
Sat Nov 1 10:18:33 2025 daemon.notice netifd: Network device 'apcli0' link is up
Sat Nov 1 10:18:34 2025 daemon.notice netifd: Interface 'wwan' has link connectivity
Sat Nov 1 10:18:34 2025 daemon.notice netifd: Wireless device 'mt7628' is now up
Sat Nov 1 10:18:34 2025 daemon.notice netifd: Network device 'ra0' link is up
I've had this happen before with my mt3000. I restarted the host router and reconnected with my mt3000, it then began to work fine, I'm guessing that my host router had something going on with the DHCP table.
If Repeater program is running, it may affect LuCI behavior since the repeater operates on the same Wi-Fi chips.
Please perform tests using only the GL.iNet Web UI to avoid conflicts.
To help us investigate, please provide:
The current firmware version
Device logs exported immediately after the issue occurs, shared with us via private message.
However interestingly, restarting the host router worked for a couple of minutes, then the whole network went down. Restarting the host router after that didn’t work and needed to reset the router to the default. Like you said, maybe somehow my MT300n messed up the DHCP table???
It's possible, but in my case, the mt3000 didn't mess up the DHCP table per say, I think it had more to do with how my host router handled its own DHCP table in general.
Something that did help on the mt3000 side of things though was that I turned off the randomized mac, and opted to go with the factory mac for the mt3000. Next time I connected the mt3000 to my host router, I added a static DHCP lease IP and arp table for my mt3000 onto the host router. Its works without doing that, because I already tested it without the static lease and ARP table, but I figured it wouldn't hurt to do so.
