Very unstable wifi GL-AXT1800 v4.1

Technical Support for Routers
1

Hello, I recently upgraded to firmware v4.1 on my GL-AXT1800. Since then the wifi network has been very unstable.

I’m in wifi-repeater mode. Connected to a 5G Wifi network in repeater mode, and creating my own 2G and 5G wifi networks. It starts out OK, and I get very good download speeds on my clients. Every minute or two the light on the front of the router starts blinking. Sometimes the internal 2G and 5G networks disappear then after a minute reappear, but not always. Once I manage to reconnect to the internal 2G or 5G network (sometimes takes a couple of trys, all is well again for a little bit.

Below is my log from just before a disconnect, then it goes down, then comes back up.

Sat Jan  7 15:03:23 2023 daemon.notice hostapd: wlan0-1: AP-STA-DISCONNECTED dc:a6:32:f9:83:eb 0 0
Sat Jan  7 15:03:23 2023 daemon.info hostapd: wlan0-1: STA dc:a6:32:f9:83:eb IEEE 802.11: authenticated
Sat Jan  7 15:03:23 2023 daemon.info hostapd: wlan0-1: STA dc:a6:32:f9:83:eb IEEE 802.11: associated (aid 4)
Sat Jan  7 15:03:23 2023 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED dc:a6:32:f9:83:eb 0 0
Sat Jan  7 15:03:23 2023 daemon.info hostapd: wlan0-1: STA dc:a6:32:f9:83:eb RADIUS: starting accounting session 077F77E64B5F66F5
Sat Jan  7 15:03:23 2023 daemon.info hostapd: wlan0-1: STA dc:a6:32:f9:83:eb WPA: pairwise key handshake completed (RSN)
Sat Jan  7 15:03:23 2023 daemon.info dnsmasq-dhcp[5810]: DHCPREQUEST(br-lan) 192.168.8.131 dc:a6:32:f9:83:eb
Sat Jan  7 15:03:23 2023 daemon.info dnsmasq-dhcp[5810]: DHCPACK(br-lan) 192.168.8.131 dc:a6:32:f9:83:eb raspberrypi
Sat Jan  7 15:03:57 2023 daemon.notice netifd: Network device 'wlan-sta0' link is down
Sat Jan  7 15:03:57 2023 daemon.notice netifd: Interface 'wwan' has link connectivity loss
Sat Jan  7 15:03:57 2023 kern.info kernel: [  172.392444] wlan-sta0: disassociated from e0:63:da:19:87:a7 (Reason: 1=UNSPECIFIED)
Sat Jan  7 15:03:57 2023 daemon.notice netifd: wwan (8943): udhcpc: received SIGTERM
Sat Jan  7 15:03:57 2023 daemon.notice netifd: wwan (8943): udhcpc: unicasting a release of 172.16.130.197 to 172.16.130.1
Sat Jan  7 15:03:57 2023 daemon.notice netifd: wwan (8943): udhcpc: sending release
Sat Jan  7 15:03:57 2023 daemon.notice netifd: wwan (8943): udhcpc: entering released state
Sat Jan  7 15:03:57 2023 daemon.notice netifd: wwan (8943): Command failed: Permission denied
Sat Jan  7 15:03:57 2023 daemon.notice netifd: Interface 'wwan' is now down
Sat Jan  7 15:03:57 2023 daemon.info avahi-daemon[3439]: Withdrawing address record for 172.16.130.197 on wlan-sta0.
Sat Jan  7 15:03:57 2023 daemon.info avahi-daemon[3439]: Leaving mDNS multicast group on interface wlan-sta0.IPv4 with address 172.16.130.197.
Sat Jan  7 15:03:57 2023 daemon.info avahi-daemon[3439]: Interface wlan-sta0.IPv4 no longer relevant for mDNS.
Sat Jan  7 15:03:57 2023 daemon.notice netifd: Interface 'wwan' is disabled
Sat Jan  7 15:03:57 2023 daemon.notice netifd: Interface 'wwan' is enabled
Sat Jan  7 15:03:57 2023 daemon.warn dnsmasq[5810]: no servers found in /tmp/resolv.conf.d/resolv.conf.auto, will retry
Sat Jan  7 15:03:57 2023 daemon.notice wpa_supplicant[2479]: wlan-sta0: CTRL-EVENT-DISCONNECTED bssid=e0:63:da:19:87:a7 reason=1
Sat Jan  7 15:03:57 2023 daemon.notice wpa_supplicant[2479]: BSSID e0:63:da:19:87:a7 ignore list count incremented to 2, ignoring for 10 seconds
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>CTRL-EVENT-DISCONNECTED bssid=e0:63:da:19:87:a7 reason=1
Sat Jan  7 15:03:57 2023 user.notice mwan3[13477]: Execute ifdown event on interface wwan (unknown)
Sat Jan  7 15:03:57 2023 user.info mwan3track[9577]: Detect ifdown event on interface wwan (wlan-sta0)
Sat Jan  7 15:03:57 2023 user.notice mwan3track[9577]: Interface wwan (wlan-sta0) is offline
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>CTRL-EVENT-SCAN-STARTED
Sat Jan  7 15:03:57 2023 daemon.notice hostapd: handle_probe_req: send failed
Sat Jan  7 15:03:57 2023 daemon.notice hostapd: handle_probe_req: send failed
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>CTRL-EVENT-SCAN-RESULTS
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>WPS-AP-AVAILABLE
Sat Jan  7 15:03:57 2023 daemon.notice wpa_supplicant[2479]: wlan-sta0: SME: Trying to authenticate with e0:63:da:19:87:a7 (SSID='INVITADOS' freq=5200 MHz)
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>SME: Trying to authenticate with e0:63:da:19:87:a7 (SSID='INVITADOS' freq=5200 MHz)
Sat Jan  7 15:03:57 2023 kern.info kernel: [  172.968617] wlan-sta0: authenticate with e0:63:da:19:87:a7
Sat Jan  7 15:03:57 2023 daemon.notice wpa_supplicant[2479]: wlan-sta0: Trying to associate with e0:63:da:19:87:a7 (SSID='INVITADOS' freq=5200 MHz)
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>Trying to associate with e0:63:da:19:87:a7 (SSID='INVITADOS' freq=5200 MHz)
Sat Jan  7 15:03:57 2023 kern.info kernel: [  173.061781] wlan-sta0: send auth to e0:63:da:19:87:a7 (try 1/3)
Sat Jan  7 15:03:57 2023 kern.info kernel: [  173.067628] wlan-sta0: authenticated
Sat Jan  7 15:03:57 2023 kern.info kernel: [  173.068331] wlan-sta0: associate with e0:63:da:19:87:a7 (try 1/3)
Sat Jan  7 15:03:57 2023 kern.info kernel: [  173.073502] wlan-sta0: RX AssocResp from e0:63:da:19:87:a7 (capab=0x1511 status=0 aid=1)
Sat Jan  7 15:03:57 2023 kern.info kernel: [  173.077829] wlan-sta0: associated
Sat Jan  7 15:03:57 2023 daemon.notice netifd: Network device 'wlan-sta0' link is up
Sat Jan  7 15:03:57 2023 daemon.notice netifd: Interface 'wwan' has link connectivity
Sat Jan  7 15:03:57 2023 daemon.notice netifd: Interface 'wwan' is setting up now
Sat Jan  7 15:03:57 2023 daemon.notice wpa_supplicant[2479]: wlan-sta0: Associated with e0:63:da:19:87:a7
Sat Jan  7 15:03:57 2023 daemon.notice wpa_supplicant[2479]: wlan-sta0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>Associated with e0:63:da:19:87:a7
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sat Jan  7 15:03:57 2023 daemon.notice netifd: wwan (13623): udhcpc: started, v1.33.2
Sat Jan  7 15:03:57 2023 daemon.notice netifd: wwan (13623): udhcpc: sending discover
Sat Jan  7 15:03:57 2023 daemon.notice wpa_supplicant[2479]: wlan-sta0: WPA: Key negotiation completed with e0:63:da:19:87:a7 [PTK=CCMP GTK=CCMP]
Sat Jan  7 15:03:57 2023 daemon.notice wpa_supplicant[2479]: wlan-sta0: CTRL-EVENT-CONNECTED - Connection to e0:63:da:19:87:a7 completed [id=0 id_str=]
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>WPA: Key negotiation completed with e0:63:da:19:87:a7 [PTK=CCMP GTK=CCMP]
Sat Jan  7 15:03:57 2023 daemon.info repeater: (/usr/sbin/repeater:472) IFNAME=wlan-sta0 <3>CTRL-EVENT-CONNECTED - Connection to e0:63:da:19:87:a7 completed [id=0 id_str=]
Sat Jan  7 15:03:58 2023 kern.info kernel: [  173.377527] ath11k c000000.wifi: bss color param 0x81000000 set on vdev 1
Sat Jan  7 15:03:59 2023 daemon.notice hostapd: wlan0-1: AP-STA-DISCONNECTED 40:cb:c0:b4:0d:c6 0 0
Sat Jan  7 15:03:59 2023 daemon.info hostapd: wlan0-1: STA 40:cb:c0:b4:0d:c6 IEEE 802.11: authenticated
Sat Jan  7 15:03:59 2023 daemon.info hostapd: wlan0-1: STA 40:cb:c0:b4:0d:c6 IEEE 802.11: associated (aid 1)
Sat Jan  7 15:03:59 2023 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED 40:cb:c0:b4:0d:c6 0 0
Sat Jan  7 15:03:59 2023 daemon.info hostapd: wlan0-1: STA 40:cb:c0:b4:0d:c6 RADIUS: starting accounting session 781B12F54A7C422A
Sat Jan  7 15:03:59 2023 daemon.info hostapd: wlan0-1: STA 40:cb:c0:b4:0d:c6 WPA: pairwise key handshake completed (RSN)
Sat Jan  7 15:04:01 2023 daemon.notice netifd: wwan (13623): udhcpc: sending discover
Sat Jan  7 15:04:01 2023 daemon.notice netifd: wwan (13623): udhcpc: sending select for 172.16.130.197
Sat Jan  7 15:04:01 2023 daemon.notice netifd: wwan (13623): udhcpc: lease of 172.16.130.197 obtained, lease time 28800
Sat Jan  7 15:04:01 2023 daemon.info avahi-daemon[3439]: Joining mDNS multicast group on interface wlan-sta0.IPv4 with address 172.16.130.197.
Sat Jan  7 15:04:01 2023 daemon.info avahi-daemon[3439]: New relevant interface wlan-sta0.IPv4 for mDNS.
Sat Jan  7 15:04:01 2023 daemon.info avahi-daemon[3439]: Registering new address record for 172.16.130.197 on wlan-sta0.IPv4.
Sat Jan  7 15:04:01 2023 daemon.notice netifd: Interface 'wwan' is now up
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: reading /tmp/resolv.conf.d/resolv.conf.auto
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using only locally-known addresses for domain test
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using only locally-known addresses for domain onion
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using only locally-known addresses for domain localhost
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using only locally-known addresses for domain local
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using only locally-known addresses for domain invalid
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using only locally-known addresses for domain bind
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using only locally-known addresses for domain lan
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using nameserver 208.91.112.53#53
Sat Jan  7 15:04:01 2023 daemon.info dnsmasq[5810]: using nameserver 208.91.112.52#53
Sat Jan  7 15:04:01 2023 user.notice mwan3[13950]: Execute ifup event on interface wwan (wlan-sta0)
Sat Jan  7 15:04:02 2023 user.notice mwan3[13950]: Starting tracker on interface wwan (wlan-sta0)
Sat Jan  7 15:04:02 2023 user.notice mwan3track[9577]: Stopping mwan3track for interface "wwan"
Sat Jan  7 15:04:03 2023 user.info mwan3rtmon[3212]: Detect rtchange event.
Sat Jan  7 15:04:04 2023 daemon.notice hostapd: wlan0-1: AP-STA-DISCONNECTED 4c:57:ca:7c:c4:80 0 0
Sat Jan  7 15:04:04 2023 daemon.info hostapd: wlan0-1: STA 4c:57:ca:7c:c4:80 IEEE 802.11: authenticated
Sat Jan  7 15:04:04 2023 daemon.info hostapd: wlan0-1: STA 4c:57:ca:7c:c4:80 IEEE 802.11: associated (aid 2)
Sat Jan  7 15:04:04 2023 daemon.notice hostapd: wlan0-1: AP-STA-CONNECTED 4c:57:ca:7c:c4:80 0 0
Sat Jan  7 15:04:04 2023 daemon.info hostapd: wlan0-1: STA 4c:57:ca:7c:c4:80 RADIUS: starting accounting session 746506F33653DEE8
Sat Jan  7 15:04:04 2023 daemon.info hostapd: wlan0-1: STA 4c:57:ca:7c:c4:80 WPA: pairwise key handshake completed (RSN)
Sat Jan  7 15:04:04 2023 user.notice firewall: Reloading firewall due to ifup of wwan (wlan-sta0)
Sat Jan  7 15:04:09 2023 user.info mwan3track[14320]: Lost 4 ping(s) on interface wwan (wlan-sta0)
Sat Jan  7 15:04:16 2023 daemon.info hostapd: wlan1: STA 4a:2d:f9:4c:0d:ae IEEE 802.11: authenticated
Sat Jan  7 15:04:16 2023 daemon.info hostapd: wlan1: STA 4a:2d:f9:4c:0d:ae IEEE 802.11: associated (aid 4)
Sat Jan  7 15:04:16 2023 daemon.notice hostapd: wlan1: AP-STA-CONNECTED 4a:2d:f9:4c:0d:ae 0 0
Sat Jan  7 15:04:16 2023 daemon.info hostapd: wlan1: STA 4a:2d:f9:4c:0d:ae RADIUS: starting accounting session EC13B52ED297DD51
Sat Jan  7 15:04:16 2023 daemon.info hostapd: wlan1: STA 4a:2d:f9:4c:0d:ae WPA: pairwise key handshake completed (RSN)
Sat Jan  7 15:04:16 2023 daemon.info dnsmasq-dhcp[5810]: DHCPREQUEST(br-lan) 192.168.8.193 4a:2d:f9:4c:0d:ae
Sat Jan  7 15:04:16 2023 daemon.info dnsmasq-dhcp[5810]: DHCPACK(br-lan) 192.168.8.193 4a:2d:f9:4c:0d:ae

Copyright © 2022 GL.iNet. All Rights Reserved
2 Likes
2

Can you set repeater to use 5G wifi?

From the log it is disconnected for no reason.

I am using 4.2 and it is stable here.

3

What do you mean use 5G? Does that mean I should only create internal 5G network and not 2G network? Or does it mean only connect to 5G external network?

Is there a way to find out why it disconnected? Could it be the external network at this hotel that is having a problem? I thought no, because when the problem happens the internal networks go down also, and I have to wait for a minute to reconnect to the router.

Is 4.2 available to the public? My router says it is up to date with 4.1 when I check the firmware version.

4

4.2 is in snapshot GL.iNet download center

I mean connecting to 5G wifi network as repeater.

In repeater it displays what band it is using.

image
image1007×422 20.7 KB

5

I have set it to use only 5Ghz and the problem continues. One thought. Could it be over-heating? I think I remember I used to hear the fan sometimes, but now there is no fan running, even when the case feels very warm. Is there a way to test this idea?

6

In System->Dashboard, you can lower the temperature setting of fun turnning on. Pls try.

7

Same issue here, been experiencing serious unstable connection for months. In my situation, the log looks like:

Mon Feb 13 21:53:16 2023 user.info mwan3track[11145]: Lost 4 ping(s) on interface wwan (wlan-sta0)
Mon Feb 13 21:53:34 2023 user.info mwan3track[11145]: Lost 4 ping(s) on interface wwan (wlan-sta0)
Mon Feb 13 21:54:25 2023 user.info mwan3track[11145]: Lost 4 ping(s) on interface wwan (wlan-sta0)
Mon Feb 13 21:55:10 2023 user.info mwan3track[11145]: Lost 3 ping(s) on interface wwan (wlan-sta0)
Mon Feb 13 21:56:08 2023 user.info mwan3track[11145]: Lost 3 ping(s) on interface wwan (wlan-sta0)
Mon Feb 13 21:56:45 2023 user.info mwan3track[11145]: Lost 5 ping(s) on interface wwan (wlan-sta0)
Mon Feb 13 21:57:25 2023 user.notice mwan3[7851]: Execute ifdown event on interface wwan (wlan-sta0)
Mon Feb 13 21:57:26 2023 user.info mwan3track[11145]: Detect ifdown event on interface wwan (wlan-sta0)
Mon Feb 13 21:57:31 2023 user.notice mwan3track[11145]: Interface wwan (wlan-sta0) is offline
Mon Feb 13 21:57:34 2023 user.info mwan3track[11145]: Lost 10 ping(s) on interface wwan (wlan-sta0)
Mon Feb 13 21:57:56 2023 user.info mwan3track[11145]: Lost 1 ping(s) on interface wwan (wlan-sta0)

I tried to lower the fan activation temperature, but no help. The CPU’s temperature never goes beyond 60 C degrees. I flashed other versions of official firmware, and factory-reset it numerous times, still no help. I’ve got the feeling that this one is also having SoC problems like the MT1300 model.

8

Yours seems to be due to MWAN3 doing its job of making sure it can connect to Google or Cisco servers. You might want to adjust your Multi-WAN settings for available and failure conditions cause your connection has high latency and/or jitter.

9

it is possible in 4.1.0 release 6 firmware? because i cant find the way of see temperatures in the gui

10

At least in 4.2.0 snapshot there is

image
image958×432 23.1 KB

1 Like
11

FYI, this seems to have resolved my issue. I turned the fan speed start temperature down to the minimum (70 degrees) and stability seems to have improved, and the fan does run. So I’m sort of satisfied. However, it seems to run quite hot for a travel router, even under very light load, and my copy at least had over-heat problems with factory settings. I’m kind of meh about this router. I bought it because I was looking for better range and performance in repeater mode with marina wifi networks (I live and travel on boats) than my GL-AR750S. It does seem a tiny bit better, but too bad about how hot it runs. Thanks for the help.

12

Beryl AX is smaller and not that hot.

13

Never mind, still having the problem. When I do big transfers across the local network the connection gets unstable. I think it might be a temperature thing. If I’m just doing typical browser stuff, the seems to stay stable enough.

1 Like
14

I’ve lost patience with this router. It is too unstable to use. I’ve gone back to my old GL-AR750S and it is working with good stability in the same environment, though the performance isn’t quite as high. I’d like my Slate AX replaced under warranty, how do I do that? Even better would be to replace it with a Beryl AX so I have something that runs a little cooler.

15

Pls talk to customer service where you bought this.

16

It works! You are right that MWAN utility has the default value of 1.1.1.1(Cloudflare) and 8.8.8.8(Google) as the ping target. These services are not available in PRC.

Thanks a lot!

1 Like