GL-MT1300 LAN WiFi Constantly drops out

alistair23 · 2021-06-16T12:22:31.049Z

Tried that, no luck. Still seeing disconnects

alistair23 · 2021-06-18T01:26:22.782Z

Any other ideas? Is it worth trying the 3.203 firmware?

~~I’m trying disabling DNS over TLS to see if that helps, but I don’t have high hopes. I’ll also test without Wireguard to see if that helps, but that isn’t a long term solution.~~ Enabling/disabling Wireguard or DNS settings doesn’t seem to make any difference. I still see regular disconnects.

I have also now tried a 65W laptop USB charger to see if that helps, no luck. I lowered the 2.4GHz and 5Ghz power as well and no luck there.

Otherwise I’m going to have to return it. It doesn’t work as every device is constantly disconnected from the WiFi.

alzhao · 2021-06-18T09:49:00.516Z

The only thing to check now is wifi encryption.

But if all devices disconnect, then is may be something else. If things cannot improve you may return.

alistair23 · 2021-06-18T22:52:58.546Z

Even if it is WiFi encryption, I’m not going to disable that. Who do I talk to about a refund?

alistair23 · 2021-06-20T23:34:06.527Z

On a Linux system this is the type of errors that I see:

[ 2410.023392] net_ratelimit: 10 callbacks suppressed
[ 2410.023398] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.024037] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.024744] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.027082] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.027083] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.027084] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.029444] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.029446] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.029447] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2410.030063] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2445.697804] wlp69s0: authenticate with 94:83:c4:0d:50:14
[ 2445.700177] wlp69s0: send auth to 94:83:c4:0d:50:14 (try 1/3)
[ 2445.735420] wlp69s0: authenticated
[ 2445.735758] wlp69s0: associate with 94:83:c4:0d:50:14 (try 1/3)
[ 2445.749495] wlp69s0: RX AssocResp from 94:83:c4:0d:50:14 (capab=0x431 status=0 aid=4)
[ 2445.755792] wlp69s0: associated
[ 2451.428640] wlp69s0: authenticate with 94:83:c4:0d:50:14
[ 2451.430998] wlp69s0: send auth to 94:83:c4:0d:50:14 (try 1/3)
[ 2451.460982] wlp69s0: authenticated
[ 2451.461689] wlp69s0: associate with 94:83:c4:0d:50:14 (try 1/3)
[ 2451.467240] wlp69s0: RX AssocResp from 94:83:c4:0d:50:14 (capab=0x431 status=0 aid=4)
[ 2451.471388] wlp69s0: associated
[ 2491.196941] wlp69s0: authenticate with 94:83:c4:0d:50:14
[ 2491.199312] wlp69s0: send auth to 94:83:c4:0d:50:14 (try 1/3)
[ 2491.228243] wlp69s0: authenticated
[ 2491.230228] wlp69s0: associate with 94:83:c4:0d:50:14 (try 1/3)
[ 2491.237882] wlp69s0: RX AssocResp from 94:83:c4:0d:50:14 (capab=0x431 status=0 aid=4)
[ 2491.241714] wlp69s0: associated
[ 2494.653894] wlp69s0: authenticate with 94:83:c4:0d:50:14
[ 2494.656232] wlp69s0: send auth to 94:83:c4:0d:50:14 (try 1/3)
[ 2494.686114] wlp69s0: authenticated
[ 2494.688171] wlp69s0: associate with 94:83:c4:0d:50:14 (try 1/3)
[ 2494.693643] wlp69s0: RX AssocResp from 94:83:c4:0d:50:14 (capab=0x431 status=0 aid=4)
[ 2494.699910] wlp69s0: associated
[ 2494.786001] net_ratelimit: 12 callbacks suppressed
[ 2494.786006] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2538.118034] wlp69s0: authenticate with 94:83:c4:0d:50:14
[ 2538.120429] wlp69s0: send auth to 94:83:c4:0d:50:14 (try 1/3)
[ 2538.248114] wlp69s0: send auth to 94:83:c4:0d:50:14 (try 2/3)
[ 2538.350967] wlp69s0: send auth to 94:83:c4:0d:50:14 (try 3/3)
[ 2538.634613] wlp69s0: authentication with 94:83:c4:0d:50:14 timed out
[ 2545.316930] wlp69s0: authenticate with 94:83:c4:0d:50:14
[ 2545.319606] wlp69s0: send auth to 94:83:c4:0d:50:14 (try 1/3)
[ 2545.350196] wlp69s0: authenticated
[ 2545.350560] wlp69s0: associate with 94:83:c4:0d:50:14 (try 1/3)
[ 2545.359389] wlp69s0: RX AssocResp from 94:83:c4:0d:50:14 (capab=0x431 status=0 aid=4)
[ 2545.360932] iwlwifi 0000:45:00.0: Unhandled alg: 0x3f0707
[ 2545.362185] wlp69s0: associated

