Xiaomi AX3600: 160 MHz not possible on ch36, radio1 (IPQ8074 802.11acaxn)

Catfriend1 · January 31, 2023, 1:19pm

Hi,

I'm on official snapshot of 29/01/2023. I tried to set:

country=DE
channel=36
mode=HE160 (160 MHz)
mode=AX

and the radio no longer comes up. Before, with 80 MHz everything was fine. Here's the log:

Tue Jan 31 12:52:58 2023 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->DFS
Tue Jan 31 12:52:58 2023 daemon.notice hostapd: phy1-ap0: DFS-CAC-START freq=5180 chan=36 sec_chan=1, width=2, seg0=50, seg1=0, cac_time=60s
Tue Jan 31 12:53:00 2023 daemon.notice netifd: radio1 (13255): command failed: Link has been severed (-67)
Tue Jan 31 12:53:00 2023 daemon.notice netifd: radio1 (13255): command failed: Link has been severed (-67)
Tue Jan 31 12:53:00 2023 daemon.notice netifd: Wireless device 'radio1' is now up
Tue Jan 31 12:53:00 2023 daemon.notice netifd: Interface 'nwi_mesh0' is enabled
Tue Jan 31 12:53:02 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Tue Jan 31 12:53:03 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Tue Jan 31 12:53:04 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
(...)
Tue Jan 31 12:53:59 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Tue Jan 31 12:54:00 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Tue Jan 31 12:54:01 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Tue Jan 31 12:54:02 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Tue Jan 31 12:54:08 2023 daemon.notice hostapd: phy1-ap0: DFS-CAC-COMPLETED success=1 freq=5180 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5250 cf2=0
Tue Jan 31 12:54:08 2023 daemon.warn hostapd: Can't set DFS state for freq 5180 MHz
Tue Jan 31 12:54:08 2023 daemon.warn hostapd: Can't set DFS state for freq 5200 MHz
Tue Jan 31 12:54:08 2023 daemon.warn hostapd: Can't set DFS state for freq 5220 MHz
Tue Jan 31 12:54:08 2023 daemon.warn hostapd: Can't set DFS state for freq 5240 MHz
Tue Jan 31 12:54:13 2023 daemon.err wpa_supplicant[1901]: could not get valid channel
Tue Jan 31 12:55:30 2023 kern.warn kernel: [43144.340941] ath11k c000000.wifi: failed to flush transmit queue, data pkts pending 3

I've then tried channel 100 and it took 10 minutes to DFS-SCAN but worked - success. Log:

Tue Jan 31 12:56:40 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: interface state UNINITIALIZED->DFS
Tue Jan 31 12:57:31 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: interface state DFS->DISABLED
Tue Jan 31 12:57:32 2023 daemon.notice hostapd: phy1-ap0: interface state COUNTRY_UPDATE->DFS
Tue Jan 31 12:57:32 2023 daemon.notice hostapd: phy1-ap0: DFS-CAC-START freq=5500 chan=100 sec_chan=1, width=2, seg0=114, seg1=0, cac_time=600s
(...)
Tue Jan 31 13:07:55 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
Tue Jan 31 13:07:56 2023 daemon.notice hostapd: phy1-ap0: DFS-CAC-COMPLETED success=1 freq=5500 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5570 cf2=0
Tue Jan 31 13:07:56 2023 kern.info kernel: [  914.465785] br-vl177: port 6(phy1-ap0) entered blocking state
Tue Jan 31 13:07:56 2023 kern.info kernel: [  914.465843] br-vl177: port 6(phy1-ap0) entered forwarding state
Tue Jan 31 13:07:56 2023 daemon.notice netifd: Network device 'phy1-ap0' link is up
Tue Jan 31 13:07:56 2023 daemon.notice hostapd: phy1-ap0: interface state DFS->ENABLED
Tue Jan 31 13:07:56 2023 daemon.notice hostapd: phy1-ap0: AP-ENABLED
Tue Jan 31 13:08:01 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Jan 31 13:08:01 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: interface state COUNTRY_UPDATE->ENABLED
Tue Jan 31 13:08:01 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: AP-ENABLED
Tue Jan 31 13:08:01 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: joining mesh MESH
Tue Jan 31 13:08:01 2023 daemon.notice netifd: Network device 'phy1-mesh0' link is up
Tue Jan 31 13:08:01 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed [id=2 id_str=]
Tue Jan 31 13:08:01 2023 daemon.notice netifd: Interface 'nwi_mesh0' has link connectivity
Tue Jan 31 13:08:01 2023 daemon.notice netifd: Interface 'nwi_mesh0' is setting up now
Tue Jan 31 13:08:01 2023 daemon.notice wpa_supplicant[1901]: phy1-mesh0: MESH-GROUP-STARTED ssid="MESH" id=2
Tue Jan 31 13:08:01 2023 kern.info kernel: [  919.579733] batman_adv: bat0: Adding interface: phy1-mesh0
Tue Jan 31 13:08:01 2023 kern.info kernel: [  919.579796] batman_adv: bat0: Interface activated: phy1-mesh0
Tue Jan 31 13:08:01 2023 daemon.notice netifd: Interface 'nwi_mesh0' is now up

Why is ch36 not working and produces errors in the log?

Kind regards,
Catfriend1

frollic · January 31, 2023, 1:40pm

AFAIK 36 isn't a 160MHz channel.

Catfriend1 · January 31, 2023, 2:11pm

Oh, then my google'd source was wrong. Which are 160 MHz channels?

frollic · January 31, 2023, 2:14pm

According to Wikipedia, 50, 114 and 163, but the info might be outdated, and/or region dependent.

Catfriend1 · January 31, 2023, 2:17pm

Thanks, definitely helpful

rincewind · January 31, 2023, 2:22pm

Run iw reg get on your router and it will show you regulatory info for each radio. Bands that have @160 can be used with 160MHz channels.

Catfriend1 · January 31, 2023, 3:07pm

I'm back on country=DE. ch50 doesn't work. ch100 works okay after waiting 10 mins for DFS to complete scanning.

system · February 10, 2023, 3:07pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.