Do you want to do some more bisecting? This one sounds a lot slower than last time, but that should not be a deterrent.
What version are you running?
Running the 11/30/21 master snapshot which includes these mac80211 fixes and can confirm 5GHz is running great on my WRT32X. Not a single issue in 3 days. I see there have been a few more mac80211 fixes in the commits now and look forward to testing those next time I update as well. Thank you so much to those that put in the time for these fixes.
As an aside, I generally disable wifi on the router outside of testing and use the $99 Ubiquiti U6-Lite-US. Although it takes up one of the gigabit switch ports it's significantly faster and provides all the new goodies like WiFi 6, OFDMA, TWT, MU-MIMO, Mesh, single login for all bands with bandstearing, etc.
The mvebu target and specifically the WRT32X / WRT3200ACM is an outstanding fast performing router for everything else, running SQM at 500 Mb/s, Adblock, USB 3.0 NAS w/Samba4 at 120 MB/s, etc.
Below are my packages installed for those curious:
Summary
opkg update && opkg install luci irqbalance luci-app-advanced-reboot luci-app-sqm luci-app-adblock luci-app-upnp luci-app-wireguard luci-app-samba4 kmod-usb3 kmod-ata-marvell-sata kmod-usb-storage kmod-usb-storage-uas block-mount usbutils mount-utils luci-app-hd-idle kmod-fs-exfat iperf3 nano
Hmm...has anyone managed to get radio2 working with this change/newist builds? If I flip back (I think to 5.10.74) radio2 works, but I can't seem to get it to start up under any config anymore.
root@OpenWrt:/etc/modules.d# hostapd /var/run/hostapd-phy2.conf
nl80211: kernel reports: Registration to specific type not supported
Failed to initialize QoS Map
Interface initialization failed
wlan2: interface state UNINITIALIZED->DISABLED
wlan2: AP-DISABLED
wlan2: Unable to setup interface.
wlan2: interface state DISABLED->DISABLED
wlan2: AP-DISABLED
wlan2: CTRL-EVENT-TERMINATING
hostapd_free_hapd_data: Interface wlan2 wasn't started
nl80211: deinit ifname=wlan2 disabled_11b_rates=0
ELOOP: remaining socket: sock=18 eloop_data=0xb6c2ec30 user_data=0 handler=0x4f5c8c
You'll need to set iw_qos_map_set to none, as @dgilman posted above. However, this should be set in radio2's wifi-iface:
config wifi-device 'radio2'
option type 'mac80211'
option path 'platform/soc/soc:internal-regs/f10d8000.sdhci/mmc_host/mmc0/mmc0:0001/mmc0:0001:1'
option country 'US'
option band '5g'
option channel '36'
option htmode 'HT20'
option cell_density '0'
config wifi-iface 'default_radio2'
option device 'radio2'
option network 'lan'
option mode 'ap'
option ssid 'OpenWrt'
option encryption 'none'
option iw_qos_map_set 'none'
1 Like
I am running 21.02.1 currently. To be honest, I don’t think we need to do bisecting yet because I need to gather more details. I am actually thinking now that this is a previously known mwlwifi issue where the 5GHz band just craps out and stops working for any devices on that band. The 2.4GHz band continues fine.
So I don’t think this is an issue specific to your patch.
I tried the wifi command this time hoping that it would recover the 5GHz band but it did not. The only way to recover the 5GHz band was a full reboot of the router.
For now, I think I will just keep my wife on the 2.4GHz band because she has been getting frustrated with it.
@WildByDesign , the following could be yet another issue, but even going back to David's last build (I haven't tested anything newer yet), I've experienced a weird issue on a WRT1200AC where if I applied certain settings on the 2.4GHz radio, the 5GHz radio would die and I'd have to reboot the router to get it working again. This could just be a separate bug, but what you wrote reminded me of it. When I have a chance to test these latest builds, I'll follow up on this.
1 Like
Awesome, that worked great! Wasn't sure that was the case to even activate the interface; I use radio2 for IoT devices; still need to enable legacy 802.11b to be able to activate but other than that it looks good!
master did not fix my iPhone issue. I guess it's a bug with mt76.
looks like mwlwifi compiled from master today is not able to work as sta+ap on 5ghz radio.
edit: sorry my mistake, need edit the mac address of ap interface
so, I noticed one other issue with ARP on devices which are connected to the same WLAN after some time (~1day working).
But meanwhile ARP is working between devices connected to different interfaces(WLAN, Ethernet)
The picture is next:
- Devices connected to WLAN(5GHz) DO NOT respond to ARP requests from devices on the same WLAN(5GHz)
- Devices connected via ethernet respond to any ARP requests from WLAN(5GHz) or WLAN(2.4GHz) and vice versa!
- Devices connected to WLAN(2.4GHz) respond to ARP requests from devices connected to WLAN(5GHz)
@mmortal03 could it be related to the used master snapshot instead of 21.02?
@stamak , I plan on testing both snapshots, but haven't had the chance yet (my WRT1200AC is at another house in the family, so there hasn't been a good opportunity to test it yet). Are you asking about your ARP issue? I can't say -- all I can suggest is that you try that 21.02 snapshot and see if you get the same result as with the master! Let me PM you.
1 Like
Same for WRT1900ACS, do you also experience problems with Ethernet with latest snapshots or 21.02?
I think I have the same problem also with an iPhone.
also station wds mode after one day was down. need check regular station.
The major bug discussed in this thread has already had a fix included in recent masters and the 21.02 daily snapshots (hidden directory, not the official release), so you'll just need to test those first if you can't wait for the next official point release, and then get back with people here if you still have problems.
See my previous post for what to do. No, I haven't personally tested the builds with the fix included yet.
Tested the 21.02 snapshot from December 5th and wifi is working a lot better than in Openwrt 19. I used to start and stop the 5GHz wifi several times before it became active. With version 21.02 it will start correctly everytime. Wifi keeps accessable with several Apple devices (iPhone Xs, 6s, iPad Pro 2017, iPad Air 2020).
The only problem is I ended up with a read-only file system. It never happened with stable builds.
1 Like
This is probably the answer, but hopefully someone with more experience with testing snapshot builds can confirm. At least we know it'll be good on next official release: Updating base-files remounts root as readonly and update fails - #7 by hnyman
Bad news. I've tested out the nightly builds for 21.02 (commit 2e5b2ab) and it still has an issue where the iPhone is unable to connect to the network.
For this latest test, I updated OpenWRT on the router in the AM, and the iPhone was physically out of the building for about 4 hours. Everything was working fine. The logs don't show anything interesting, except for a radar detected by firmware in the first half hour or so of it being up, and a DFS-NOP-FINISHED thirty minutes later. In response to the DFS channel switch three devices had to reconnect to the network but I think this is typical?
When the iPhone came into the building it was unable to connect to the wifi at all. Thinking that maybe it was some issue with DFS and switching I forced the wifi to channel 149 to avoid DFS. This let the iPhone re-join the network right away. I will keep an eye on it for the next day or so to see how well channel 149 does.
Yes, this is expected behavior, as mandated by regulations.
Perhaps your router changed to a channel forbidden in your region?
1 Like