Unable to get a Compex WLE600NX working with hostapd

Unable to get a Compex WLE600NX working with hostapd

[Matthias Cramer]

Hi All

I already spent several hours trying to build an AP with hostapd and a Compex WLE600NX card.
I have found several examples which seemed to work for the author on this mailing list but all more than 1 year old.

My system runs Debian unstable with kernel 4.3.0-1-amd64 (stable and testing do not have the ath10k firmware).
hostapd v2.3

my config looks like this (is one of the configs I found here with very small changes):

----------------------------------------------------------------------------------------

### hostapd configuration file
ctrl_interface=/var/run/hostapd
interface=wlp4s0
driver=nl80211
bridge=br0

### IEEE 802.11
ssid=ath10k
hw_mode=a
channel=0
max_num_sta=128
auth_algs=1
disassoc_low_ack=1

### DFS
ieee80211h=1
ieee80211d=1
country_code=CH

### IEEE 802.11n
ieee80211n=1
ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40]

### IEEE 802.11ac
ieee80211ac=1
vht_oper_chwidth=1
vht_capab=[MAX-MPDU-11454][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP7][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN]

### WPA/IEEE 802.11i
wpa=2
wpa_key_mgmt=WPA-PSK
wpa_passphrase=12345678
wpa_pairwise=CCMP

### Wi-Fi Protected Setup (WPS)
wps_state=2
ap_setup_locked=0
wps_pin_requests=/var/run/hostapd_wps_pin_requests
device_name=QCA Access Point
manufacturer=Qualcomm Atheros
device_type=6-0050F204-1
config_methods=virtual_push_button physical_push_button label keypad virtual_display
pbc_in_m1=1
ap_pin=12345670
upnp_iface=br-lan
eap_server=1

### hostapd event logger configuration
logger_syslog=127
logger_syslog_level=2
logger_stdout=127
logger_stdout_level=2

### WMM
wmm_enabled=1
uapsd_advertisement_enabled=1
wmm_ac_bk_cwmin=4
wmm_ac_bk_cwmax=10
wmm_ac_bk_aifs=7
wmm_ac_bk_txop_limit=0
wmm_ac_bk_acm=0
wmm_ac_be_aifs=3
wmm_ac_be_cwmin=4
wmm_ac_be_cwmax=10
wmm_ac_be_txop_limit=0
wmm_ac_be_acm=0
wmm_ac_vi_aifs=2
wmm_ac_vi_cwmin=3
wmm_ac_vi_cwmax=4
wmm_ac_vi_txop_limit=94
wmm_ac_vi_acm=0
wmm_ac_vo_aifs=2
wmm_ac_vo_cwmin=2
wmm_ac_vo_cwmax=3
wmm_ac_vo_txop_limit=47
wmm_ac_vo_acm=0

### TX queue parameters
tx_queue_data3_aifs=7
tx_queue_data3_cwmin=15
tx_queue_data3_cwmax=1023
tx_queue_data3_burst=0
tx_queue_data2_aifs=3
tx_queue_data2_cwmin=15
tx_queue_data2_cwmax=63
tx_queue_data2_burst=0
tx_queue_data1_aifs=1
tx_queue_data1_cwmin=7
tx_queue_data1_cwmax=15
tx_queue_data1_burst=3.0
tx_queue_data0_aifs=1
tx_queue_data0_cwmin=3
tx_queue_data0_cwmax=7
tx_queue_data0_burst=1.5

----------------------------------------------------------------------------------------

This is the output if I start hostapd form the console:

Configuration file: hostapd.conf
wlp4s0: interface state UNINITIALIZED->COUNTRY_UPDATE
ACS: Automatic channel selection started, this may take a bit
wlp4s0: interface state COUNTRY_UPDATE->ACS
wlp4s0: ACS-STARTED
wlp4s0: ACS-COMPLETED freq=5260 channel=52
wlp4s0: interface state ACS->HT_SCAN
wlp4s0: interface state HT_SCAN->DFS
wlp4s0: DFS-CAC-START freq=5260 chan=52 sec_chan=1, width=1, seg0=58, seg1=0, cac_time=0s
DFS start_dfs_cac() failed, -1
Interface initialization failed
wlp4s0: interface state DFS->DISABLED
wlp4s0: AP-DISABLED
hostapd_free_hapd_data: Interface wlp4s0 wasn't started

