Please help solve wifi instability

You have two different country codes set, US and DE. try setting it to the same thing

1 Like

I would recommend disabling 802.11r on all of your APs. For some client devices, 802.11r can cause major issues.

And +1 to what @Ramon said about your country codes -- they should be the same and they should be set to your actual country/region.

But thats a function that makes devices easily cross over into a other ap...? I'd rather not lose a function...besides it works good in most areas of the house.
Il try to use the same country code tommorow but i think i did that because of some bug that did not allow a normal channel to be used...

1 Like

It's actually not a necessary standard in many cases. Standard roaming (without 802.11r) can work really well when properly tuned. In fact, I often recommend turning off all of the 'additions' (802.11 k / r / v) and spend a bit of time optimizing the radios for good standard roaming performance first, as it is necessary for this to be working well before adding any of the other standards on top. Then, if you want to make for a (theoretically) improved roaming experience, then add those in. I don't use 802.11r and I have nearly seamless roaming across multiple APs.

2 Likes

Thanks! Can i just disable it, also on the dumb ap's? Or do i have to disable or alter the mesh network then? The external routers are accessable through wireless mesh on a local ip, if i lose access to them with a wrong setting change, its quite some work to grab them and hook them up by a lan cable.
I updated the region settings but that unfortunately did not help.

I think you can just disable 802.11r.... although I'm not an expert on mesh -- I prefer to have all APs hardwired, so that's what I've done in my setups.

I assume that you're actually using mesh, and not confusing the terminology, right? Mesh specifically refers to the use of a wireless backhaul (i.e. one wired AP, the others are wirelessly conneted to the first). Many people think that mesh = roaming and that roaming = mesh. In actuality, client devices will roam from one node to another in a mesh network, but they can also roam from one node to another in a non-meshed network... roaming is simply the client moving between APs. Meshing is the wireless backhaul that makes up the connections between the APs.

I have noticed occasional WiFi firmware crashes in kernel log when WPA3 clients leave/disassociate. I first disabled WPA3 802.11r, and currently trying to test if "WPA2 only" is more stable.

You might try using just WPA2

I just disabled fast roaming on all devices and rebooted. Everything worked fine. Then later the issue started again.
A reboot then fixes it again....
How to proceed now...:thinking:

Where can we find crashes/crash reports?

Dmesg.

I have two wrx36s, with 802.11r enabled, they've been working flawlessly since I flashed them in Jan.

No WPA3 though.

1 Like

E.g. here links to them

.

Also search

Hmm...do you need to repair devices when switching encryption?
I suppose it's worth a try

it does not hurt, to reset the Wifi config once on your client devices, if you had switched from a completely different router HW before.

1 Like

Can you try enabling "Multicast to unicast" on all APs? I would not recommend this normally, but with ath11k it can be much more reliable.

Going from WPA3 to WPA2 ?
No idea.

I already had to, all devices were connected to the router manually already.

i did this on two devices, the main router that i have a lan connection with, and one dumb ap. My devices still connect with wlan, but i lost connection with one dumb AP with the mesh network(also enabled it for mesh...i shouldnt have done that?)
I still have access to the second dumb AP though, where "Multicast to unicast" is disabled on all wireless networks.

EDIT: Enabled it on the second dumb AP on everything except mesh, and it stays connected. First have to reset the settings on the other dumb ap first, which will take me a good hour to grab it from outside and connect it to pc etc.

i see that i am using wpa2'-psk on all wireless networks already...except for the mesh network, that requires wpa3 pretty much.

as for wifi crashes, im pretty sure it is not a total wifi failure because i have many wifi devices that would have shown issues then. i have 5 wifi camera's and they show for example no issues with cloud recording.

whats the next thing to try?

Here is one recent crash from today. (I left to work, and the phone disassociated...)

