GL-AXT1800 constant drop from wifi when in Repeater mode (4.7)

Hi. I just bought a GL-AXT1800. When i got it, i immediately upgraded to the latest firmware (4.7).
I am traveling for the first time with it, and the it keeps constantly dropping from the hotel wifi.
This doesn't happen to other devices on the hotel wifi.

When the device drops, the LED starts flashing blue.
I was able to collect this from the logs of the GL-AXT1800:

Mon Apr 28 16:53:08 2025 daemon.notice netifd: Network device 'sta1' link is down
Mon Apr 28 16:53:08 2025 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Mon Apr 28 16:53:08 2025 kern.info kernel: [ 4334.345605] sta1: deauthenticated from b4:a2:5c:f8:e4:b1 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Mon Apr 28 16:53:08 2025 daemon.notice netifd: wwan (8360): udhcpc: received SIGTERM
Mon Apr 28 16:53:08 2025 daemon.notice netifd: wwan (8360): udhcpc: unicasting a release of 10.100.5.245 to 10.100.0.1
Mon Apr 28 16:53:08 2025 daemon.notice netifd: wwan (8360): udhcpc: sending release
Mon Apr 28 16:53:08 2025 daemon.notice netifd: wwan (8360): udhcpc: entering released state
Mon Apr 28 16:53:08 2025 kern.warn kernel: [ 4334.409155] ath11k c000000.wifi: recv beacon last time 13300, connection is missing and disconnect it
Mon Apr 28 16:53:08 2025 daemon.notice netifd: wwan (8360): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wwan" } (Permission denied)
Mon Apr 28 16:53:08 2025 daemon.notice wpa_supplicant[4224]: sta1: CTRL-EVENT-DISCONNECTED bssid=b4:a2:5c:f8:e4:b1 reason=6
Mon Apr 28 16:53:08 2025 daemon.notice wpa_supplicant[4224]: sta1: SME: Trying to authenticate with b4:a2:5c:f8:e4:b1 (SSID='<redacted>' freq=2412 MHz)
Mon Apr 28 16:53:08 2025 kern.info kernel: [ 4334.446787] sta1: Connection to AP 00:00:00:00:00:00 lost
Mon Apr 28 16:53:08 2025 daemon.notice netifd: Interface 'wwan' is now down
Mon Apr 28 16:53:08 2025 daemon.info avahi-daemon[5520]: Withdrawing address record for 10.100.5.245 on sta1.
Mon Apr 28 16:53:08 2025 daemon.info avahi-daemon[5520]: Leaving mDNS multicast group on interface sta1.IPv4 with address 10.100.5.245.
Mon Apr 28 16:53:08 2025 daemon.info avahi-daemon[5520]: Interface sta1.IPv4 no longer relevant for mDNS.
Mon Apr 28 16:53:08 2025 daemon.warn dnsmasq[14148]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Apr 28 16:53:08 2025 daemon.err gl-repeater[3630]: (repeater.lua:498) disconnected from <redacted> b4:a2:5c:f8:e4:b1
Mon Apr 28 16:53:08 2025 kern.info kernel: [ 4334.515505] sta1: authenticate with b4:a2:5c:f8:e4:b1
Mon Apr 28 16:53:08 2025 kern.info kernel: [ 4334.522436] sta1: send auth to b4:a2:5c:f8:e4:b1 (try 1/3)
Mon Apr 28 16:53:08 2025 daemon.notice wpa_supplicant[4224]: sta1: Trying to associate with b4:a2:5c:f8:e4:b1 (SSID='<redacted>' freq=2412 MHz)
Mon Apr 28 16:53:08 2025 kern.info kernel: [ 4334.550246] sta1: authenticated
Mon Apr 28 16:53:08 2025 kern.info kernel: [ 4334.553489] sta1: associate with b4:a2:5c:f8:e4:b1 (try 1/3)
Mon Apr 28 16:53:08 2025 kern.info kernel: [ 4334.567616] sta1: RX AssocResp from b4:a2:5c:f8:e4:b1 (capab=0x421 status=0 aid=1)
Mon Apr 28 16:53:08 2025 kern.info kernel: [ 4334.569128] sta1: associated
Mon Apr 28 16:53:08 2025 daemon.notice netifd: Network device 'sta1' link is up
Mon Apr 28 16:53:08 2025 daemon.notice netifd: Interface 'wwan' has link connectivity
Mon Apr 28 16:53:08 2025 daemon.notice netifd: Interface 'wwan' is setting up now
Mon Apr 28 16:53:08 2025 daemon.notice wpa_supplicant[4224]: sta1: Associated with b4:a2:5c:f8:e4:b1
Mon Apr 28 16:53:08 2025 daemon.notice wpa_supplicant[4224]: sta1: CTRL-EVENT-CONNECTED - Connection to b4:a2:5c:f8:e4:b1 completed [id=0 id_str=]
Mon Apr 28 16:53:08 2025 daemon.notice wpa_supplicant[4224]: sta1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mon Apr 28 16:53:08 2025 daemon.info gl-repeater[3630]: (repeater-nl80211.lua:163) ifname sta1 mtu nil
Mon Apr 28 16:53:08 2025 daemon.info gl-repeater[3630]: (repeater.lua:485) connected to <redacted> b4:a2:5c:f8:e4:b1
Mon Apr 28 16:53:08 2025 daemon.notice netifd: wwan (18108): udhcpc: started, v1.36.1
Mon Apr 28 16:53:08 2025 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wwan" ] } }
Mon Apr 28 16:53:08 2025 kern.warn kernel: [ 4334.672939] kmwan: Delete node:wwan
Mon Apr 28 16:53:08 2025 daemon.notice netifd: wwan (18108): udhcpc: broadcasting discover
Mon Apr 28 16:53:08 2025 user.notice firewall: Reloading firewall due to ifdown of wwan ()
Mon Apr 28 16:53:08 2025 daemon.notice netifd: wwan (18108): udhcpc: broadcasting select for 10.100.5.245, server 10.100.0.1
Mon Apr 28 16:53:09 2025 daemon.notice netifd: wwan (18108): udhcpc: lease of 10.100.5.245 obtained from 10.100.0.1, lease time 43200
Mon Apr 28 16:53:09 2025 daemon.info avahi-daemon[5520]: Joining mDNS multicast group on interface sta1.IPv4 with address 10.100.5.245.
Mon Apr 28 16:53:09 2025 daemon.info avahi-daemon[5520]: New relevant interface sta1.IPv4 for mDNS.
Mon Apr 28 16:53:09 2025 daemon.info avahi-daemon[5520]: Registering new address record for 10.100.5.245 on sta1.IPv4.
Mon Apr 28 16:53:09 2025 daemon.notice netifd: Interface 'wwan' is now up
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using nameserver 100.100.100.100#53 for domain ts.net
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using nameserver 8.8.8.8#53
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using nameserver 202.140.62.62#53
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using nameserver 202.122.21.106#53
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for test
Mon Apr 28 16:53:09 2025 daemon.info gl-repeater[3630]: (repeater.lua:1695) interface "wwan" up
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for onion
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for localhost
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for local
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for invalid
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for bind
Mon Apr 28 16:53:09 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for lan
Mon Apr 28 16:53:10 2025 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wwan", "netdev": "sta1", "track_mode": "force", "addr_type": 4, "force_ip": "10.100.5.245", "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Mon Apr 28 16:53:10 2025 kern.warn kernel: [ 4336.011741] [add_dev_config 319]add node success. iface:wwan, dev:sta1, ifindex:30
Mon Apr 28 16:53:10 2025 user.notice firewall: Reloading firewall due to ifup of wwan (sta1)
Mon Apr 28 16:53:10 2025 daemon.info avahi-daemon[5520]: Interface tailscale0.IPv4 no longer relevant for mDNS.
Mon Apr 28 16:53:10 2025 daemon.info avahi-daemon[5520]: Leaving mDNS multicast group on interface tailscale0.IPv4 with address 100.66.117.15.
Mon Apr 28 16:53:10 2025 daemon.info avahi-daemon[5520]: Withdrawing address record for 100.66.117.15 on tailscale0.
Mon Apr 28 16:53:10 2025 user.notice root: disable GRO on tailscale0
Mon Apr 28 16:53:11 2025 daemon.info gl-repeater[3630]: (repeater-portal.lua:410) portal detecting...
Mon Apr 28 16:53:19 2025 daemon.notice netifd: Network device 'sta1' link is down
Mon Apr 28 16:53:19 2025 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Mon Apr 28 16:53:19 2025 kern.info kernel: [ 4345.122121] sta1: deauthenticated from b4:a2:5c:f8:e4:b1 (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
Mon Apr 28 16:53:19 2025 daemon.notice netifd: wwan (18108): udhcpc: received SIGTERM
Mon Apr 28 16:53:19 2025 daemon.notice netifd: wwan (18108): udhcpc: unicasting a release of 10.100.5.245 to 10.100.0.1
Mon Apr 28 16:53:19 2025 daemon.notice netifd: wwan (18108): udhcpc: sending release
Mon Apr 28 16:53:19 2025 daemon.notice netifd: wwan (18108): udhcpc: entering released state
Mon Apr 28 16:53:19 2025 daemon.notice netifd: wwan (18108): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "wwan" } (Permission denied)
Mon Apr 28 16:53:19 2025 daemon.notice netifd: Interface 'wwan' is now down
Mon Apr 28 16:53:19 2025 daemon.info avahi-daemon[5520]: Withdrawing address record for 10.100.5.245 on sta1.
Mon Apr 28 16:53:19 2025 daemon.info avahi-daemon[5520]: Leaving mDNS multicast group on interface sta1.IPv4 with address 10.100.5.245.
Mon Apr 28 16:53:19 2025 daemon.info avahi-daemon[5520]: Interface sta1.IPv4 no longer relevant for mDNS.
Mon Apr 28 16:53:19 2025 daemon.warn dnsmasq[14148]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Mon Apr 28 16:53:19 2025 daemon.notice wpa_supplicant[4224]: sta1: CTRL-EVENT-DISCONNECTED bssid=b4:a2:5c:f8:e4:b1 reason=6
Mon Apr 28 16:53:19 2025 daemon.err gl-repeater[3630]: (repeater.lua:498) disconnected from <redacted> b4:a2:5c:f8:e4:b1
Mon Apr 28 16:53:19 2025 daemon.notice wpa_supplicant[4224]: sta1: SME: Trying to authenticate with b4:a2:5c:f8:e4:b1 (SSID='<redacted>' freq=2412 MHz)
Mon Apr 28 16:53:19 2025 kern.info kernel: [ 4345.280113] sta1: authenticate with b4:a2:5c:f8:e4:b1
Mon Apr 28 16:53:19 2025 kern.info kernel: [ 4345.286891] sta1: send auth to b4:a2:5c:f8:e4:b1 (try 1/3)
Mon Apr 28 16:53:19 2025 daemon.notice wpa_supplicant[4224]: sta1: Trying to associate with b4:a2:5c:f8:e4:b1 (SSID='<redacted>' freq=2412 MHz)
Mon Apr 28 16:53:19 2025 kern.info kernel: [ 4345.299737] sta1: authenticated
Mon Apr 28 16:53:19 2025 kern.info kernel: [ 4345.303563] sta1: associate with b4:a2:5c:f8:e4:b1 (try 1/3)
Mon Apr 28 16:53:19 2025 daemon.notice netifd: Network device 'sta1' link is up
Mon Apr 28 16:53:19 2025 daemon.notice netifd: Interface 'wwan' has link connectivity
Mon Apr 28 16:53:19 2025 daemon.notice netifd: Interface 'wwan' is setting up now
Mon Apr 28 16:53:19 2025 daemon.notice wpa_supplicant[4224]: sta1: Associated with b4:a2:5c:f8:e4:b1
Mon Apr 28 16:53:19 2025 daemon.notice wpa_supplicant[4224]: sta1: CTRL-EVENT-CONNECTED - Connection to b4:a2:5c:f8:e4:b1 completed [id=0 id_str=]
Mon Apr 28 16:53:19 2025 kern.info kernel: [ 4345.314457] sta1: RX AssocResp from b4:a2:5c:f8:e4:b1 (capab=0x421 status=0 aid=1)
Mon Apr 28 16:53:19 2025 kern.info kernel: [ 4345.316017] sta1: associated
Mon Apr 28 16:53:19 2025 daemon.info gl-repeater[3630]: (repeater-nl80211.lua:163) ifname sta1 mtu nil
Mon Apr 28 16:53:19 2025 daemon.notice wpa_supplicant[4224]: sta1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mon Apr 28 16:53:19 2025 daemon.info gl-repeater[3630]: (repeater.lua:485) connected to <redacted> b4:a2:5c:f8:e4:b1
Mon Apr 28 16:53:19 2025 daemon.notice netifd: wwan (19092): udhcpc: started, v1.36.1
Mon Apr 28 16:53:19 2025 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wwan" ] } }
Mon Apr 28 16:53:19 2025 kern.warn kernel: [ 4345.404763] kmwan: Delete node:wwan
Mon Apr 28 16:53:19 2025 daemon.notice netifd: wwan (19092): udhcpc: broadcasting discover
Mon Apr 28 16:53:19 2025 user.notice firewall: Reloading firewall due to ifdown of wwan ()
Mon Apr 28 16:53:21 2025 daemon.notice netifd: wwan (19092): udhcpc: broadcasting select for 10.100.5.245, server 10.100.0.1
Mon Apr 28 16:53:21 2025 daemon.notice netifd: wwan (19092): udhcpc: lease of 10.100.5.245 obtained from 10.100.0.1, lease time 43200
Mon Apr 28 16:53:21 2025 daemon.info avahi-daemon[5520]: Joining mDNS multicast group on interface sta1.IPv4 with address 10.100.5.245.
Mon Apr 28 16:53:21 2025 daemon.info avahi-daemon[5520]: New relevant interface sta1.IPv4 for mDNS.
Mon Apr 28 16:53:21 2025 daemon.info avahi-daemon[5520]: Registering new address record for 10.100.5.245 on sta1.IPv4.
Mon Apr 28 16:53:21 2025 daemon.notice netifd: Interface 'wwan' is now up
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: reading /tmp/resolv.conf.d/resolv.conf.auto
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using nameserver 100.100.100.100#53 for domain ts.net
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using nameserver 8.8.8.8#53
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using nameserver 202.140.62.62#53
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using nameserver 202.122.21.106#53
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for test
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for onion
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for localhost
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for local
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for invalid
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for bind
Mon Apr 28 16:53:21 2025 daemon.info dnsmasq[14148]: using only locally-known addresses for lan
Mon Apr 28 16:53:21 2025 daemon.info gl-repeater[3630]: (repeater.lua:1695) interface "wwan" up
Mon Apr 28 16:53:21 2025 user.notice kmwan: config json str={ "op": 2, "data": { "cells": [ { "interface": "wwan", "netdev": "sta1", "track_mode": "force", "addr_type": 4, "force_ip": "10.100.5.245", "tracks": [ { "type": "ping", "ip": "1.1.1.1" }, { "type": "ping", "ip": "8.8.8.8" }, { "type": "ping", "ip": "208.67.222.222" }, { "type": "ping", "ip": "208.67.220.220" } ] } ] } }
Mon Apr 28 16:53:21 2025 kern.warn kernel: [ 4347.910124] [add_dev_config 319]add node success. iface:wwan, dev:sta1, ifindex:30
Mon Apr 28 16:53:22 2025 user.notice firewall: Reloading firewall due to ifup of wwan (sta1)
Mon Apr 28 16:53:22 2025 user.notice root: disable GRO on tailscale0
Mon Apr 28 16:53:23 2025 daemon.info gl-repeater[3630]: (repeater-portal.lua:410) portal detecting...
Mon Apr 28 16:53:27 2025 daemon.info gl-repeater[3630]: (repeater-portal.lua:426) detect portal aborted

I have just downgraded to 4.6 to see if it will solve. Is this a known issue?!

Hi,

  1. How about the AXT1800 repeater if it installed v4.6.8 firmware?
  2. If AXT1800 with v4.7.0 and connect to the phone hotspot through repeater, is it stable?
  3. If AXT1800 with v4.7.0, and connect to the hotel wifi. When it reproduced the issue, is the GL GUI available to access?
  1. 4.6.8 works perfectly fine. I downgraded and ran for an entire week at the hotel without any more issues.

  2. Not sure what you mean

  3. No, the device becomes completely unreachable. Unless I already had an Ethernet cable connected. I'm that case, even when it crashes I was still able to access the gui

Hi,

Thanks for your reply.

  1. AXT1800 on v4.7.0, bring it connects to a phone hotspot through repeater, is the router network stable?

  2. If it can access the GL GUI through wired cable, please export all syslogs and share with me through PM.

I'm sorry, but I can't upgrade the device back to 4.7 just to test this. Also, I'm no longer traveling, so I no longer have access to a hotel wifi with captive portal.