I am trying (and failing) to get DFS to work with my AP using a QCA9882-based (ath10k) card. This is for 5GHz 802.11ac. I have compiled my kernel with the requisite DFS options so I get: # dmesg -T | grep -i dfs [Sat Oct 13 17:49:55 2018] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 0 [Sat Oct 13 17:49:56 2018] ath10k_pci 0000:07:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 1 testmode 0 (I have two cards of the same chipset installed in this machine; I want it to work as a dual-band AP. The 2.4GHz card is working perfectly.) Everything works for the 5GHz card if I have DFS disabled. However, if I enable DFS, I see this in the log, which looks very confusing to me: Oct 13 21:51:43 braid systemd[1]: Started hostapd wireless AP on wlp7s0. Oct 13 21:51:43 braid hostapd[16428]: Configuration file: /nix/store/4m5isvlqjdwiv7ylgy2vg7mzhj65la4n-wlp7s0-hostapd.conf Oct 13 21:51:43 braid hostapd[16428]: wlp7s0: interface state UNINITIALIZED->COUNTRY_UPDATE Oct 13 21:51:43 braid hostapd[16428]: ACS: Automatic channel selection started, this may take a bit Oct 13 21:51:43 braid hostapd[16428]: wlp7s0: interface state COUNTRY_UPDATE->ACS Oct 13 21:51:43 braid hostapd[16428]: wlp7s0: ACS-STARTED Oct 13 21:52:02 braid hostapd[16428]: wlp7s0: ACS-COMPLETED freq=5660 channel=132 Oct 13 21:52:02 braid hostapd[16428]: wlp7s0: interface state ACS->HT_SCAN Oct 13 21:52:02 braid hostapd[16428]: wlp7s0: interface state HT_SCAN->DFS Oct 13 21:52:02 braid hostapd[16428]: wlp7s0: DFS-CAC-START freq=5660 chan=132 sec_chan=1, width=1, seg0=138, seg1=0, cac_time=60s Oct 13 21:53:03 braid hostapd[16428]: wlp7s0: DFS-CAC-COMPLETED success=1 freq=5660 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5690 cf2=0 Oct 13 21:53:03 braid hostapd[16428]: Using interface wlp7s0 with hwaddr 00:30:1a:4e:07:43 and ssid "abcdef" Oct 13 21:53:03 braid hostapd[16428]: wlp7s0: interface state DFS->ENABLED Oct 13 21:53:03 braid hostapd[16428]: wlp7s0: AP-ENABLED Oct 13 21:53:03 braid hostapd[16428]: wlp7s0: DFS-CAC-COMPLETED success=1 freq=5660 ht_enabled=0 chan_offset=0 chan_width=3 cf1=5690 cf2=0 Oct 13 21:53:03 braid hostapd[16428]: hostapd_setup_bss: Interface wlp7s0 was already started Oct 13 21:53:03 braid hostapd[16428]: Interface initialization failed Oct 13 21:53:03 braid hostapd[16428]: wlp7s0: interface state ENABLED->DISABLED Oct 13 21:53:03 braid hostapd[16428]: wlp7s0: AP-DISABLED I find this super confusing. It looks like CAC runs to completion, and the interface is started. But then, it "finishes" a second time, which fails a sanity check, and then the whole thing is brought down. Is this a bug? I can provide whatever logs you want, this is totally reproducible. It also reproduces exactly the same whether I run one instance of hostapd with two config files or two separate instances. Thanks! Q My failing config: interface=wlp7s0 driver=nl80211 ssid=abcdef hw_mode=a channel=0 # logging (debug level) logger_syslog=-1 logger_syslog_level=2 logger_stdout=-1 logger_stdout_level=2 ctrl_interface=/var/run/hostapd ctrl_interface_group=wheel wpa=2 wpa_passphrase=12345 bridge=br0 # Pairwise cipher for WPA (v1) (default: TKIP) wpa_pairwise=CCMP # Pairwise cipher for RSN/WPA2 (default: use wpa_pairwise value) rsn_pairwise=CCMP wpa=2 # DFS country_code=US ieee80211d=1 ieee80211h=1 # Switching to 0 allows the AP to come up. # WMM wmm_enabled=1 # IEEE 802.11n ieee80211n=1 ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][MAX-AMSDU-7935][DSSS_CCK-40][SMPS-STATIC][40-INTOLERANT] # IEEE 802.11ac ieee80211ac=1 vht_oper_chwidth=1 vht_capab=[MAX-MPDU-11454][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN][MAX-A-MPDU-LEN-EXP3] ieee8021x=0 _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
