... this was sth else.
Update: I've found a workaround how the connection works. I need to go to Windows device manager, select my newly inserted Intel AX210NGW wireless card driver and then setz "wireless mode 802.11n/ac/ax" to option "3. 802.11 ac". So, something is wrong with the ax radio1 the device tries to connect to on the first attempt.
I can now replicate the problem. I've enabled AX Ch36 80 Mhz on the AX3600 radio1. If a client like Intel AX210NGW (Windows 10) tries to connect in AX mode, it fails (connected, speed visible, no network and no internet connectivity at all, 0 bytes received, 21 bytes sent).
If I restrict the mode to "ac" in device manager, the connection works pretty well, fast and reliable.
ath10k is for 802.11ac generation of chips. Those won't do you any good.
Yeah, I noticed the ath11k is affected. Deleted my first post as this is another problem already solved nothing to do with this problem still left. Whenever I switch to AX mode on the Intel AX210 client, it doesn't communicate.
Do you have the appropriate country code set on the router?
and does the wifi pop up on your cell phone, assuming it's AX capable ?
Yes, the problem occured with the correct and an alternative country code. So I think that's not the cause.
My cell phone works, but it has an AC adapter (no AX support).
It's strange - I had those "0 bytes received" appearance on multiple notebooks with an AX210NGW adapter the last days. When it occurs, it doesn't go away by itself.
I've now rebooted my two AX3600 units and it started working after setting mode=AX in Windows device manager for the wifi card.
I'll report when it stops working again.
I'll be on the lookout what my be the root cause here... currently I suspect the mesh SSID running in parallel to the SSID where the AX210 clients connect to. This is my config:
(...)
config wifi-device 'radio1'
option type 'mac80211'
option path 'platform/soc/c000000.wifi'
option channel '100'
option band '5g'
option htmode 'HE160'
option txpower '23'
option cell_density '0'
option country 'DE'
option disabled '0'
(...)
config wifi-iface 'wifinet0'
option device 'radio1'
option disabled '0'
option short_preamble '0'
option mode 'mesh'
option network 'nwi_mesh0'
option mesh_id 'MESH-SSID'
option encryption 'sae'
option key 'PSK'
option disassoc_low_ack '1'
option dtim_period '1'
option short_preamble '1'
option mesh_fwding '0'
option mesh_rssi_threshold '0'
config wifi-iface 'wifinet1'
option device 'radio1'
option disabled '0'
option mode 'ap'
option network 'VL177'
option ssid 'SSID'
option encryption 'psk2+ccmp'
option key 'PSK'
option ieee80211w '1'
option wpa_disable_eapol_key_retries '1'
option disassoc_low_ack '1'
option dtim_period '1'
option short_preamble '1'
When I played with 160MHz, on the WAX206 (MT chipset using openwrt beta fw) the radio wouldn't even come up if I selected a non-160 channel.
2 Likes
On Xiaomi AX3600, radio1 tries to DFS scan and then throws errors in the end.
Can you show these?
- I don't see errors - I see scans though.
- Perhaps you should use one thread for your issue.
- Are you asking for your device to ignore DFS?
- Are you asking about 20/40/80/160 MHz bandwidth?
- I see an error about country and you mentioned changing it - please verify you've set the country to the correct/legal setting for your locale
The only legal way I know for you to ignore DFS - is to move to another country that doesn't require DFS scans. Perhaps I'm missing something.
It's not about ignoring DFS. This thread is about wifi clients not able to connect via AX but only AC. This occured again some minutes ago and I don't understand why. It happens with HE80 or HE160 mode.
I have 5 SSIDs + 1 802.11s network all on one radio on my 301w with no issues connecting any clients, so I don't think your mesh net is an issue.
IIRC, 160MHz will always need a DFS channel to work (not sure about 80+80) as there is not anywhere on the spectrum 8 contiguous 20MHz channels outside DFS.
2 Likes
Thanks for sharing your experience :). So it's wrong to suspect the mesh. Came to this as a radio restart with unconnected mesh partner allowed to connect via AX. I'm currently totally compliant with dfs rules and using the correct country code so it's also not the client with a mismatched country.
I must have been unclear - or there's a misunderstanding on how it's related to DFS.
So - can you provide your current config (or just link to the post that contains them).
Do not scan for overlapping BSSs in HT40+/- mode.
Turning this on will violate regulatory requirements!
From: https://openwrt.org/docs/guide-user/network/wifi/basic
Are you following all regulations?
I believe this will work...but why?
All devices support this?
2 Likes