alzhao · 2021-06-21T04:29:41.608Z

Can you get the log of wpa_supplicant from your Linux which could show more info?

It should be in /var/log/syslog

alistair23 · 2021-06-21T05:34:13.199Z

Jun 21 08:56:37 wpa_supplicant[4144]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfac>
Jun 21 08:56:38 wpa_supplicant[4144]: wlp69s0: SME: Trying to authenticate with 94:83:c4:0d:50:14 (SSID=‘’ freq=2462 MHz)
Jun 21 08:56:38 wpa_supplicant[4144]: wlp69s0: Trying to associate with 94:83:c4:0d:50:14 (SSID='’ freq=2462 MHz)
Jun 21 08:56:38 wpa_supplicant[4144]: wlp69s0: Associated with 94:83:c4:0d:50:14
Jun 21 08:56:38 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 21 08:56:38 wpa_supplicant[4144]: wlp69s0: WPA: Key negotiation completed with 94:83:c4:0d:50:14 [PTK=CCMP GTK=CCMP]
Jun 21 08:56:38 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-CONNECTED - Connection to 94:83:c4:0d:50:14 completed [id=0 id_str=]
Jun 21 08:56:38 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-73 noise=9999 txrate=26000
Jun 21 08:56:40 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-DISCONNECTED bssid=94:83:c4:0d:50:14 reason=4 locally_generated=1
Jun 21 08:56:41 wpa_supplicant[4144]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfac>
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: SME: Trying to authenticate with 94:83:c4:0d:50:14 (SSID=‘’ freq=2462 MHz)
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: Trying to associate with 94:83:c4:0d:50:14 (SSID='’ freq=2462 MHz)
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: Associated with 94:83:c4:0d:50:14
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: WPA: Key negotiation completed with 94:83:c4:0d:50:14 [PTK=CCMP GTK=CCMP]
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-CONNECTED - Connection to 94:83:c4:0d:50:14 completed [id=0 id_str=]
Jun 21 08:56:41 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-70 noise=9999 txrate=26000
Jun 21 08:57:22 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:57:22 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:57:22 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:57:22 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:57:26 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:57:26 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:57:26 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-BEACON-LOSS
Jun 21 08:57:26 wpa_supplicant[4144]: wlp69s0: CTRL-EVENT-DISCONNECTED bssid=94:83:c4:0d:50:14 reason=4 locally_generated=1

JerryZhao · 2021-06-22T03:17:37.385Z

Use your mobile phone to connect to the MT1300, normal?

alistair23 · 2021-06-22T03:29:04.301Z

Nope, all devices appear to have the same problem

GL-FUN · 2021-07-18T14:19:54.211Z

I had the same and I found that if a client makes an excessive number of DNS requests (reliably replicated - until i found the reason, I reimaged the router and configured from scratch again, though it was a problem with the router) the router drops the connection.

if on windows, try LiveTcpUdpWatch from nirsoft[.]net or other equivalent if mac etc

alzhao · 2021-07-19T04:44:19.235Z

How did you solve then?

GL-FUN · 2021-07-19T08:49:24.164Z

i would not say solved, the router continues dropping connection when an excessive number of DNS queries are made: I do some testing with BIND RPZ on raspberry pi and it seems i hit the router’s limitation. hopefully, it can be corrected programmatically, but I have not figured out how to do so.

FYI: the rate it’s happening is dozens of queries per second - unlikely can be achieved by a healthy system. so I suspect @alistair23 might have something suspicious going on on his system (a bot infection?)

with this rate of testing no dropped connections, but if i 2-3x increase it I will experience the same drops

image1511×334 29.9 KB

alzhao · 2021-07-19T10:23:16.120Z

Can you check the router’s cpu usage? Maybe it is full?

GL-FUN · 2021-07-19T10:40:09.367Z

image1723×220 10.8 KB

does not seem to be full - but now i an under the above conditions 200-300 DNS qps (5wps)

but this is 5 times more than the whole household on another Pi.

klyntar · 2021-08-06T14:34:14.943Z

I’m having the same problem with the Wifi. It keeps dropping out. I’m wondering if it’s related to the FRAG Wifi attacks patched in the latest firmware which seems to be hung up for this router specifically. It was fine on 3.201 up until the last week or so. I’ve tried upgrading to 3.203 Beta but the wifi wasn’t working with the build so I had to downgrade it back to 3.201. Still have the same problem. Hugely annoying at the moment since it’s dropping and locking up my zoom calls and tv streams. If anyone has any ideas, I’m getting pretty annoyed and might swap for another device until the next firmware lands.

chriswyatt · 2021-10-22T13:25:26.189Z

It might not be the same problem here, but I found that with the wi-fi was frequently dropping out on both 2 GHz and 5 GHz. The issue turned out to be automatic scanning. Once I unchecked ‘Auto scan and re-connect’ in the repeater options, the problem went away.

The behaviour only appeared after I added my phone’s hotspot to the list of known networks.

kiltym · 2021-10-27T18:44:36.984Z

Have the same issue on my devices when connected to WiFi on MT1300. Running latest firmware.

I also have a LOT of DHCP requests that keep showing up in the logs, just like @alistair23

They are from Windows 10 computers. My only workaround was to set static IP on both my windows machines. I do not have this issue on any other router so there is some odd interaction between MT1300 and Windows 10. Not sure this will address the WiFi disconnect issue, but will re-post if reducing the DHCP requests has any effect.

Either way, GL should look into why Windows 10 causes so many DHCP requests. It looks like every 45 seconds the Windows 10 machine calls for new DHCP:

Wed Oct 27 12:31:29 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:32:16 2021 daemon.info dnsmasq-dhcp[2880]: DHCPREQUEST(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:32:16 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:32:59 2021 daemon.info dnsmasq-dhcp[2880]: DHCPREQUEST(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:32:59 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:33:45 2021 daemon.info dnsmasq-dhcp[2880]: DHCPREQUEST(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:33:45 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:34:30 2021 daemon.info dnsmasq-dhcp[2880]: DHCPREQUEST(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:34:30 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:35:15 2021 daemon.info dnsmasq-dhcp[2880]: DHCPREQUEST(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:35:15 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:36:00 2021 daemon.info dnsmasq-dhcp[2880]: DHCPREQUEST(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:36:00 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:36:46 2021 daemon.info dnsmasq-dhcp[2880]: DHCPREQUEST(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:36:46 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:37:32 2021 daemon.info dnsmasq-dhcp[2880]: DHCPREQUEST(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:37:32 2021 daemon.info dnsmasq-dhcp[2880]: DHCPACK(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d ASUS
Wed Oct 27 12:38:15 2021 daemon.info dnsmasq-dhcp[2880]: DHCPRELEASE(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:38:19 2021 daemon.info dnsmasq-dhcp[2880]: DHCPDISCOVER(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d
Wed Oct 27 12:38:19 2021 daemon.info dnsmasq-dhcp[2880]: DHCPOFFER(br-lan) 192.168.8.181 98:2c:bc:d4:b8:1d

kiltym · 2021-10-27T18:47:51.080Z

Just to add some more detail on my WiFi disconnects.

The MT1300 is my main router, it is tethered to a phone for internet access.

The disconnects happen on all my devices, iPad, Android, Windows, etc…

If there is anything I can post to resolve the issue, please ask!

Tytanium · 2021-11-20T19:14:39.470Z

I’m having this exact issue as well. DHCP log floods from my windows laptop, and even when I put it to static IP I’m getting wifi drops over and over. Firmware version is 3.203 and keep seeing this in the kernel log, xx:xx:xx:xx:xx:xx is my laptop mac

[ 4022.277556] scan_ch_restore,central ch=1,bw=0
[ 4022.277556]
[ 4063.656442] scan_ch_restore,central ch=155,bw=2
[ 4063.656442]
[ 4067.415471] scan_ch_restore,central ch=1,bw=0
[ 4067.415471]
[ 4073.345698] AP SETKEYS DONE - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=1 from xx:xx:xx:xx:xx:xx
[ 4073.345698]
[ 4108.698357] scan_ch_restore,central ch=155,bw=2
[ 4108.698357]
[ 4112.573569] scan_ch_restore,central ch=1,bw=0
[ 4112.573569]
[ 4118.703103] AP SETKEYS DONE - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=1 from xx:xx:xx:xx:xx:xx
[ 4118.703103]
[ 4153.835444] scan_ch_restore,central ch=155,bw=2
[ 4153.835444]
[ 4157.711023] scan_ch_restore,central ch=1,bw=0
[ 4157.711023]
[ 4163.651153] AP SETKEYS DONE - AKMMap=WPA2PSK, PairwiseCipher=AES, GroupCipher=AES, wcid=1 from xx:xx:xx:xx:xx:xx
[ 4163.651153]

Tytanium · 2021-11-20T19:38:57.053Z

It all started when I connected an apple TV hardwired into the router and now I unplugged it and it is stopped disconnecting me. Not sure if there was an IP conflict or something. But it’s no longer dropping my windows laptop and the dhcp log flood stopped.