strange, files on the router have different md5sums from your post.
Does it have anything to do with me building my own image ?
edit: just to clarify, I'm talking about the old / original "Build Time: 20221012174" mt firmware files here
I know nothing about building OpenWRT images, so I can't help you there.
The md5sums I posted were from the latest MediaTek firmware files.
[ 6.296094] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20240507160318
[ 6.336985] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20240507160509
1 Like
ok it magically worked this time. I just downloaded the files again, replaced the old ones and rebooted.
1 Like
Glad it worked on the second try! I suspected you had a file or two that must have been corrupted on your previous download. What you experienced on your second try is far more the norm 
2 Likes
Has anyone else experienced any wifi performance issues with recent snapshot builds up through r26308-4341901f05?
I built an updated image last evening at that commit level and kept struggling with my APs not passing data on 5Ghz (I didn't test 2.4Ghz) SSIDs. The APs themselves seemed responsive, but wireless clients would begin a data transmission and within about 3 seconds the speed would trail off to basically 0.
Curious if anyone else has noticed the same or if I'm chasing a ghost here.
My wifi crashed / ssid disappeared and came back 5 mins later. Found the issue to be the Fragmentation and RTS thresholds were set (2346 / 534). I cleared them and the issue went away. Beacon interval setting is fine (103).
This issue happens to all builds / firmwares - 23.05.3, snapshots...
1 Like
Did you upgrade the WiFi firmware? I had an issue with 5ghz and I reverted back to snapshot firmware and havenāt had issues since.
Very interesting--let me look into that! Thanks for the tip.
I have, indeed. I am running this firmware presently:
[ 11.706890] platform 15010000.wed: MTK WED WO Firmware Version: DEV_000000, Build Time: 20240411200554
[ 12.405565] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20240411200401
[ 12.489848] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20240411200542
You might be onto something here. I did start noticing this issue just recently, and the timing could correlate to when I upgraded to this latest firmware. I'll do some testing by rolling back a version or so and see how it looks. Thanks for the pointer!
1 Like
I've been running the MediaTek 20240507 WiFi firmware for a week with no noticeable problems. It's streaming video/music over the 5Ghz for ~5 hours a day with no complaints from anyone in the house.
I'll update if I notice anything.
I did have some interference troubles (latency inconsistencies) with the 160Mhz channels, but that disappeared when I switched to channel 149 80Mhz. I dunno if that has anything to do with the WiFi firmware though.
You can quickly replicate the issue by setting the thresholds, reboot router, and run a internet speedtest on fast.com, speedtest.net or waveform buffer bloat. It will crash during the upload part of the test.
Again this issue is with all firmwares, not just the latest 2024 build.
1 Like
I had the same ( r26307 ? i think, new MT firmware used). Flashed the APās in the evening and the next day wifi just dropped out on everything, no wifi icons on any of the phones. LAN side was fine. Iāll post the log later on
here's a piece of log I collected at the time it happened
Mon May 13 21:05:08 2024 daemon.err uhttpd[1760]: [info] luci: accepted login on / for root from 192.168.0.7
Mon May 13 21:06:08 2024 daemon.notice hostapd: phy1-ap0: STA-OPMODE-N_SS-CHANGED 0e:60:9a:fb:cc:05 2
Mon May 13 21:06:08 2024 daemon.info hostapd: phy1-ap0: STA 0e:60:9a:fb:cc:05 IEEE 802.11: associated (aid 3)
Mon May 13 21:06:08 2024 daemon.notice hostapd: phy1-ap0: AP-STA-CONNECTED 0e:60:9a:fb:cc:05 auth_alg=sae
Mon May 13 21:06:08 2024 daemon.info hostapd: phy1-ap0: STA 0e:60:9a:fb:cc:05 WPA: pairwise key handshake completed (RSN)
Mon May 13 21:06:08 2024 daemon.notice hostapd: phy1-ap0: EAPOL-4WAY-HS-COMPLETED 0e:60:9a:fb:cc:05
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: DFS-RADAR-DETECTED freq=5640 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5610 cf2=0
Mon May 13 21:34:12 2024 daemon.notice hostapd: dfs_downgrade_bandwidth: no DFS channels left, waiting for NOP to finish
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 0e:60:9a:fb:cc:05
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED ec:08:e5:5c:b8:7b
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED 00:04:4b:b7:96:1a
Mon May 13 21:34:12 2024 daemon.err hostapd: 20/40 MHz: center segment 0 (=122) and center freq 1 (=5630) not in sync
Mon May 13 21:34:12 2024 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Mon May 13 21:34:12 2024 kern.info kernel: [127576.762046] mt798x-wmac 18000000.wifi phy1-ap0: left allmulticast mode
Mon May 13 21:34:12 2024 kern.info kernel: [127576.768666] mt798x-wmac 18000000.wifi phy1-ap0: left promiscuous mode
Mon May 13 21:34:12 2024 kern.info kernel: [127576.775264] br-lan: port 6(phy1-ap0) entered disabled state
Mon May 13 21:34:12 2024 daemon.notice netifd: Network device 'phy1-ap0' link is down
Mon May 13 21:34:12 2024 daemon.info avahi-daemon[1861]: Interface phy1-ap0.IPv6 no longer relevant for mDNS.
Mon May 13 21:34:12 2024 daemon.info avahi-daemon[1861]: Leaving mDNS multicast group on interface phy1-ap0.IPv6 with address fe80::9683:c4ff:fea2:b8d5.
Mon May 13 21:34:12 2024 daemon.info avahi-daemon[1861]: Withdrawing address record for fe80::9683:c4ff:fea2:b8d5 on phy1-ap0.
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: interface state ENABLED->DISABLED
Mon May 13 21:34:12 2024 kern.info kernel: [127577.346152] br-lan: port 6(phy1-ap0) entered blocking state
Mon May 13 21:34:12 2024 kern.info kernel: [127577.351830] br-lan: port 6(phy1-ap0) entered disabled state
Mon May 13 21:34:12 2024 kern.info kernel: [127577.357498] mt798x-wmac 18000000.wifi phy1-ap0: entered allmulticast mode
Mon May 13 21:34:12 2024 kern.info kernel: [127577.364514] mt798x-wmac 18000000.wifi phy1-ap0: entered promiscuous mode
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: interface state DISABLED->COUNTRY_UPDATE
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->HT_SCAN
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: DFS-RADAR-DETECTED freq=5640 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5610 cf2=0
Mon May 13 21:34:12 2024 daemon.notice hostapd: dfs_downgrade_bandwidth: no DFS channels left, waiting for NOP to finish
Mon May 13 21:34:12 2024 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Mon May 13 21:34:12 2024 daemon.err hostapd: hostapd_free_hapd_data: Interface phy1-ap0 wasn't started
Mon May 13 21:34:12 2024 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Mon May 13 21:34:12 2024 kern.info kernel: [127577.390865] mt798x-wmac 18000000.wifi phy1-ap0: left allmulticast mode
Mon May 13 21:34:12 2024 kern.info kernel: [127577.397496] mt798x-wmac 18000000.wifi phy1-ap0: left promiscuous mode
Mon May 13 21:34:12 2024 kern.info kernel: [127577.404083] br-lan: port 6(phy1-ap0) entered disabled state
Mon May 13 21:34:13 2024 daemon.notice hostapd: phy1-ap0: interface state HT_SCAN->DISABLED
Mon May 13 21:34:13 2024 kern.info kernel: [127577.603954] br-lan: port 6(phy1-ap0) entered blocking state
Mon May 13 21:34:13 2024 kern.info kernel: [127577.609613] br-lan: port 6(phy1-ap0) entered disabled state
Mon May 13 21:34:13 2024 kern.info kernel: [127577.615315] mt798x-wmac 18000000.wifi phy1-ap0: entered allmulticast mode
Mon May 13 21:34:13 2024 daemon.notice hostapd: phy1-ap0: interface state DISABLED->COUNTRY_UPDATE
Mon May 13 21:34:13 2024 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->HT_SCAN
Mon May 13 21:34:13 2024 kern.info kernel: [127577.622316] mt798x-wmac 18000000.wifi phy1-ap0: entered promiscuous mode
Mon May 13 21:34:13 2024 daemon.err hostapd: could not get valid channel
Mon May 13 21:34:13 2024 daemon.notice hostapd: phy1-ap0: interface state HT_SCAN->DFS
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: DFS-NOP-FINISHED freq=5580 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5580 cf2=0
Mon May 13 22:04:28 2024 daemon.err hostapd: could not get valid channel
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: interface state DFS->DFS
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: DFS-NOP-FINISHED freq=5600 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5600 cf2=0
Mon May 13 22:04:28 2024 daemon.err hostapd: could not get valid channel
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: interface state DFS->DFS
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: DFS-NOP-FINISHED freq=5620 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5620 cf2=0
Mon May 13 22:04:28 2024 daemon.err hostapd: could not get valid channel
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: interface state DFS->DFS
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: DFS-NOP-FINISHED freq=5640 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5640 cf2=0
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: interface state DFS->DFS
Mon May 13 22:04:28 2024 daemon.notice hostapd: phy1-ap0: DFS-CAC-START freq=5640 chan=128 sec_chan=-1, width=0, seg0=122, seg1=0, cac_time=60s
Mon May 13 22:04:28 2024 daemon.err hostapd: 20/40 MHz: center segment 0 (=122) and center freq 1 (=5630) not in sync
Mon May 13 22:04:28 2024 daemon.err hostapd: Can't set freq params
Mon May 13 22:04:28 2024 daemon.err hostapd: DFS start_dfs_cac() failed <
It seems to me that something is going wrong with the channel selection (?)
I have two of these MT6000s. One upstairs one down.
Using 802.11r fast transition on both of these devices. I have the full WPAD installed on both devices.
Occasionally, I'll log in and see no clients connected to my downstairs DUMBAP. When i see this it usually means some of my nest smokes are offline, and Shelly devices have gone AWOL as well. It's as if the AP is still advertising the wireless but not allowing any connections.
I think the only thing I've tweaked is the station inactivity limit to 900. 300 seems a little aggressive for some devices on my network and 900 seemed like a nice compromise.... 5 to 15 minutes?
I am capturing all the logs from my OpenWRTs. Nothing really special to report ont he logs. Most of the devices seem to get kicked for inactivity though. It's as if they can't respond or the AP never sees a response and just kicks everyone off for inactivity.
I just rolled back from yesterday's snap to r26305. It seemed like I had a little better luck with that on my dumb AP.
This never happens on my OpenWRT that also is connected to my cable internet. just the DumbAP it seems.
Perfectly willing to bet it's something on my end that is misconfigured.... but I thought it might be worth mentioning here.
1 Like
So much great feedback hereāthanks one, and all!
I realized last night (tired eyes?) that I wrote that I was running the MT 20240411 firmware, and that was true. But that is not the latest, contrary to what I even posted back here: GL.iNET Flint 2 (GL-MT6000) Snapshot / Experimental / Bleeding Edge - #2 by _FailSafe 
sighā¦ So I did roll my FW back and things seem stable and āproperā on the snapshot firmware now. Today I will go forward to the 20240507 firmware again (where I meant to be before) and see if the WiFi stall issue begins to reoccur.
Thanks for the inputs while I get this sorted. Hopefully this will help others too!
Hey all, I found some bugs in my previous get-mt7986-fw.sh script that kept it from working properly on Linux. This updated script has been tested now on MacOS (Darwin) and Linux (Ubuntu), and it's working correctly for both OS types:
3 Likes
My situation is nearly the same, I've got three MT6000 as dumb AP's separately wired to the main router / firewall. Using 802.11r fast transition too with no other setting on all three. I'm on the r26280 snapshot and it seemed to be fine till today when WiFi got an heart stroke again. Connection was dropped on all devices and I couldn't connect to any of the three AP's. It was like WiFi was turned off.
I think something is not right with the selected DFS channels. I read a Radar Detection in logs but we do not have a airport near here. Weird situation
Here is a piece of the todays log again;
Thu May 16 15:19:39 2024 daemon.notice hostapd: phy1-ap0: DFS-RADAR-DETECTED freq=5620 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5610 cf2=0
Thu May 16 15:19:39 2024 daemon.notice hostapd: dfs_downgrade_bandwidth: no DFS channels left, waiting for NOP to finish
Thu May 16 15:19:39 2024 daemon.notice hostapd: phy1-ap0: AP-DISABLED
Thu May 16 15:19:39 2024 daemon.notice hostapd: phy1-ap0: AP-STA-DISCONNECTED c4:18:e9:9c:66:7d
Thu May 16 15:19:39 2024 daemon.err hostapd: 20/40 MHz: center segment 0 (=122) and center freq 1 (=5630) not in sync
Thu May 16 15:19:39 2024 daemon.notice hostapd: nl80211: deinit ifname=phy1-ap0 disabled_11b_rates=0
Thu May 16 15:19:39 2024 kern.info kernel: [154272.929309] mt798x-wmac 18000000.wifi phy1-ap0: left allmulticast mode
Thu May 16 15:19:39 2024 kern.info kernel: [154272.935932] mt798x-wmac 18000000.wifi phy1-ap0: left promiscuous mode
Thu May 16 15:19:39 2024 kern.info kernel: [154272.942534] br-lan: port 7(phy1-ap0) entered disabled state
Thu May 16 15:19:40 2024 daemon.notice netifd: Network device 'phy1-ap0' link is down
Thu May 16 15:19:40 2024 daemon.info avahi-daemon[2117]: Interface phy1-ap0.IPv6 no longer relevant for mDNS.
Thu May 16 15:19:40 2024 daemon.info avahi-daemon[2117]: Leaving mDNS multicast group on interface phy1-ap0.IPv6 with address fe80::9683:c4ff:fea2:b759.
Thu May 16 15:19:40 2024 daemon.info avahi-daemon[2117]: Withdrawing address record for fe80::9683:c4ff:fea2:b759 on phy1-ap0.
Thu May 16 15:19:40 2024 daemon.notice hostapd: phy1-ap0: interface state ENABLED->DISABLED
Thu May 16 15:19:40 2024 kern.info kernel: [154273.283326] br-lan: port 6(phy1-ap0) entered blocking state
Thu May 16 15:19:40 2024 kern.info kernel: [154273.289006] br-lan: port 6(phy1-ap0) entered disabled state
Thu May 16 15:19:40 2024 kern.info kernel: [154273.294677] mt798x-wmac 18000000.wifi phy1-ap0: entered allmulticast mode
Thu May 16 15:19:40 2024 daemon.notice hostapd: phy1-ap0: interface state DISABLED->COUNTRY_UPDATE
Thu May 16 15:19:40 2024 kern.info kernel: [154273.301686] mt798x-wmac 18000000.wifi phy1-ap0: entered promiscuous mode
Thu May 16 15:19:40 2024 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->HT_SCAN
Thu May 16 15:19:40 2024 daemon.err hostapd: could not get valid channel
Thu May 16 15:19:40 2024 daemon.notice hostapd: phy1-ap0: interface state HT_SCAN->DFS
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: DFS-NOP-FINISHED freq=5580 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5580 cf2=0
Thu May 16 15:50:18 2024 daemon.err hostapd: could not get valid channel
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: interface state DFS->DFS
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: DFS-NOP-FINISHED freq=5600 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5600 cf2=0
Thu May 16 15:50:18 2024 daemon.err hostapd: could not get valid channel
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: interface state DFS->DFS
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: DFS-NOP-FINISHED freq=5620 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5620 cf2=0
Thu May 16 15:50:18 2024 daemon.err hostapd: could not get valid channel
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: interface state DFS->DFS
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: DFS-NOP-FINISHED freq=5640 ht_enabled=0 chan_offset=0 chan_width=0 cf1=5640 cf2=0
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: interface state DFS->DFS
Thu May 16 15:50:18 2024 daemon.notice hostapd: phy1-ap0: DFS-CAC-START freq=5620 chan=124 sec_chan=1, width=0, seg0=122, seg1=0, cac_time=60s
Thu May 16 15:50:18 2024 daemon.err hostapd: 20/40 MHz: center segment 0 (=122) and center freq 1 (=5630) not in sync
Thu May 16 15:50:18 2024 daemon.err hostapd: Can't set freq params
Thu May 16 15:50:18 2024 daemon.err hostapd: DFS start_dfs_cac() failed, -1
Thu May 16 17:10:22 2024 daemon.err uhttpd[2016]: [info] luci: accepted login on / for root from 192.168.1.78
Could you confirm which MT firmware version you're running presently?
1 Like
I'm on SNAPSHOT r26280-8113169cad
What's the output of this command? dmesg | grep -i firmware
running the old firmware.
root@Skynet:~# dmesg | grep -i firmware
[ 0.000000] psci: PSCIv1.1 detected in firmware.
[ 10.126239] mt798x-wmac 18000000.wifi: WM Firmware Version: ____000000, Build Time: 20221012174725
[ 10.210377] mt798x-wmac 18000000.wifi: WA Firmware Version: DEV_000000, Build Time: 20221012174937>
I think our issues are different. I just disabled Disassociate ON Low Acknowledgement on DUMBAP and it seems to have cleared it up. At least my Nest Smokes aren't dropping like flies.
Did you set your country code on the SSID > Advanced Settings?