I also tried several different configs all with no usable result.

Any guidance is very welcome.

Regards

  Matthias

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Unable to get a Compex WLE600NX working with hostapd

[Michal Kazior]

On 12 January 2016 at 17:01, Matthias Cramer <cramer@freestone.net> wrote:
> Hi All
>
> I already spent several hours trying to build an AP with hostapd and a Compex WLE600NX card.
> I have found several examples which seemed to work for the author on this mailing list but all more than 1 year old.
>
> My system runs Debian unstable with kernel 4.3.0-1-amd64 (stable and testing do not have the ath10k firmware).
> hostapd v2.3
>
> my config looks like this (is one of the configs I found here with very small changes):
[...]
> ### DFS
> ieee80211h=1
> ieee80211d=1
> country_code=CH
[...]
> This is the output if I start hostapd form the console:
>
> Configuration file: hostapd.conf
> wlp4s0: interface state UNINITIALIZED->COUNTRY_UPDATE
> ACS: Automatic channel selection started, this may take a bit
> wlp4s0: interface state COUNTRY_UPDATE->ACS
> wlp4s0: ACS-STARTED
> wlp4s0: ACS-COMPLETED freq=5260 channel=52
> wlp4s0: interface state ACS->HT_SCAN
> wlp4s0: interface state HT_SCAN->DFS
> wlp4s0: DFS-CAC-START freq=5260 chan=52 sec_chan=1, width=1, seg0=58, seg1=0, cac_time=0s
> DFS start_dfs_cac() failed, -1
[...]

Can you try running with "-dddd" for more debug output?

I don't know how debian builds the kernel but it might not have the
regulatory onus enabled (which is required for DFS operation).

Generally see output of these two commands:
 iw list
 iw reg get

In the first one you need to see something like the following to be
able to use DFS channels:

  radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

But maybe you don't really need DFS channels? In that case you can use
channels 36,40,44,48 or 149,154,159,163 depending on your regulatory
settings. Again - `iw list` will help you see which channels are
allowed and which aren't.


Michał

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

Re: Unable to get a Compex WLE600NX working with hostapd

[Michal Kazior]

+ list

Please don't strip the mailing list away from Cc.


On 12 January 2016 at 20:23, Matthias Cramer <cramer@freestone.net> wrote:
> Hi Michal
>
> Thanks for your reply. I played around a little more, disabled DFS, set the channel manually to 40 or 44, no luck.
>
> Attached the output of the commands you told me before any changes where made.
>
> In the ACS scan list I only see channels 40 and 44 in the 5GHz band ... I think that is strange.

Ok the attached files:

root@stargate:~#  iw reg get
country 00: DFS-UNSET
(2402 - 2472 @ 40), (6, 20), (N/A)
(2457 - 2482 @ 40), (6, 20), (N/A), PASSIVE-SCAN
(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 160), (6, 20), (N/A), PASSIVE-SCAN
(5250 - 5330 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
(5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)

This may suggest you don't have CRDA running properly since you're
stuck on world regulatory domain.

`iwlist` shows you have no channels available for initiating
radiation. This is due to the regulatory problem.

Frequencies:
* 5180 MHz [36] (30.0 dBm) (no IR)
* 5200 MHz [40] (30.0 dBm) (no IR)
* 5220 MHz [44] (30.0 dBm) (no IR)
* 5240 MHz [48] (30.0 dBm) (no IR)
* 5260 MHz [52] (30.0 dBm) (no IR, radar detection)
 DFS state: usable (for 162 sec)
 DFS CAC time: 0 ms
* 5280 MHz [56] (30.0 dBm) (no IR, radar detection)
 DFS state: usable (for 162 sec)
 DFS CAC time: 0 ms
* 5300 MHz [60] (30.0 dBm) (no IR, radar detection)
 DFS state: usable (for 162 sec)
 DFS CAC time: 0 ms
* 5320 MHz [64] (30.0 dBm) (no IR, radar detection)
 DFS state: usable (for 162 sec)
 DFS CAC time: 0 ms
* 5500 MHz [100] (disabled)
* 5520 MHz [104] (disabled)
* 5540 MHz [108] (disabled)
* 5560 MHz [112] (disabled)
* 5580 MHz [116] (disabled)
* 5600 MHz [120] (disabled)
* 5620 MHz [124] (disabled)
* 5640 MHz [128] (disabled)
* 5660 MHz [132] (disabled)
* 5680 MHz [136] (disabled)
* 5700 MHz [140] (disabled)
* 5720 MHz [144] (30.0 dBm) (no IR)
* 5745 MHz [149] (30.0 dBm) (no IR)
* 5765 MHz [153] (30.0 dBm) (no IR)
* 5785 MHz [157] (30.0 dBm) (no IR)
* 5805 MHz [161] (30.0 dBm) (no IR)
* 5825 MHz [165] (30.0 dBm) (no IR)

You also don't have certification onus in the kernel and have no radar
detection in interface combinations:

alid interface combinations:
* #{ AP } <= 8,
  total <= 8, #channels <= 1, STA/AP BI must match

You'd have to recompile the kernel yourself and enable the onus and
DFS for ath/ath10k modules if you want to use channels 52-140.

However I would first look into the regulatory domain problem. Do you
have crda installed on your system? (apt-get install crda) Is it up to
date?


Michał


>
> Regards
>
>   Matthias
>
> On 12/01/16 17:13, Michal Kazior wrote:
>> On 12 January 2016 at 17:01, Matthias Cramer <cramer@freestone.net> wrote:
>>> Hi All
>>>
>>> I already spent several hours trying to build an AP with hostapd and a Compex WLE600NX card.
>>> I have found several examples which seemed to work for the author on this mailing list but all more than 1 year old.
>>>
>>> My system runs Debian unstable with kernel 4.3.0-1-amd64 (stable and testing do not have the ath10k firmware).
>>> hostapd v2.3
>>>
>>> my config looks like this (is one of the configs I found here with very small changes):
>> [...]
>>> ### DFS
>>> ieee80211h=1
>>> ieee80211d=1
>>> country_code=CH
>> [...]
>>> This is the output if I start hostapd form the console:
>>>
>>> Configuration file: hostapd.conf
>>> wlp4s0: interface state UNINITIALIZED->COUNTRY_UPDATE
>>> ACS: Automatic channel selection started, this may take a bit
>>> wlp4s0: interface state COUNTRY_UPDATE->ACS
>>> wlp4s0: ACS-STARTED
>>> wlp4s0: ACS-COMPLETED freq=5260 channel=52
>>> wlp4s0: interface state ACS->HT_SCAN
>>> wlp4s0: interface state HT_SCAN->DFS
>>> wlp4s0: DFS-CAC-START freq=5260 chan=52 sec_chan=1, width=1, seg0=58, seg1=0, cac_time=0s
>>> DFS start_dfs_cac() failed, -1
>> [...]
>>
>> Can you try running with "-dddd" for more debug output?
>>
>> I don't know how debian builds the kernel but it might not have the
>> regulatory onus enabled (which is required for DFS operation).
>>
>> Generally see output of these two commands:
>>  iw list
>>  iw reg get
>>
>> In the first one you need to see something like the following to be
>> able to use DFS channels:
>>
>>   radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
>>
>> But maybe you don't really need DFS channels? In that case you can use
>> channels 36,40,44,48 or 149,154,159,163 depending on your regulatory
>> settings. Again - `iw list` will help you see which channels are
>> allowed and which aren't.
>>
>>
>> Michał
>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
>>
>

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k