OpenWRT 18.06.02 hasn't improved the 160MHz situation.
The regulatory db has the correct info, but setting 160MHz in luci causes hostapd to not bring up the adapter. Setting to the AU country code doesn't work either.
<pre>Sat Mar 23 16:10:35 2019 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Sat Mar 23 16:10:42 2019 kern.warn kernel: [977907.692948] ath10k_pci 0000:01:00.0: Unknown eventid: 36933
Sat Mar 23 16:10:42 2019 kern.info kernel: [977907.696105] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sat Mar 23 16:10:42 2019 kern.info kernel: [977907.702019] br-lan: port 3(wlan0) entered blocking state
Sat Mar 23 16:10:42 2019 kern.info kernel: [977907.703667] br-lan: port 3(wlan0) entered disabled state
Sat Mar 23 16:10:42 2019 kern.info kernel: [977907.709154] device wlan0 entered promiscuous mode
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->HT_SCAN
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: interface state HT_SCAN->DFS
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: DFS-CAC-START freq=5500 chan=100 sec_chan=1, width=2, seg0=114, seg1=0, cac_time=60s
Sat Mar 23 16:10:42 2019 daemon.err hostapd: DFS start_dfs_cac() failed, -1
Sat Mar 23 16:10:42 2019 daemon.err hostapd: Interface initialization failed
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: interface state DFS->DISABLED
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: interface state DISABLED->DISABLED
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: AP-DISABLED
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: wlan0: CTRL-EVENT-TERMINATING
Sat Mar 23 16:10:42 2019 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan0 wasn't started
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Sat Mar 23 16:10:42 2019 kern.info kernel: [977908.071830] device wlan0 left promiscuous mode
Sat Mar 23 16:10:42 2019 kern.info kernel: [977908.071925] br-lan: port 3(wlan0) entered disabled state
Sat Mar 23 16:10:42 2019 kern.warn kernel: [977908.112339] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
Sat Mar 23 16:10:42 2019 daemon.notice hostapd: ELOOP: remaining socket: sock=22 eloop_data=0xb6f73aa0 user_data=0 handler=0x42314
Sat Mar 23 16:10:42 2019 daemon.notice netifd: radio0 (15765): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process 1400 path ()</pre>
18.06.2 with VHT160 on qca9984 works and speed is very good (about 100 MB/s, not stable - sometimes drivers crashes), but on current master branch with new ath10k-ct drivers (2018-10-10-d366b80d-1) VHT160 did not works at all.
On 18.06.2 iw list shows:
valid interface combinations:
* #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }
On current master branch:
valid interface combinations:
* #{ managed } <= 16, #{ AP, mesh point } <= 16, #{ IBSS } <= 1,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
If you can actually use 160 MHz channels, you can uninstall the -CT drivers and firmware and install the “classic” (no -ct suffix) drivers and firmware as packages (or in your own build).
Even on classic drivers there is no success:
valid interface combinations:
* #{ managed } <= 1, #{ AP, mesh point } <= 16,
total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
i have tried ath10k-ct driver and classic firmware, VHT160 has start showing in valid combination, but not works.
In all cases iw list shows:
VHT Capabilities (0x339b79fa):
Max MPDU length: 11454
Supported Channel Width: 160 MHz, 80+80 MHz
RX LDPC
short GI (80 MHz)
short GI (160/80+80 MHz)
but not works.
on stable branch 18.06.2 with kmod-ath10k-ct and ath10k-firmware-qca9984-ct-htt
on current master branch OpenWrt SNAPSHOT r9855-8f17c019a1 / LuCI Master (f138fc93) with kmod-ath10k-ct (have tried kmod-ath10k) and ath10k-firmware-qca9984-ct-htt (have tried classic/ct/ct-htt).
1 - works VHT160 (successfully set and show 1733 mbit speed in WLAN card) ;
2 - not works (entering disable state and hangs, wireless did not up).
How did you get VHT160 to work on 18.06.2? I've tried numerous combinations, but hostapd refuses to start up. Please describe your settings. Your channel, regulatory domain, etc.
DFS seems to indicate you can’t use those channels. The is nothing you can legally do to override that. 160 MHz channels are seldom usable because they are already occupied by other services that have higher priority.
OK, the driver you use was a very important detail that you left out of your original posts.
I was using country code of HT. Verified it with 'iw reg get' as well. I am using the upstream kernel driver ath10k, which is also the 18.06.2 default driver. Using a forked driver does not interest me.
I am in the USA and not near any military or weather radar. It appears those in the USA are unable to use 160mhz bonding. All of these new 160mhz cards and APs are useless.
10 cm reinforced concrete wall
VHT160 (as on VHT80) is very unstable for high speed file transfer, but i have seen about 130 MB/s on VHT160 1733 mbit, but behind the 2 walls speed is drops to 866 mbit (50-80 MB/s).
I have use QCA9994 on J3060 (X86) board, works very good on CT driver and classic firmware, but VHT160 on current branch master OpenWrt is broken (on 18.06.2 stable works).
Its working stable now (even at high speed transfer)?
Are you the author of the youtube vid with the pcie extension etc? I'm contemplating a build using this pcie card and the purpose is primarily high speed wifi (80MB+), would appreciate your thoughts since it seems you've been using this system for a few months.
Did you try the card on bare metal (I see you using VMs) and allocate more than 128MB ram?
I have try it in Windows Server 2016/2019 Hyper-V under OpenWrt (it works), but server is in very long distance from wireless clients, and now i make another miniPC (Q3060G2-P board) with emergency 4G connection and 2.4/5 GHz WiFi in center of my apartments...
Compex WLE1216V5-20-I with the latest 18.06.2 works very stable and with 60-100 MB/s on Broadcom BCM4360 WiFi adapter, but it's VERY HOT, with max rate (~100 MB/s) in 30 minutes on open air temps in chip hits 130'C. It needs AIR cooling.