Mon Sep 11 08:25:16 2023 daemon.info dnsmasq-dhcp[1]: DHCPREQUEST(br-lan) 192.168.1.216 a8:cc:6f:0a:50:f1
Mon Sep 11 08:25:16 2023 daemon.info dnsmasq-dhcp[1]: DHCPACK(br-lan) 192.168.1.216 a8:cc:6f:0a:50:f1 Nokia-X30-5G
Mon Sep 11 08:26:59 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Sep 11 08:26:59 2023 daemon.info hostapd: hn5wpa2r: STA a8:cc:6f:0a:50:f1 IEEE 802.11: associated (aid 2)
Mon Sep 11 08:26:59 2023 daemon.notice hostapd: hn5wpa2r: AP-STA-CONNECTED a8:cc:6f:0a:50:f1 auth_alg=ft
Mon Sep 11 08:27:00 2023 daemon.notice hostapd: hn5wpa2r: AP-STA-DISCONNECTED a8:cc:6f:0a:50:f1
Mon Sep 11 08:27:04 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Sep 11 08:27:04 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Sep 11 08:27:04 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Sep 11 08:27:04 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Sep 11 08:27:04 2023 daemon.notice hostapd: hn5wpa2r: STA a8:cc:6f:0a:50:f1 IEEE 802.11: did not acknowledge authentication response
Mon Sep 11 08:27:04 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Sep 11 08:27:04 2023 daemon.notice hostapd: hn5wpa2r: STA a8:cc:6f:0a:50:f1 IEEE 802.11: did not acknowledge authentication response
Mon Sep 11 08:27:07 2023 daemon.err hostapd: nl80211: kernel reports: key addition failed
Mon Sep 11 08:27:07 2023 daemon.info hostapd: hn5wpa2r: STA a8:cc:6f:0a:50:f1 IEEE 802.11: associated (aid 2)
Mon Sep 11 08:27:07 2023 daemon.notice hostapd: hn5wpa2r: AP-STA-CONNECTED a8:cc:6f:0a:50:f1 auth_alg=ft
Mon Sep 11 08:27:20 2023 daemon.notice hostapd: hn5wpa2r: AP-STA-DISCONNECTED a8:cc:6f:0a:50:f1
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received:
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.9.0.1-01890-QCAHKSWPL_SILICONZ-1
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634]
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] wal_peer_control.c:2904 Assertion is_graceful_to_handle failedparam0 :zero, param1 :zero, param2 :zero.
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] Thread ID      : 0x00000069  Thread name    : WLAN RT0  Process ID     : 0
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] Register:
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] SP : 0x4bfb9340
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] FP : 0x4bfb9348
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] PC : 0x4b1080c4
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] SSR : 0x00000008
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] BADVA : 0x00020000
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] LR : 0x4b107860
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634]
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] Stack Dump
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] from : 0x4bfb9340
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634] to   : 0x4bfb9ba0
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.194634]
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.245370] remoteproc remoteproc0: crash detected in cd00000.q6v5_wcss: type fatal error
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.267586] remoteproc remoteproc0: handling crash #1 in cd00000.q6v5_wcss
Mon Sep 11 08:27:20 2023 kern.err kernel: [216218.275645] remoteproc remoteproc0: recovering cd00000.q6v5_wcss
Mon Sep 11 08:27:20 2023 kern.info kernel: [216218.308306] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.604408] ath11k c000000.wifi: failed to find peer a8:cc:6f:0a:50:f1 on vdev 1 after creation
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.604468] ath11k c000000.wifi: failed to find peer vdev_id 1 addr a8:cc:6f:0a:50:f1 in delete
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.612277] ath11k c000000.wifi: failed peer a8:cc:6f:0a:50:f1 delete vdev_id 1 fallback ret -22
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.621073] ath11k c000000.wifi: Failed to add peer: a8:cc:6f:0a:50:f1 for VDEV: 1
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.629825] ath11k c000000.wifi: Failed to add station: a8:cc:6f:0a:50:f1 for VDEV: 1
Mon Sep 11 08:27:21 2023 daemon.notice hostapd: hn5wpa3: STA a8:cc:6f:0a:50:f1 IEEE 802.11: Could not add STA to kernel driver
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.724436] ath11k c000000.wifi: failed to send WMI_PEER_DELETE cmd
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.724469] ath11k c000000.wifi: failed to delete peer vdev_id 2 addr a8:cc:6f:0a:50:f1 ret -108
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.729859] ath11k c000000.wifi: Failed to delete peer: a8:cc:6f:0a:50:f1 for VDEV: 2
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.738645] ath11k c000000.wifi: Found peer entry 2e:ea:dc:85:e3:3d n vdev 2 after it was supposedly removed
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.746495] ------------[ cut here ]------------
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.756412] WARNING: CPU: 1 PID: 2351 at sta_set_sinfo+0xc44/0xca0 [mac80211]
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.761104] Modules linked in: pppoe ppp_async ath11k_ahb ath11k wireguard pppox ppp_generic nft_redir nft_nat nft_masq nft_flow_offload nft_fib_inet nft_ct nft_chain_nat nf_nat nf_flow_table_inet nf_flow_table nf_conntrack_netlink nf_conntrack mac80211 libchacha20poly1305 ipt_REJECT chacha_neon cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_ecn xt_dscp xt_comment xt_TCPMSS xt_LOG xt_HL xt_DSCP xt_CLASSIFY slhc sch_cake qrtr_smd qrtr qmi_helpers poly1305_neon nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_quota nft_objref nft_numgen nft_log nft_limit nft_hash nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_compat nf_tables nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcurve25519_generic libcrc32c libchacha iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat ntfs3 cls_bpf act_bpf sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_route cls_m
 atchall cls_fw cls_flow cls_basic act_skbedit
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.761381]  act_mirred act_gact xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ipmac ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 msdos ifb ip6_udp_tunnel udp_tunnel sit tunnel4 ip_tunnel tun cifs oid_registry cifs_md4 cifs_arc4 asn1_decoder dns_resolver nls_utf8 nls_iso8859_1 nls_cp437 sha512_generic seqiv jitterentropy_rng drbg michael_mic md5 hmac des_generic cmac usb_storage leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom qca_nss_dp qca_ssdk ramoops reed_solomon pstore gpio_button_hotplug vfat fat ext4 mbcache jbd2 exfat aquantia hwmon crc32c_generic
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.909613] CPU: 1 PID: 2351 Comm: hostapd Not tainted 6.1.51 #0
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.931848] Hardware name: Dynalink DL-WRX36 (DT)
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.937923] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.942615] pc : sta_set_sinfo+0xc44/0xca0 [mac80211]
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.949815] lr : sta_set_sinfo+0xc40/0xca0 [mac80211]
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.954763] sp : ffffffc00a60b880
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.959881] x29: ffffffc00a60b880 x28: ffffff8002223000 x27: ffffffc00a60bdc8
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.963274] x26: ffffff80020aa880 x25: ffffffc008c52900 x24: ffffffc000fb0000
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.970479] x23: ffffffc00a60ba70 x22: ffffff8012d28900 x21: ffffff8014389aa8
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.977684] x20: ffffff8007378880 x19: ffffff8014389000 x18: 00000000000001d4
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.984888] x17: 322076656476206e x16: 2064333a33653a35 x15: ffffffc008b57218
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.992093] x14: 000000000000057c x13: 00000000000001d4 x12: 00000000ffffffea
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216218.999298] x11: 00000000ffffefff x10: ffffffc008baf218 x9 : ffffffc008b571c0
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.006503] x8 : 0000000000000024 x7 : ffffff8014388000 x6 : 0000000000000003
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.013708] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffffff8002223000
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.020912] x2 : 0000000000000000 x1 : ffffff8002223000 x0 : 00000000ffffff94
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.028118] Call trace:
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.035314]  sta_set_sinfo+0xc44/0xca0 [mac80211]
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.038009]  sta_info_destroy_addr_bss+0x50/0x74 [mac80211]
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.042612]  ieee80211_color_change_finish+0x1ac8/0x1d70 [mac80211]
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.048429]  cfg80211_check_station_change+0x11b8/0x4c30 [cfg80211]
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.054766]  genl_family_rcv_msg_doit+0xb8/0x11c
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.061098]  genl_rcv_msg+0x108/0x230
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.065698]  netlink_rcv_skb+0x5c/0x130
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.069343]  genl_rcv+0x38/0x50
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.073421]  netlink_unicast+0x1e8/0x2d4
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.076635]  netlink_sendmsg+0x1a0/0x3d0
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.080542]  ____sys_sendmsg+0x1c8/0x270
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.084535]  ___sys_sendmsg+0x7c/0xc0
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.088527]  __sys_sendmsg+0x48/0xb0
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.092172]  __arm64_sys_sendmsg+0x24/0x30
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.095906]  invoke_syscall.constprop.0+0x5c/0x104
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.099901]  do_el0_svc+0x58/0x17c
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.104759]  el0_svc+0x18/0x54
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.108230]  el0t_64_sync_handler+0xf4/0x120
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.111359]  el0t_64_sync+0x174/0x178
Mon Sep 11 08:27:21 2023 kern.warn kernel: [216219.115871] ---[ end trace 0000000000000000 ]---
Mon Sep 11 08:27:22 2023 kern.warn kernel: [216220.420685] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Mon Sep 11 08:27:25 2023 daemon.info hostapd: hn5wpa2r: STA a8:cc:6f:0a:50:f1 IEEE 802.11: deauthenticated due to local deauth request
Mon Sep 11 08:27:26 2023 kern.err kernel: [216223.564444] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: start timed out
Mon Sep 11 08:27:26 2023 kern.err kernel: [216223.564494] remoteproc remoteproc0: can't start rproc cd00000.q6v5_wcss: -110
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.424618] ath11k_warn: 56 callbacks suppressed
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.424639] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.428330] ath11k c000000.wifi: failed to send pdev bss chan info request
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.436057] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.442736] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.449372] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.455943] ath11k c000000.wifi: failed to submit beacon template command: -108
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.462182] ath11k c000000.wifi: failed to update bcn template: -108
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.469832] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.476181] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Mon Sep 11 08:27:28 2023 kern.warn kernel: [216226.482929] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Mon Sep 11 08:27:34 2023 kern.warn kernel: [216232.490283] ath11k_warn: 59 callbacks suppressed
Mon Sep 11 08:27:34 2023 kern.warn kernel: [216232.490304] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
...

Curiously, one error line has the router's own MAC listed as a peer to be deleted...
Found peer entry 2e:ea:dc:85:e3:3d n vdev 2 after it was supposedly removed
That 2e:ea:dc:85:e3:3d is radio0's MAC, not a peer.