One was configured as AP and the other in Router mode. Which version are you running currently?
Honestly, with the stock firmware, I don't have to do any config and the devices roam fine. Hence the question. I understand the factors that you have called out.
Since roaming is a client decision, the client simply chose to stick to the current AP which complicates the situation.
I would say that there is more than enough overlap between the two routers making it complicated.
Yeah, this is a tricky situation at times because various devices have different roaming thresholds. Not sure what kind of client devices you have, but Apple publishes their roaming criteria, for example. But even Apple has differing candidate selection criteria based on band and signal level.
My recommendation is generally the KISS approach. By keeping it simple and starting with turning power down methodically on each AP, you can generally achieve a pretty acceptable outcome. If you have a device that gives real-time (or very close to it) signal/noise level feedback, then take that device around your dwelling and check (and tune!!!) signal overlap between your APs at your primary usage spots. Too often people leave AP power cranked up as high as possible thinking more power == more speed (or some fallacy like that). I get where people think more power == more range, but TX power from the AP is only half the equation, so to speak. And a long range, but weak signal with high noise is not going to be very useful.
If after that, your clients still arenāt roaming in the way you expect or desire, then move toward the steering tools (dawn or usteer). IMHO, Dawn āfeelsā heavier on my APs, so Iāve gravitated toward Usteer. But, with either tool, you can make an acceptable situation worse if you simply install them and walk away. Theyāre not magical, one-click fixes that I often see people think. If you donāt take the time to really learn and understand each setting, the solution will be sub-par at best and counterproductive at worst.
Again, this is all my opinion on approach, but is grounded in countless hours (across many days, weeks, months, etc) of experience and trial & error.
Using one as router/AP and other as AP complicates things. One configured as router will indeed be able use SQM for outgoing WAN link. (Enabling software offload will disable SQM though.)
But none of this has anything to do with WiFi roaming. Roaming is strictly on WiFi/LAN side.
I am only using WPA3 and 5GHz network and all my devices are Apple products. Also, all my AP's have different channels in order not to overlap each other. This has worked fine with my previous Archer C7's and continues to work fine with AX3600.
I have updated OpenWRT versions multiple times.
1 Like
OK, after 1 month atk11k crashed.n Dev thread seems to be closed so I will paste crash dump here. Reboot solved the issue. (Just restarting the wireless did not help)
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: fatal error received:
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.5.0.1-01208-QCAHKSWPL_SILICONZ-1
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] Image Variant : IMAGE_VARIANT_STRING=8074.wlanfw.eval_v2Q
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] NOC_error.c:474 NOCError: FATAL ERRORparam0 :zero, param1 :zero, param2 :zero.
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] Thread ID : 0x0000006f Thread name : ABTIST182 Process ID : 0
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] Register:
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] SP : 0x4b590078
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] FP : 0x4b590080
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] PC : 0x4b195a10
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] SSR : 0x00000008
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] BADVA : 0x00020000
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] LR : 0x4b1951ac
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] Stack Dump
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] from : 0x4b590078
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227] to : 0x4b590150
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.187227]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.237326] remoteproc remoteproc0: crash detected in cd00000.q6v5_wcss: type fatal error
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.259540] remoteproc remoteproc0: handling crash #1 in cd00000.q6v5_wcss
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.267772] remoteproc remoteproc0: recovering cd00000.q6v5_wcss
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.285148] ath11k c000000.wifi: failed to send WMI_PEER_DELETE cmd
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.285195] ath11k c000000.wifi: failed to delete peer vdev_id 1 addr 50:ed:3c:47:33:e8 ret -108
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.290585] ath11k c000000.wifi: Failed to delete peer: 50:ed:3c:47:33:e8 for VDEV: 1
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.299467] ath11k c000000.wifi: Found peer entry 9c:9d:7e:76:5d:01 n vdev 1 after it was supposedly removed
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.301082] remoteproc remoteproc0: stopped remote processor cd00000.q6v5_wcss
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.307401] ------------[ cut here ]------------
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.324948] WARNING: CPU: 2 PID: 1477 at sta_set_sinfo+0xba4/0xbc0 [mac80211]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.329558] Modules linked in: pppoe ppp_async nft_fib_inet nf_flow_table_ipv6 nf_flow_table_ipv4 nf_flow_table_inet ath11k_ahb ath11k ath10k_pci ath10k_core ath pppox ppp_generic nft_reject_ipv6 nft_reject_ipv4 nft_reject_inet nft_reject nft_redir nft_quota nft_objref nft_numgen nft_nat nft_masq nft_log nft_limit nft_hash nft_flow_offload nft_fib_ipv6 nft_fib_ipv4 nft_fib nft_ct nft_counter nft_chain_nat nf_tables nf_nat nf_flow_table nf_conntrack mac80211 cfg80211 slhc qrtr_smd qrtr qmi_helpers ns nfnetlink nf_reject_ipv6 nf_reject_ipv4 nf_log_syslog nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c hwmon crc_ccitt compat seqiv jitterentropy_rng drbg michael_mic hmac cmac leds_gpio xhci_plat_hcd xhci_pci xhci_hcd dwc3 dwc3_qcom qca_nss_dp qca_ssdk gpio_button_hotplug crc32c_generic
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.383269] CPU: 2 PID: 1477 Comm: hostapd Not tainted 5.15.86 #0
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.405508] Hardware name: Xiaomi AX3600 (DT)
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.411667] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.416188] pc : sta_set_sinfo+0xba4/0xbc0 [mac80211]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.423475] lr : sta_set_sinfo+0xba0/0xbc0 [mac80211]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.428508] sp : ffffffc00aecb840
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.433713] x29: ffffffc00aecb840 x28: ffffff80097d5240 x27: ffffffc00aecbdd0
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.437195] x26: ffffff800206e880 x25: ffffffc008c170c0 x24: ffffffc000a96000
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.444486] x23: ffffffc00aecba38 x22: ffffff8007664100 x21: ffffff800987c900
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.451777] x20: ffffff8005c78880 x19: ffffff8015da2000 x18: 0000000000000005
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.459070] x17: 312076656476206e x16: 2031303a64353a36 x15: 373a65373a64393a
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.466360] x14: 6339207972746e65 x13: 205d373634393932 x12: 0000000000000001
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.473653] x11: 0000000000000004 x10: 000000000000000d x9 : ffffffc00aecb39c
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.480945] x8 : 0000000000000000 x7 : ffffffc008ccd000 x6 : 0000000000008e08
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.488235] x5 : 000000008c131702 x4 : 0000000000000000 x3 : ffffff80097d5240
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.495528] x2 : 0000000000000000 x1 : ffffff80097d5240 x0 : 00000000ffffff94
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.502821] Call trace:
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.510100] sta_set_sinfo+0xba4/0xbc0 [mac80211]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.512882] sta_info_destroy_addr_bss+0x50/0x7c [mac80211]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.517574] ieee80211_color_change_finish+0x1d88/0x2040 [mac80211]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.523477] cfg80211_check_station_change+0x1408/0x4970 [cfg80211]
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.529901] genl_family_rcv_msg_doit+0xb8/0x11c
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.536320] genl_rcv_msg+0xd4/0x1cc
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.541005] netlink_rcv_skb+0x5c/0x130
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.544738] genl_rcv+0x38/0x50
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.548817] netlink_unicast+0x1f8/0x2f4
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.552117] netlink_sendmsg+0x1a0/0x3dc
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.556110] ____sys_sendmsg+0x288/0x2c0
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.560190] ___sys_sendmsg+0x84/0xf0
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.564266] __sys_sendmsg+0x48/0xb0
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.564297] ath11k c000000.wifi: failed to transmit frame -108
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.567999] __arm64_sys_sendmsg+0x24/0x30
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.568003] invoke_syscall.constprop.0+0x5c/0x104
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.582239] do_el0_svc+0x6c/0x15c
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.587183] el0_svc+0x18/0x54
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.590742] el0t_64_sync_handler+0xe8/0x114
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.593956] el0t_64_sync+0x184/0x188
Apr 7 19:31:26 OpenWrt9 kernel: [2330731.598209] ---[ end trace 5e2dbf6ef999b878 ]---
Apr 7 19:31:29 OpenWrt9 kernel: [2330733.889573] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Apr 7 19:31:29 OpenWrt9 kernel: [2330733.889624] ath11k c000000.wifi: failed to send pdev bss chan info request
Apr 7 19:31:29 OpenWrt9 kernel: [2330733.896682] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Apr 7 19:31:29 OpenWrt9 kernel: [2330733.903451] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Apr 7 19:31:29 OpenWrt9 kernel: [2330733.910145] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Apr 7 19:31:31 OpenWrt9 kernel: [2330736.315092] qcom-q6v5-wcss-pil cd00000.q6v5_wcss: start timed out
Apr 7 19:31:31 OpenWrt9 kernel: [2330736.315143] remoteproc remoteproc0: can't start rproc cd00000.q6v5_wcss: -110
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.922777] ath11k_warn: 35 callbacks suppressed
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.922799] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.926518] ath11k c000000.wifi: failed to send pdev bss chan info request
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.934701] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.941437] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.948141] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.954782] ath11k c000000.wifi: failed to submit beacon template command: -108
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.961138] ath11k c000000.wifi: failed to update bcn template: -108
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.968525] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.974921] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Apr 7 19:31:35 OpenWrt9 kernel: [2330739.981793] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Apr 7 19:31:41 OpenWrt9 kernel: [2330745.990839] ath11k_warn: 30 callbacks suppressed
Apr 7 19:31:41 OpenWrt9 kernel: [2330745.990863] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
Apr 7 19:31:41 OpenWrt9 kernel: [2330745.994555] ath11k c000000.wifi: failed to send pdev bss chan info request
Apr 7 19:31:41 OpenWrt9 kernel: [2330746.002776] ath11k c000000.wifi: failed to send WMI_PDEV_SET_PARAM cmd
Apr 7 19:31:41 OpenWrt9 kernel: [2330746.009508] ath11k c000000.wifi: Failed to set beacon mode for VDEV: 1
Apr 7 19:31:41 OpenWrt9 kernel: [2330746.016198] ath11k c000000.wifi: failed to send WMI_BCN_TMPL_CMDID
Apr 7 19:31:41 OpenWrt9 kernel: [2330746.022850] ath11k c000000.wifi: failed to submit beacon template command: -108
Apr 7 19:31:41 OpenWrt9 kernel: [2330746.029208] ath11k c000000.wifi: failed to update bcn template: -108
Apr 7 19:31:41 OpenWrt9 kernel: [2330746.036584] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Apr 7 19:31:41 OpenWrt9 kernel: [2330746.042988] ath11k c000000.wifi: failed to set BA BUFFER SIZE 256 for vdev: 1
Apr 7 19:31:41 OpenWrt9 kernel: [2330746.049876] ath11k c000000.wifi: failed to send WMI_VDEV_SET_PARAM_CMDID
Apr 7 19:31:47 OpenWrt9 kernel: [2330752.060960] ath11k_warn: 30 callbacks suppressed
Please upgrade to current snapshot, as there is a new wifi firmware in place since a few days.
2 Likes
Do I have to reset all my config or can I keep them?
I upgraded the version a few days ago (Attended Sysupgrade) and since then, I have been updating daily. But it feels like it is getting worse and worse
You should be able to keep the config.
is it possible to use ax3600 with some firmware for 1000/1000 internet connection?
my device will do only 650/650 over wifi running OpenWrt SNAPSHOT r24936-60ffcfdabc / LuCI Master git-24.025.10336-0617d30
:-/ can i modify something to make it faster?
What about via ethernet?
Wifi is subject to bandwidth limitations based on the channel width, environmental factors, distance, radio performance of the sta device, etc.
Yes, but not at full speed.
ipq8071a with its four 1.4 GHz cortex a53 cores maxes out at a routing throughput of around 600 MBit/s, as you already noticed. The OEM firmware is designed with NSS offloading in mind, which bypasses significant parts of the kernel's netfilter processing and offloads most of the packet process into a proprietary firmware running on its two 1.5 GHz ubicom-LE NPU cores to achieve wire speed.
While there is lots of untapped optimization potential in the very basic (~=bad) switchdev drivers, improving those will take years at best (or might never happen).
OpenWrt itself will never support NSS offloading, as it's way too invasive on the kernel side and would impose a huge maintenance burden on the project; community builds trying to work on NSS exist - but I would not choose this hardware with NSS in mind.
ipq8072a and upwards should get closer to 1 GBit/s throughput, thanks to their faster clockspeed (4*2.2 GHz), but even those are around the limit for these WAN speeds. Mediatek based routers (mt7622bv or filogic 820/ 830, filogic 880) have the upper hand on ipq807x for these wan speeds, as their packet processing has mainline support and considering that their network/ switch drivers and much more optimized than the basic drivers for the ipq807x platfom.
ā¦still applies
I use mine as AP and hit 850Mbit/sec with WiFi w/o problems (measured with iperf3 client running on phone). CPU hovers around 20%. And that is using 80Mhz 2x2 radio as I do not own any 3x3 802.11ax device. I bet that you can completely saturate Gbit line with 3x3 device.
So at least WiFi portion is not an issue. ax3600 is perfect as low-cost replacement for C7 Access point.
Whether it is as capable NAT device, I hope someone can do some benchmarking (I use x86 as router).
yes i know that NSS builds are able to max 1Gb/s both ways but they are much less stable for me now so i stay on classic builds and also on last builds im unable to connect with 50% of my wifi devices.
NAT is the issue here with bridge i can also pull 1GB/s
i just wondered if there is some way how to make it work full 1Gb/s
also does it work fullspeed with nss on xiaomi default firmware?
It probably does, but with CCP firmware utilizing HW accelleration and no way to tell what it is doing.
Heck, my old Archer C7 did NAT at almost 1Gbit. I still flashed it with OpenWRT.
I always have issues with the 5Ghz radio (Qualcomm Atheros QCA9887 802.11ac/b/g/n) disappearing or not allowing connections. The only time it's operable is for a short period when the router is reset or flashed with new firmware. It malfunctions within an hour sometimes.
I've used the regular snapshots from OpenWRT and have tried some NSS builds. The other IPQ8074 radios work fine with no issues. I like to use the 3rd band for IoT but it's useless due to this issue.
Thoughts anyone?
THANKS
That's IoT radio, right? The third one?
Frankly, I never used it. Kinda pointless bit of kit considering you have .ax 2.4GHz radio fitted. I have dozen of IoT devices working off QCA9887 2.4GHz radio w/o trouble.