Use this channel guide to use with 160MHz, based on your country settings.
e.g for country US, try channel 36/100/149
My phone is a Samsung A54 and my laptop has a WiFi 6E card. That's why I need to use the 160MHz channel width. I don't think I need to change my configuration beyond what was already working with RC1.
I am using channel 36. Always worked until I changed firmware.
1 Like
No occurrence of cac_time or DFS in the logs.
From my experiments, I believe that there's mismatch between how Wikipedia numbers these channels and what this router expects.
For me, the working channel numbers for 160Mhz are 64, 128 and 177
Anything else doesn't work.
Wi-Fi scanner app on client laptop sees them as 36-64, 100-128, 149-177.
I don't know what is this and what is the proper naming and whether it's a bug in LUCI UI or driver, or by design etc.
If you use 36@80Mhz, it will use channels 36,40,44,48 and no DFS.
If you use 36@160Mhz, it uses channels 36 to 64 and DFS.
So when you use 160Mhz you should see the DFS msgs.
I don't know if your wifi driver crashed, if your log was too big or if you tried with 80Mhz.
Here is part of my log a few minutes after I reboot the router, using latest snapshot 36@160Mhz:
( cac_time=60s, so it should take 1 minute to test for DFS radar before it can decide if he can turn the AP on)
Sat Sep 30 09:23:20 2023 daemon.notice hostapd: phy1-ap0: AP-ENABLED
Sat Sep 30 09:23:20 2023 daemon.notice hostapd: phy0-ap0: interface state HT_SCAN->DFS
Sat Sep 30 09:23:20 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5180 chan=36 sec_chan=1, width=2, seg0=50, seg1=0, cac_time=60s
Sat Sep 30 09:23:20 2023 daemon.notice netifd: Wireless device 'radio0' is now up
...
Sat Sep 30 09:28:01 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-COMPLETED success=1 freq=5180 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5250 cf2=0
Sat Sep 30 09:28:01 2023 daemon.warn hostapd: Can't set DFS state for freq 5180 MHz
Sat Sep 30 09:28:01 2023 daemon.warn hostapd: Can't set DFS state for freq 5200 MHz
Sat Sep 30 09:28:01 2023 daemon.warn hostapd: Can't set DFS state for freq 5220 MHz
Sat Sep 30 09:28:01 2023 daemon.warn hostapd: Can't set DFS state for freq 5240 MHz
...
Sat Sep 30 09:28:01 2023 daemon.notice hostapd: phy0-ap0: interface state DFS->ENABLED
Sat Sep 30 09:28:01 2023 daemon.notice hostapd: phy0-ap0: AP-ENABLED
For me the working choices are only 64, 128 and 177, not 36
r23930-6cf27094e9
It depends on the Country you select.
that's odd, what output do you get if you run: iwinfo phy0 info ?
I changed from 36 to 48 and everything is working as expected.
1 Like
It's exactly the same to select 36 or 48 at 80Mhz or at 160Mhz.
Each individual channel is only 20Mhz wide.
Whatever channel you select from 36 to 48, with 80Mhz it will use all channels from 36 to 48.
Whatever channel you select from 36 to 64, with 160Mhz it will use all channels from 36 to 64.
Read about this in the 5Ghz section here:
https://forum.openwrt.org/t/dynalink-dl-wrx36-askey-rt5010w-ipq8072a-technical-discussion/110454/2414
It's not exactly same... 48 works and 36 doesn't
1 Like
phy0 ESSID: unknown
Access Point: A4:97:33:??:??:??
Mode: Master Channel: 128 (5.640 GHz) HT Mode: HE160
Center Channel 1: 114 2: unknown
Tx-Power: 23 dBm Link Quality: unknown/70
Signal: unknown Noise: unknown
Bit Rate: unknown
Encryption: unknown
Type: nl80211 HW Mode(s): 802.11ac/ax/n
Hardware: embedded [Qualcomm Atheros IPQ8074]
TX power offset: none
Frequency offset: none
Supports VAPs: yes PHY name: phy0
I just tried....
and now the 5GHz SSID is not even shown in my wireless list, so unable to connect.
I am not sure if DL-WRX36 factory firmware supports 160 MHz.
There was a similar problem with Belkin RT3200 which uses Mediatek platform. The factory firmware has proprietary Mediatek WiFi driver and has 160 MHz disabled. But mt76 driver in OpenWrt initially allowed 160 MHz but there were some problems and 160 MHz was disabled in mt76 code for that device and some early Mediatek wifi 6 hardware.
Maybe there's a similar problem with the DL-WRX36, although this device has Qualcomm platform and uses ath11k wifi driver.
Do you really need 160 MHz? I think 80 MHz would be more stable.
1 Like
I only use 80Mhz for 5GHz.
I just found it odd connecting to channels 64/128/177 using 160MHz as @fun_gift does, so I tried channel 128 as posted, only to find it stopped broadcasting altogether.
Could you take a look at syslog to try to find any hint on what happens to you?
Here 128@160Mhz works after 10 minutes (as it's expected).
cac_time=600s, so it only turns the AP on after 10 minutes.
After that I can connect to it.
Sun Oct 1 08:55:08 2023 daemon.notice hostapd: phy0-ap0: interface state HT_SCAN->DFS
Sun Oct 1 08:55:08 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5640 chan=128 sec_chan=-1, width=2, seg0=114, seg1=0, cac_time=600s
...
Sun Oct 1 09:05:34 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-COMPLETED success=1 freq=5640 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5570 cf2=0
...
Sun Oct 1 09:05:35 2023 daemon.notice netifd: Network device 'phy0-ap0' link is up
Sun Oct 1 09:05:35 2023 daemon.notice hostapd: phy0-ap0: interface state DFS->ENABLED
Sun Oct 1 09:05:35 2023 daemon.notice hostapd: phy0-ap0: AP-ENABLED
As can be seen by syslog time stamp entries, it took 10 minutes before DFS could decide if it could turn the AP on.
Sorry, I can't replicate any of the described issues here.
OK, working on channel 36@160Mhz, can connect to it:
Sun Oct 1 22:54:24 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-COMPLETED success=1 freq=5180 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5250 cf2=0
...
Sun Oct 1 22:53:23 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5180 chan=36 sec_chan=1, width=2, seg0=50, seg1=0, cac_time=60s
channel 128@160Mhz, yet SSID is not seen
Sun Oct 1 22:26:25 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-COMPLETED success=1 freq=5640 ht_enabled=0 chan_offset=0 chan_width=5 cf1=5570 cf2=0
...
Sun Oct 1 22:25:22 2023 daemon.notice hostapd: phy0-ap0: DFS-CAC-START freq=5640 chan=128 sec_chan=-1, width=2, seg0=114, seg1=0, cac_time=60s
using channel 177 / 165 / 149@160Mhz disables phy0-ap0
Sun Oct 1 23:13:48 2023 daemon.notice hostapd: phy0-ap0: AP-DISABLED
Sun Oct 1 23:13:48 2023 daemon.notice hostapd: phy0-ap0: interface state HT_SCAN->DISABLED
Sun Oct 1 23:13:48 2023 daemon.err hostapd: Interface initialization failed
Sun Oct 1 23:13:47 2023 daemon.notice netifd: Wireless device 'radio0' is now up
Sun Oct 1 23:13:47 2023 daemon.notice hostapd: phy0-ap0: interface state COUNTRY_UPDATE->HT_SCAN
Sun Oct 1 23:13:47 2023 daemon.notice hostapd: phy0-ap0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Oct 1 23:13:47 2023 kern.info kernel: [26848.167845] br-lan: port 5(phy0-ap0) entered disabled state
Sun Oct 1 23:13:47 2023 kern.info kernel: [26848.162157] br-lan: port 5(phy0-ap0) entered forwarding state
Sun Oct 1 23:13:47 2023 kern.info kernel: [26848.157006] br-lan: port 5(phy0-ap0) entered blocking state
Sun Oct 1 23:13:47 2023 kern.info kernel: [26848.151684] device phy0-ap0 entered promiscuous mode
Sun Oct 1 23:13:47 2023 kern.info kernel: [26848.147027] br-lan: port 5(phy0-ap0) entered disabled state
Sun Oct 1 23:13:47 2023 kern.info kernel: [26848.146989] br-lan: port 5(phy0-ap0) entered blocking state
Sun Oct 1 23:13:47 2023 daemon.notice hostapd: Configuration file: data: driver=nl80211 logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 country_code=US ieee80211d=1 ieee80211h=1 hw_mode=a beacon_int=100 chanlist=177 tx_queue_data2_burst=2.0 #num_global_macaddr=1 ieee80211n=1 ht_coex=0 ht_capab=[HT40-][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40] ieee80211ac=1 vht_oper_chwidth=2 vht_oper_centr_freq_seg0_idx=177 vht_capab=[RXLDPC][SHORT-GI-80][SHORT-GI-160][TX-STBC-2BY1][SU-BEAMFORMER][SU-BEAMFORMEE][MU-BEAMFORMER][MU-BEAMFORMEE][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][RX-STBC-1][SOUNDING-DIMENSION-4][BF-ANTENNA-4][VHT160-80PLUS80][MAX-MPDU-11454][MAX-A-MPDU-LEN-EXP7] ieee80211ax=1 he_oper_chwidth=2 he_oper_centr_freq_seg0_idx=177 he_su_beamformer=1 he_su_beamformee=1 he_mu_beamformer=1 he_bss_color=128 he_spr_sr_control=3 he_default_pe_duration=4 he_rts_threshold=1023 he_mu_edca_qos_info_param_count=0 he_mu_edca_qos_info_q_ack=0 he_mu_edca_qos_info_queue_reques
Sun Oct 1 23:13:47 2023 kern.info kernel: [26847.868004] br-lan: port 5(phy0-ap0) entered disabled state
Sun Oct 1 23:13:47 2023 kern.info kernel: [26847.867876] device phy0-ap0 left promiscuous mode
Sun Oct 1 23:13:47 2023 daemon.notice hostapd: nl80211: deinit ifname=phy0-ap0 disabled_11b_rates=0
Sun Oct 1 23:13:47 2023 daemon.err hostapd: hostapd_free_hapd_data: Interface phy0-ap0 wasn't started
Sun Oct 1 23:13:47 2023 daemon.err hostapd: rmdir[ctrl_interface=/var/run/hostapd]: Permission denied
Sun Oct 1 23:13:47 2023 daemon.notice hostapd: phy0-ap0: CTRL-EVENT-TERMINATING
One difference I noticed is my cac_time for 128@160Mhz is 10 minutes and your is 1 minute.
I have selected an European country and you have selected US. I don't know if they have different cac_time for the same channel.
Regarding the other error msgs., let's wait if someone else knows what they mean.
Just for reference, I running yesterday snapshot OpenWrt SNAPSHOT r24043-ff95f859eb / LuCI Master git-23.266.27574-7744ad0.