I saw @psherman's note requesting patience while build queues drain after a release. Are there any expected timelines for publishing the 21.02.3 Docker images? Where do the Docker image builds typically land within the post-release build queue?
Netgear R7800 upgraded from 21.02.2 to 21.02.3; configuration settings retained.
Upgrade was unevenful and everything works. Thank you!
Actually I do have an issue after upgrading on my 2xR7800. Seems both radios "crash" after some BSS-TM-RSP notice from hostapd. They do come back up after ~15 seconds. I thought it might be related to dawn. I switched to usteer, but exactly the same thing happens.
Does anybody have any idea what the issue is?
Thank you,
Ramon
2022-04-25 11:12:01 notice hostapd[]: wlan1-1: BSS-TM-RESP 30:xx:xx:xx:xx:xx status_code=7 bss_termination_delay=0
2022-04-25 11:12:01 notice netifd[]: Network device 'wlan0-1' link is down
2022-04-25 11:12:01 info kernel[]: [169177.152762] br-lan: port 3(wlan0-1) entered disabled state
2022-04-25 11:12:02 warning netifd[]: Wireless device 'radio1' setup failed, retry=3
2022-04-25 11:12:02 warning netifd[]: Wireless device 'radio0' setup failed, retry=3
2022-04-25 11:12:02 info kernel[]: [169177.432727] ath10k_pci 0001:01:00.0: mac flush null vif, drop 0 queues 0xffff
2022-04-25 11:12:02 notice netifd[]: radio1 (10799): Command failed: Not found
2022-04-25 11:12:02 notice netifd[]: radio0 (10800): Command failed: Not found
2022-04-25 11:12:02 warning kernel[]: [169177.504232] ath10k_pci 0000:01:00.0: could not get mac80211 beacon, vdev_id: 0 addr: bc:xx:xx:xx:xx:xx
2022-04-25 11:12:02 info avahi-daemon[1756]: Interface wlan1-1.IPv6 no longer relevant for mDNS.
2022-04-25 11:12:02 info avahi-daemon[1756]: Leaving mDNS multicast group on interface wlan1-1.IPv6 with address fe80::xxx:xxx:xxx:xx6d.
2022-04-25 11:12:02 notice netifd[]: Network device 'wlan1-1' link is down
2022-04-25 11:12:02 warning kernel[]: [169177.523314] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
2022-04-25 11:12:02 warning kernel[]: [169177.523389] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
2022-04-25 11:12:02 info kernel[]: [169177.529793] br-lan: port 2(wlan1-1) entered disabled state
2022-04-25 11:12:02 info kernel[]: [169177.532608] ath10k_pci 0000:01:00.0: mac flush null vif, drop 0 queues 0xffff
2022-04-25 11:12:02 info kernel[]: [169177.534904] device wlan1-1 left promiscuous mode
2022-04-25 11:12:02 info kernel[]: [169177.534913] br-lan: port 2(wlan1-1) entered disabled state
2022-04-25 11:12:02 warning kernel[]: [169177.663597] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
2022-04-25 11:12:02 warning kernel[]: [169177.663687] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
2022-04-25 11:12:02 info kernel[]: [169177.669928] br-lan: port 3(wlan0-1) entered disabled state
2022-04-25 11:12:02 info kernel[]: [169177.677803] device wlan0-1 left promiscuous mode
2022-04-25 11:12:02 info kernel[]: [169177.677816] br-lan: port 3(wlan0-1) entered disabled state
2022-04-25 11:12:02 warning kernel[]: [169177.774365] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
2022-04-25 11:12:02 warning kernel[]: [169177.774403] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
2022-04-25 11:12:02 info kernel[]: [169177.858143] br-guest: port 2(wlan0) entered disabled state
2022-04-25 11:12:02 warning kernel[]: [169177.863227] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
2022-04-25 11:12:02 warning kernel[]: [169177.863329] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
2022-04-25 11:12:02 info kernel[]: [169177.948873] br-guest: port 3(wlan1) entered disabled state
2022-04-25 11:12:02 info avahi-daemon[1756]: Withdrawing address record for fe80::xxxx:xxxx:xxxx:xx6d on wlan1-1.
2022-04-25 11:12:02 info avahi-daemon[1756]: Interface wlan0-1.IPv6 no longer relevant for mDNS.
2022-04-25 11:12:02 info avahi-daemon[1756]: Leaving mDNS multicast group on interface wlan0-1.IPv6 with address fe80::xxxx:xxxx:xxxx:xx6d.
2022-04-25 11:12:02 info avahi-daemon[1756]: Withdrawing address record for fe80::xxxx:xxxx:xxxx:xx6c on wlan0-1.
2022-04-25 11:12:02 info avahi-daemon[1756]: Interface wlan0.IPv6 no longer relevant for mDNS.
2022-04-25 11:12:02 info avahi-daemon[1756]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::xxxx:xxxx:xxxx:xx6c.
2022-04-25 11:12:02 info avahi-daemon[1756]: Withdrawing address record for fe80::xxxx:xxxx:xxxx:xx6c on wlan0.
2022-04-25 11:12:02 info avahi-daemon[1756]: Interface wlan1.IPv6 no longer relevant for mDNS.
2022-04-25 11:12:02 info avahi-daemon[1756]: Leaving mDNS multicast group on interface wlan1.IPv6 with address fe80::xxxx:xxxx:xxxx:xx6d.
2022-04-25 11:12:02 info avahi-daemon[1756]: Withdrawing address record for fe80::xxxx:xxxx:xxxx:xx6d on wlan1.
2022-04-25 11:12:02 notice netifd[]: Network device 'wlan0' link is down
2022-04-25 11:12:02 notice netifd[]: Network device 'wlan1' link is down
2022-04-25 11:12:02 info kernel[]: [169177.993206] device wlan0 left promiscuous mode
2022-04-25 11:12:02 info kernel[]: [169177.993233] br-guest: port 2(wlan0) entered disabled state
2022-04-25 11:12:02 info kernel[]: [169178.123104] device wlan1 left promiscuous mode
2022-04-25 11:12:02 info kernel[]: [169178.123129] br-guest: port 3(wlan1) entered disabled state
2022-04-25 11:12:03 notice netifd[]: Wireless device 'radio0' is now down
2022-04-25 11:12:03 notice netifd[]: Wireless device 'radio1' is now down
2022-04-25 11:12:03 notice hostapd[]: Configuration file: /var/run/hostapd-phy0.conf (phy wlan0) --> new PHY
2022-04-25 11:12:09 warning kernel[]: [169184.627330] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
2022-04-25 11:12:09 warning kernel[]: [169184.627357] ath10k_pci 0000:01:00.0: msdu-desc: 2500 skid: 32
2022-04-25 11:12:09 info kernel[]: [169184.709380] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
2022-04-25 11:12:09 info kernel[]: [169184.710203] ath10k_pci 0000:01:00.0: wmi print 'free: 84920 iram: 13156 sram: 11224'
2022-04-25 11:12:09 notice hostapd[]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
2022-04-25 11:12:09 notice hostapd[]: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
2022-04-25 11:12:09 info kernel[]: [169185.084050] ath10k_pci 0000:01:00.0: rts threshold 500
2022-04-25 11:12:09 warning kernel[]: [169185.084300] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
2022-04-25 11:12:09 info kernel[]: [169185.087859] br-guest: port 2(wlan0) entered blocking state
2022-04-25 11:12:09 info kernel[]: [169185.087871] br-guest: port 2(wlan0) entered disabled state
2022-04-25 11:12:09 info kernel[]: [169185.088095] device wlan0 entered promiscuous mode
2022-04-25 11:12:09 notice hostapd[]: Configuration file: /var/run/hostapd-phy1.conf (phy wlan1) --> new PHY
2022-04-25 11:12:11 notice netifd[]: Wireless device 'radio0' is now up
2022-04-25 11:12:15 warning kernel[]: [169191.048871] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16 peers: 48 tid: 96
2022-04-25 11:12:15 warning kernel[]: [169191.048898] ath10k_pci 0001:01:00.0: msdu-desc: 2500 skid: 32
2022-04-25 11:12:15 info kernel[]: [169191.132946] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186 msdu-desc: 2500 sw-crypt: 0 ct-sta: 0'
2022-04-25 11:12:15 info kernel[]: [169191.133809] ath10k_pci 0001:01:00.0: wmi print 'free: 84920 iram: 13156 sram: 11224'
2022-04-25 11:12:16 info kernel[]: [169191.792759] ath10k_pci 0001:01:00.0: rts threshold 500
2022-04-25 11:12:16 warning kernel[]: [169191.793485] ath10k_pci 0001:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
2022-04-25 11:12:16 notice hostapd[]: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
2022-04-25 11:12:16 info kernel[]: [169191.802700] br-guest: port 3(wlan1) entered blocking state
2022-04-25 11:12:16 info kernel[]: [169191.802708] br-guest: port 3(wlan1) entered disabled state
2022-04-25 11:12:16 info kernel[]: [169191.802869] device wlan1 entered promiscuous mode
2022-04-25 11:12:17 info kernel[]: [169192.202497] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
2022-04-25 11:12:17 info kernel[]: [169192.202620] br-guest: port 3(wlan1) entered blocking state
2022-04-25 11:12:17 info kernel[]: [169192.202628] br-guest: port 3(wlan1) entered listening state
2022-04-25 11:12:17 notice netifd[]: Network device 'wlan1-1' link is up
2022-04-25 11:12:17 info kernel[]: [169192.208047] br-lan: port 2(wlan1-1) entered blocking state
2022-04-25 11:12:17 info kernel[]: [169192.208056] br-lan: port 2(wlan1-1) entered disabled state
2022-04-25 11:12:17 info kernel[]: [169192.208198] device wlan1-1 entered promiscuous mode
2022-04-25 11:12:17 info kernel[]: [169192.211489] ath10k_pci 0001:01:00.0: rts threshold 500
2022-04-25 11:12:17 notice netifd[]: Network device 'wlan1-1' link is down
2022-04-25 11:12:17 info kernel[]: [169192.219736] br-lan: port 2(wlan1-1) entered blocking state
2022-04-25 11:12:17 info kernel[]: [169192.219746] br-lan: port 2(wlan1-1) entered listening state
2022-04-25 11:12:17 notice netifd[]: Network device 'wlan1-1' link is up
2022-04-25 11:12:17 notice hostapd[]: wlan1: interface state COUNTRY_UPDATE->ENABLED
2022-04-25 11:12:17 notice hostapd[]: wlan1: AP-ENABLED
2022-04-25 11:12:17 info kernel[]: [169192.342979] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
2022-04-25 11:12:17 notice netifd[]: Network device 'wlan0' link is up
2022-04-25 11:12:17 info kernel[]: [169192.718400] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
2022-04-25 11:12:17 info kernel[]: [169192.718597] br-guest: port 2(wlan0) entered blocking state
2022-04-25 11:12:17 info kernel[]: [169192.718612] br-guest: port 2(wlan0) entered listening state
2022-04-25 11:12:17 notice netifd[]: Network device 'wlan0-1' link is up
2022-04-25 11:12:17 info kernel[]: [169192.725348] br-lan: port 3(wlan0-1) entered blocking state
2022-04-25 11:12:17 info kernel[]: [169192.725361] br-lan: port 3(wlan0-1) entered disabled state
2022-04-25 11:12:17 info kernel[]: [169192.725624] device wlan0-1 entered promiscuous mode
2022-04-25 11:12:17 info kernel[]: [169192.727708] ath10k_pci 0000:01:00.0: rts threshold 500
2022-04-25 11:12:17 notice netifd[]: Network device 'wlan0-1' link is down
2022-04-25 11:12:17 info kernel[]: [169192.740577] br-lan: port 3(wlan0-1) entered blocking state
2022-04-25 11:12:17 info kernel[]: [169192.740588] br-lan: port 3(wlan0-1) entered listening state
2022-04-25 11:12:17 info kernel[]: [169192.802337] br-lan: port 3(wlan0-1) entered disabled state
2022-04-25 11:12:17 info kernel[]: [169192.842980] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
2022-04-25 11:12:17 info kernel[]: [169192.843121] br-lan: port 3(wlan0-1) entered blocking state
2022-04-25 11:12:17 info kernel[]: [169192.843129] br-lan: port 3(wlan0-1) entered listening state
2022-04-25 11:12:17 notice netifd[]: Network device 'wlan0-1' link is up
2022-04-25 11:12:17 notice hostapd[]: wlan0: interface state HT_SCAN->ENABLED
2022-04-25 11:12:17 notice hostapd[]: wlan0: AP-ENABLED
2022-04-25 11:12:18 notice netifd[]: Wireless device 'radio1' is now up
2022-04-25 11:12:18 notice netifd[]: Network device 'wlan1' link is up
Thanks for releasing!
Stably running on WRT3200ACM.
1 Like
I see my wan dropping out frequently, for a 3-5 seconds at a time. There is no pattern to frequency, it happens overnight and during the day. Sometimes it happens once every 4 hours, sometimes every hour, and sometimes 2-3 times in an hour. All hardware is connected to a UPS so power is not the issue.
Can I increase the verbosity level to get a better idea of what is going on? Any other suggestions(wondering if something is wrong with the cable modem)?
I am using OpenWRT v21.02.3 on a WRT3200ACM.
This is what it looks like in the logs:
Wed Apr 27 07:06:13 2022 daemon.notice netifd: Network device 'wan' link is down
Wed Apr 27 07:06:13 2022 daemon.notice netifd: Interface 'wan' has link connectivity loss
Wed Apr 27 07:06:13 2022 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Wed Apr 27 07:06:13 2022 kern.info kernel: [407256.445892] mv88e6085 f1072004.mdio-mii:00 wan: Link is Down
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan6 (32152): Command failed: Permission denied
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): udhcpc: received SIGTERM
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): udhcpc: unicasting a release of 99.xxx.xx.xx to 99.xxx.xx.xx
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): udhcpc: sending release
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): udhcpc: entering released state
Wed Apr 27 07:06:13 2022 daemon.notice netifd: wan (32151): Command failed: Permission denied
Wed Apr 27 07:06:13 2022 daemon.notice netifd: Interface 'wan' is now down
Wed Apr 27 07:06:14 2022 daemon.notice netifd: Interface 'wan6' is now down
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Network device 'wan' link is up
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Interface 'wan' has link connectivity
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Interface 'wan' is setting up now
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Interface 'wan6' has link connectivity
Wed Apr 27 07:06:18 2022 daemon.notice netifd: Interface 'wan6' is setting up now
1 Like
I also experienced similar frequent connectivity issues, same router model. Although I assumed that wireless was the culprit without digging into it further. I will switch back over to my 21.02.3 partition and see if I have similar logged events.
Stable as wifi 6 access point from Totolink X5000R, just delete the wan interface and drag it to br-lan device. Delete dnsmasq, odhcpd-ipv6only, dropbear, etc.
I use DD-WRT still as the VPN router.
I think there is a bug in hostapd handling of that message. This is a report of the same: Pagefault error - Possibly DAWN related
DEVICE_CLAIM_FAILED error has been due to timeout issues with netifd and driver timing out too quickly and thus not notifying the ubus changes sync
On my gitlab https://gitlab.com/db260179/openwrt-netifd/-/commit/c5ea57c9ec7a296a1cdafc5ca8cdc1a1a1e7990c
Fixed wireless auto channel scanning.
Needs a better fix, maybe felix can get a proper fix on this?
Thx! And yes must be some error handling going wrong. On that link the error is slightly different though.
I do think the original fault is hopefully gone, because when testing out usteer i followed [OpenWrt Wiki] Setting up usteer and band-steering in OpenWrt. That mentioned putting the time_zone to GMT0. I did that because i though that was required, but that did not work (as I indicated above), but it got me thinking that the actualy error maybe its related to that. So instead of GMT0 I put in the exact string of /etc/TZ. Seems to be ok now, although would be good if that error handling bug gets fixed as crashing the whole wireless is a bit drastic.
I have a small issue with Netgear Nighthawk X4S R7800 router
Why is there a red light on port 4?
It is since upgrade
There is no error in dmesg and kernel log
The vlan thing not detecting my lan port and not receiving packets in my Mi router 4A gigabit edition is not fix yet in this version, but in 22.03.0-rc1 they fixed it there
I get red light on R7800 on some cases when there is a connected cable, but the device is turned off. E.g. my NAS causes a red LED when turned off. When NAS is on, the light is normal white.
1 Like
With Netgear's default setup,
Orange/red light can be triggered by a device connecting at 100 Mb/s rather than 1000 Mb/s.
I also encountered it when a failing network cable/plug was in use.
You can easily test it out by unplugging the existing network cable out of port 4
and
Plugging in one of the cables from port 1, 2 or 3 and see if the LED changes to white.
4 Likes
This is awesome and a game changer. Upgraded 3 routers with this method, one of which is a wireless bridge running relayd that i was not looking forward to dismounting from it's location. Everything worked perfectly. Thank you for this tidbit of info.
1 x Linksys WRT1900AC v1
2 x Netgear WNDR3800
Is there any wifi issues on the R6220(both 2.4Ghz and 5Ghz)?
All over is it stable?
Hi.
None, very stable. I have/use several devices as routers or AP.
Nevertheless I have moved all these devices to 22.03. One is even running on master snapshot.
Are you having issus with RealTek Fast Ethernet controller enabled devices. I am having issues where devices shows "Ethernet cable unplugged" and log shows something like below
The only way I found to fix this is by manually restarting the LAN interface(on the router) and turing off ARP off load and flow control from windows device manager.
Also I have 2.4Ghz device which show "wifi connected, but no internet" every 13-25mins of usage. Only disconnecting and reconnection helps, but no permanent fix. Device using is R6220.
I have not encountered any issues with the LAN nor ̶W̶i̶F̶i̶.
The 2.4GHz never had issues. It was 5 GHz that had problems with combo stated in previous stable releases.
Reminder that your R6220 is not MediaTek MT7621AT/MT7615N combo that I mentioned.
R6220 has MediaTek MT7621ST/MT7603EN combination
EDIT: Spoke too soon.
After 9 days, encountered same bug where 5 GHz connected to router without any issues, signal strength was excellent but failed to navigate/open any webpages.
Android phone displays Address Not Found
Took a quick look at the system log, nothing indicating problem.
Used android phone without any problems, it went to sleep mode due to inactivity, approximately 7 minutes later, attempted to connect/use Firefox, it displayed error stated above.
Second time error encountered within four hours.
Router: D-Link DIR-878 rev.A1
1 Like
Looks like the 21.02.3 Docker images are published now and the Github release for 21.02.3 has also been created.
So a possible answer to my own question is that Docker images will be published around the time the official Github release is created for the same version.