* Scanning all 5Ghz channels with AC NIC.
@ 2014-03-24 18:10 Ben Greear
2014-03-24 19:33 ` Janusz Dziedzic
2014-03-25 14:42 ` Jouni Malinen
0 siblings, 2 replies; 7+ messages in thread
From: Ben Greear @ 2014-03-24 18:10 UTC (permalink / raw)
To: hostap@lists.shmoo.com, ath10k
I notice this issue while trying to scan specific channels with
an ath10k NIC.
If I configure supplicant to use a specific freq list, it will fail:
1395683887.458813: nl80211: Scan frequency 5170 MHz
1395683887.458823: nl80211: Scan frequency 5180 MHz
1395683887.458829: nl80211: Scan frequency 5190 MHz
1395683887.458834: nl80211: Scan frequency 5200 MHz
1395683887.458840: nl80211: Scan frequency 5210 MHz
1395683887.458845: nl80211: Scan frequency 5220 MHz
1395683887.458850: nl80211: Scan frequency 5230 MHz
1395683887.458855: nl80211: Scan frequency 5240 MHz
1395683887.458861: nl80211: Scan frequency 5260 MHz
1395683887.458866: nl80211: Scan frequency 5280 MHz
1395683887.458871: nl80211: Scan frequency 5300 MHz
1395683887.458876: nl80211: Scan frequency 5320 MHz
1395683887.458881: nl80211: Scan frequency 5500 MHz
1395683887.458886: nl80211: Scan frequency 5520 MHz
1395683887.458890: nl80211: Scan frequency 5540 MHz
1395683887.458895: nl80211: Scan frequency 5560 MHz
1395683887.458900: nl80211: Scan frequency 5580 MHz
1395683887.458905: nl80211: Scan frequency 5600 MHz
1395683887.458911: nl80211: Scan frequency 5580 MHz
1395683887.458916: nl80211: Scan frequency 5600 MHz
1395683887.458921: nl80211: Scan frequency 5620 MHz
1395683887.458926: nl80211: Scan frequency 5640 MHz
1395683887.458931: nl80211: Scan frequency 5660 MHz
1395683887.458936: nl80211: Scan frequency 5620 MHz
1395683887.458942: nl80211: Scan frequency 5640 MHz
1395683887.458947: nl80211: Scan frequency 5660 MHz
1395683887.458952: nl80211: Scan frequency 5680 MHz
1395683887.458957: nl80211: Scan frequency 5700 MHz
1395683887.458962: nl80211: Scan frequency 5745 MHz
1395683887.458987: nl80211: Scan frequency 5645 MHz
1395683887.458996: nl80211: Scan frequency 5785 MHz
1395683887.459001: nl80211: Scan frequency 5805 MHz
1395683887.459005: nl80211: Scan frequency 5825 MHz
1395683887.459040: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
A standard scan seems to use only a subset of these channels.
But, wouldn't that make us miss scanning for some /a or /n APs
out there?
[root@ct521-FCFC ~]# iw event
wlan0 (phy #1): scan started
wlan0 (phy #1): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5745 5765 5785 5805 5825, ""
Any idea if this is a bug in my config/assumptions, ath10k, or supplicant?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Scanning all 5Ghz channels with AC NIC.
2014-03-24 18:10 Scanning all 5Ghz channels with AC NIC Ben Greear
@ 2014-03-24 19:33 ` Janusz Dziedzic
2014-03-24 19:47 ` Ben Greear
2014-03-25 14:42 ` Jouni Malinen
1 sibling, 1 reply; 7+ messages in thread
From: Janusz Dziedzic @ 2014-03-24 19:33 UTC (permalink / raw)
To: Ben Greear; +Cc: hostap@lists.shmoo.com, ath10k
On 24 March 2014 19:10, Ben Greear <greearb@candelatech.com> wrote:
> I notice this issue while trying to scan specific channels with
> an ath10k NIC.
>
> If I configure supplicant to use a specific freq list, it will fail:
>
> 1395683887.458813: nl80211: Scan frequency 5170 MHz
> 1395683887.458823: nl80211: Scan frequency 5180 MHz
> 1395683887.458829: nl80211: Scan frequency 5190 MHz
> 1395683887.458834: nl80211: Scan frequency 5200 MHz
> 1395683887.458840: nl80211: Scan frequency 5210 MHz
> 1395683887.458845: nl80211: Scan frequency 5220 MHz
> 1395683887.458850: nl80211: Scan frequency 5230 MHz
> 1395683887.458855: nl80211: Scan frequency 5240 MHz
> 1395683887.458861: nl80211: Scan frequency 5260 MHz
> 1395683887.458866: nl80211: Scan frequency 5280 MHz
> 1395683887.458871: nl80211: Scan frequency 5300 MHz
> 1395683887.458876: nl80211: Scan frequency 5320 MHz
> 1395683887.458881: nl80211: Scan frequency 5500 MHz
> 1395683887.458886: nl80211: Scan frequency 5520 MHz
> 1395683887.458890: nl80211: Scan frequency 5540 MHz
> 1395683887.458895: nl80211: Scan frequency 5560 MHz
> 1395683887.458900: nl80211: Scan frequency 5580 MHz
> 1395683887.458905: nl80211: Scan frequency 5600 MHz
> 1395683887.458911: nl80211: Scan frequency 5580 MHz
> 1395683887.458916: nl80211: Scan frequency 5600 MHz
> 1395683887.458921: nl80211: Scan frequency 5620 MHz
> 1395683887.458926: nl80211: Scan frequency 5640 MHz
> 1395683887.458931: nl80211: Scan frequency 5660 MHz
> 1395683887.458936: nl80211: Scan frequency 5620 MHz
> 1395683887.458942: nl80211: Scan frequency 5640 MHz
> 1395683887.458947: nl80211: Scan frequency 5660 MHz
> 1395683887.458952: nl80211: Scan frequency 5680 MHz
> 1395683887.458957: nl80211: Scan frequency 5700 MHz
> 1395683887.458962: nl80211: Scan frequency 5745 MHz
> 1395683887.458987: nl80211: Scan frequency 5645 MHz
> 1395683887.458996: nl80211: Scan frequency 5785 MHz
> 1395683887.459001: nl80211: Scan frequency 5805 MHz
> 1395683887.459005: nl80211: Scan frequency 5825 MHz
> 1395683887.459040: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
>
>
> A standard scan seems to use only a subset of these channels.
> But, wouldn't that make us miss scanning for some /a or /n APs
> out there?
>
> [root@ct521-FCFC ~]# iw event
> wlan0 (phy #1): scan started
> wlan0 (phy #1): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5745 5765 5785 5805 5825, ""
>
>
> Any idea if this is a bug in my config/assumptions, ath10k, or supplicant?
>
Strange, works quite good from iw:
janusz@dell:~$ sudo iw wlan1 scan freq 5180 5200 5220 5240 5260 5280
5300 5320 5745 5765 5785 5805 5825|grep freq
janusz@dell:~$ sudo iw wlan1 scan freq 2412 2417 2422 2427 2432 2437
2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5745
5765 5785 5805 5825|grep freq
freq: 2437
freq: 2427
freq: 2432
freq: 2452
freq: 2442
janusz@dell:~$
Last hostap with config:
network={
ssid="linksys"
psk="somepsk"
key_mgmt=WPA-PSK
disabled=1
scan_freq=2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462
5180 5200 5220 5240 5260 5280 5300 5
320 5745 5765 5785 5805 5825
}
After enable_n 4:
1395688797.243510: nl80211 Scan frequency 2412 MHz
1395688797.243522: nl80211: Scan frequency 2417 MHz
1395688797.243530: nl80211: Scan frequency 2422 MHz
1395688797.243537: nl80211: Scan frequency 2427 MHz
1395688797.243545: nl80211: Scan frequency 2432 MHz
1395688797.243552: nl80211: Scan frequency 2437 MHz
1395688797.243559: nl80211: Scan frequency 2442 MHz
1395688797.243566: nl80211: Scan frequency 2447 MHz
1395688797.243574: nl80211: Scan frequency 2452 MHz
1395688797.243581: nl80211: Scan frequency 2457 MHz
1395688797.243588: nl80211: Scan frequency 2462 MHz
1395688797.243596: nl80211: Scan frequency 5180 MHz
1395688797.243603: nl80211: Scan frequency 5200 MHz
1395688797.243610: nl80211: Scan frequency 5220 MHz
1395688797.243618: nl80211: Scan frequency 5240 MHz
1395688797.243625: nl80211: Scan frequency 5260 MHz
1395688797.243632: nl80211: Scan frequency 5280 MHz
1395688797.243639: nl80211: Scan frequency 5300 MHz
1395688797.243647: nl80211: Scan frequency 5320 MHz
1395688797.243654: nl80211: Scan frequency 5745 MHz
1395688797.243661: nl80211: Scan frequency 5765 MHz
1395688797.243669: nl80211: Scan frequency 5785 MHz
1395688797.243676: nl80211: Scan frequency 5805 MHz
1395688797.243683: nl80211: Scan frequency 5825 MHz
1395688797.243926: Scan requested (ret=0) - scan timeout 30 seconds
1395688797.244349: wlan0: CTRL-EVENT-SCAN-STARTED
1395688798.595940: nl80211: Scan included frequencies: 2412 2417 2422
2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280
5300 5320
1395688798.595993: wlan0: Event SCAN_RESULTS (3) received
CTRL-EVENT-CONNECTED - Connection to 00:14:bf:16:b8:44 completed [id=4 id_str=]
BR
Janusz
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Scanning all 5Ghz channels with AC NIC.
2014-03-24 19:33 ` Janusz Dziedzic
@ 2014-03-24 19:47 ` Ben Greear
2014-03-24 20:04 ` Ben Greear
2014-03-24 20:06 ` Janusz Dziedzic
0 siblings, 2 replies; 7+ messages in thread
From: Ben Greear @ 2014-03-24 19:47 UTC (permalink / raw)
To: Janusz Dziedzic; +Cc: hostap@lists.shmoo.com, ath10k
On 03/24/2014 12:33 PM, Janusz Dziedzic wrote:
> On 24 March 2014 19:10, Ben Greear <greearb@candelatech.com> wrote:
>> I notice this issue while trying to scan specific channels with
>> an ath10k NIC.
>>
>> If I configure supplicant to use a specific freq list, it will fail:
>>
>> 1395683887.458813: nl80211: Scan frequency 5170 MHz
>> 1395683887.458823: nl80211: Scan frequency 5180 MHz
>> 1395683887.458829: nl80211: Scan frequency 5190 MHz
>> 1395683887.458834: nl80211: Scan frequency 5200 MHz
>> 1395683887.458840: nl80211: Scan frequency 5210 MHz
>> 1395683887.458845: nl80211: Scan frequency 5220 MHz
>> 1395683887.458850: nl80211: Scan frequency 5230 MHz
>> 1395683887.458855: nl80211: Scan frequency 5240 MHz
>> 1395683887.458861: nl80211: Scan frequency 5260 MHz
>> 1395683887.458866: nl80211: Scan frequency 5280 MHz
>> 1395683887.458871: nl80211: Scan frequency 5300 MHz
>> 1395683887.458876: nl80211: Scan frequency 5320 MHz
>> 1395683887.458881: nl80211: Scan frequency 5500 MHz
>> 1395683887.458886: nl80211: Scan frequency 5520 MHz
>> 1395683887.458890: nl80211: Scan frequency 5540 MHz
>> 1395683887.458895: nl80211: Scan frequency 5560 MHz
>> 1395683887.458900: nl80211: Scan frequency 5580 MHz
>> 1395683887.458905: nl80211: Scan frequency 5600 MHz
>> 1395683887.458911: nl80211: Scan frequency 5580 MHz
>> 1395683887.458916: nl80211: Scan frequency 5600 MHz
>> 1395683887.458921: nl80211: Scan frequency 5620 MHz
>> 1395683887.458926: nl80211: Scan frequency 5640 MHz
>> 1395683887.458931: nl80211: Scan frequency 5660 MHz
>> 1395683887.458936: nl80211: Scan frequency 5620 MHz
>> 1395683887.458942: nl80211: Scan frequency 5640 MHz
>> 1395683887.458947: nl80211: Scan frequency 5660 MHz
>> 1395683887.458952: nl80211: Scan frequency 5680 MHz
>> 1395683887.458957: nl80211: Scan frequency 5700 MHz
>> 1395683887.458962: nl80211: Scan frequency 5745 MHz
>> 1395683887.458987: nl80211: Scan frequency 5645 MHz
>> 1395683887.458996: nl80211: Scan frequency 5785 MHz
>> 1395683887.459001: nl80211: Scan frequency 5805 MHz
>> 1395683887.459005: nl80211: Scan frequency 5825 MHz
>> 1395683887.459040: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
>>
>>
>> A standard scan seems to use only a subset of these channels.
>> But, wouldn't that make us miss scanning for some /a or /n APs
>> out there?
>>
>> [root@ct521-FCFC ~]# iw event
>> wlan0 (phy #1): scan started
>> wlan0 (phy #1): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5745 5765 5785 5805 5825, ""
>>
>>
>> Any idea if this is a bug in my config/assumptions, ath10k, or supplicant?
>>
> Strange, works quite good from iw:
>
> janusz@dell:~$ sudo iw wlan1 scan freq 5180 5200 5220 5240 5260 5280
> 5300 5320 5745 5765 5785 5805 5825|grep freq
> janusz@dell:~$ sudo iw wlan1 scan freq 2412 2417 2422 2427 2432 2437
> 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5745
> 5765 5785 5805 5825|grep freq
> freq: 2437
> freq: 2427
> freq: 2432
> freq: 2452
> freq: 2442
> janusz@dell:~$
>
> Last hostap with config:
> network={
> ssid="linksys"
> psk="somepsk"
> key_mgmt=WPA-PSK
> disabled=1
> scan_freq=2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462
> 5180 5200 5220 5240 5260 5280 5300 5
> 320 5745 5765 5785 5805 5825
> }
Maybe my config is wrong...I was using freq_list instead of scan_freq,
and using it twice...
ctrl_interface=/var/run/wpa_supplicant
fast_reauth=1
scan_cur_freq=1
min_scan_gap=5
freq_list=5170 5180 5190 5200 5210 5220 5230 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5580 5600 5620 5640 5660 5620 5640 5660 5680 5700 5745 5645
5785 5805 5825
bss_max_count=2000
network={
ssid="NETGEAR76-5G"
disable_ht=0
disable_vht=0
disable_ht40=0
disable_sgi=0
ht_mcs=""
disable_max_amsdu=-1
ampdu_factor=-1
ampdu_density=-1
freq_list=5170 5180 5190 5200 5210 5220 5230 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5580 5600 5620 5640 5660 5620 5640 5660 5680 5700 5745
5645 5785 5805 5825
key_mgmt=NONE
proactive_key_caching=0
}
>
> After enable_n 4:
How are you enabling n?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Scanning all 5Ghz channels with AC NIC.
2014-03-24 19:47 ` Ben Greear
@ 2014-03-24 20:04 ` Ben Greear
2014-03-24 20:06 ` Janusz Dziedzic
1 sibling, 0 replies; 7+ messages in thread
From: Ben Greear @ 2014-03-24 20:04 UTC (permalink / raw)
To: Janusz Dziedzic; +Cc: hostap@lists.shmoo.com, ath10k
On 03/24/2014 12:47 PM, Ben Greear wrote:
> Maybe my config is wrong...I was using freq_list instead of scan_freq,
> and using it twice...
>
> ctrl_interface=/var/run/wpa_supplicant
> fast_reauth=1
> scan_cur_freq=1
> min_scan_gap=5
> freq_list=5170 5180 5190 5200 5210 5220 5230 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5580 5600 5620 5640 5660 5620 5640 5660 5680 5700 5745 5645
> 5785 5805 5825
Err, I simply had a duplicated channel (5580, 5600)...
Must have cut-n-pasted wrong.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Scanning all 5Ghz channels with AC NIC.
2014-03-24 19:47 ` Ben Greear
2014-03-24 20:04 ` Ben Greear
@ 2014-03-24 20:06 ` Janusz Dziedzic
1 sibling, 0 replies; 7+ messages in thread
From: Janusz Dziedzic @ 2014-03-24 20:06 UTC (permalink / raw)
To: Ben Greear; +Cc: hostap@lists.shmoo.com, ath10k
On 24 March 2014 20:47, Ben Greear <greearb@candelatech.com> wrote:
> On 03/24/2014 12:33 PM, Janusz Dziedzic wrote:
>> On 24 March 2014 19:10, Ben Greear <greearb@candelatech.com> wrote:
>>> I notice this issue while trying to scan specific channels with
>>> an ath10k NIC.
>>>
>>> If I configure supplicant to use a specific freq list, it will fail:
>>>
>>> 1395683887.458813: nl80211: Scan frequency 5170 MHz
>>> 1395683887.458823: nl80211: Scan frequency 5180 MHz
>>> 1395683887.458829: nl80211: Scan frequency 5190 MHz
>>> 1395683887.458834: nl80211: Scan frequency 5200 MHz
>>> 1395683887.458840: nl80211: Scan frequency 5210 MHz
>>> 1395683887.458845: nl80211: Scan frequency 5220 MHz
>>> 1395683887.458850: nl80211: Scan frequency 5230 MHz
>>> 1395683887.458855: nl80211: Scan frequency 5240 MHz
>>> 1395683887.458861: nl80211: Scan frequency 5260 MHz
>>> 1395683887.458866: nl80211: Scan frequency 5280 MHz
>>> 1395683887.458871: nl80211: Scan frequency 5300 MHz
>>> 1395683887.458876: nl80211: Scan frequency 5320 MHz
>>> 1395683887.458881: nl80211: Scan frequency 5500 MHz
>>> 1395683887.458886: nl80211: Scan frequency 5520 MHz
>>> 1395683887.458890: nl80211: Scan frequency 5540 MHz
>>> 1395683887.458895: nl80211: Scan frequency 5560 MHz
>>> 1395683887.458900: nl80211: Scan frequency 5580 MHz
>>> 1395683887.458905: nl80211: Scan frequency 5600 MHz
>>> 1395683887.458911: nl80211: Scan frequency 5580 MHz
>>> 1395683887.458916: nl80211: Scan frequency 5600 MHz
>>> 1395683887.458921: nl80211: Scan frequency 5620 MHz
>>> 1395683887.458926: nl80211: Scan frequency 5640 MHz
>>> 1395683887.458931: nl80211: Scan frequency 5660 MHz
>>> 1395683887.458936: nl80211: Scan frequency 5620 MHz
>>> 1395683887.458942: nl80211: Scan frequency 5640 MHz
>>> 1395683887.458947: nl80211: Scan frequency 5660 MHz
>>> 1395683887.458952: nl80211: Scan frequency 5680 MHz
>>> 1395683887.458957: nl80211: Scan frequency 5700 MHz
>>> 1395683887.458962: nl80211: Scan frequency 5745 MHz
>>> 1395683887.458987: nl80211: Scan frequency 5645 MHz
>>> 1395683887.458996: nl80211: Scan frequency 5785 MHz
>>> 1395683887.459001: nl80211: Scan frequency 5805 MHz
>>> 1395683887.459005: nl80211: Scan frequency 5825 MHz
>>> 1395683887.459040: nl80211: Scan trigger failed: ret=-22 (Invalid argument)
>>>
>>>
>>> A standard scan seems to use only a subset of these channels.
>>> But, wouldn't that make us miss scanning for some /a or /n APs
>>> out there?
>>>
>>> [root@ct521-FCFC ~]# iw event
>>> wlan0 (phy #1): scan started
>>> wlan0 (phy #1): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5745 5765 5785 5805 5825, ""
>>>
>>>
>>> Any idea if this is a bug in my config/assumptions, ath10k, or supplicant?
>>>
>> Strange, works quite good from iw:
>>
>> janusz@dell:~$ sudo iw wlan1 scan freq 5180 5200 5220 5240 5260 5280
>> 5300 5320 5745 5765 5785 5805 5825|grep freq
>> janusz@dell:~$ sudo iw wlan1 scan freq 2412 2417 2422 2427 2432 2437
>> 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5745
>> 5765 5785 5805 5825|grep freq
>> freq: 2437
>> freq: 2427
>> freq: 2432
>> freq: 2452
>> freq: 2442
>> janusz@dell:~$
>>
>> Last hostap with config:
>> network={
>> ssid="linksys"
>> psk="somepsk"
>> key_mgmt=WPA-PSK
>> disabled=1
>> scan_freq=2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462
>> 5180 5200 5220 5240 5260 5280 5300 5
>> 320 5745 5765 5785 5805 5825
>> }
>
> Maybe my config is wrong...I was using freq_list instead of scan_freq,
> and using it twice...
>
> ctrl_interface=/var/run/wpa_supplicant
> fast_reauth=1
> scan_cur_freq=1
> min_scan_gap=5
> freq_list=5170 5180 5190 5200 5210 5220 5230 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5580 5600 5620 5640 5660 5620 5640 5660 5680 5700 5745 5645
> 5785 5805 5825
>
> bss_max_count=2000
> network={
> ssid="NETGEAR76-5G"
> disable_ht=0
> disable_vht=0
> disable_ht40=0
> disable_sgi=0
> ht_mcs=""
> disable_max_amsdu=-1
> ampdu_factor=-1
> ampdu_density=-1
> freq_list=5170 5180 5190 5200 5210 5220 5230 5240 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5580 5600 5620 5640 5660 5620 5640 5660 5680 5700 5745
> 5645 5785 5805 5825
>
> key_mgmt=NONE
> proactive_key_caching=0
>
> }
>
With such config also works fine:
ctrl_interface=/var/run/wpa_supplicant
update_config=1
freq_list=2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180
5200 5220 5240 5260 5280 5300 5320 5745
5765 5785 5805 5825
network={
ssid="linksys"
psk="some psk"
key_mgmt=WPA-PSK
disabled=1
freq_list=2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462
5180 5200 5220 5240 5260 5280 5300 5
320 5745 5765 5785 5805 5825
}
1395691023.317204: nl80211: Scan frequency 5805 MHz
1395691023.317211: nl80211: Scan frequency 5825 MHz
1395691023.317489: Scan requested (ret=0) - scan timeout 30 seconds
1395691027.433376: wlan0: nl80211: New scan results available
1395691027.433429: nl80211: Scan probed for SSID ''
1395691027.433451: nl80211: Scan included frequencies: 2412 2417 2422
2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280
5300 5320 5745 5765 5785 5805 5825
1395691027.433502: wlan0: Event SCAN_RESULTS (3) received
1395691027.433589: wlan0: Scan completed in 4.115746 seconds
So maybe other options?
Does it works from iw?
>
>>
>> After enable_n 4:
>
> How are you enabling n?
>
From wpa_cli - 4 is my net_id I am testing - this enable network and
trigger scan.
BR
Janusz
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Scanning all 5Ghz channels with AC NIC.
2014-03-24 18:10 Scanning all 5Ghz channels with AC NIC Ben Greear
2014-03-24 19:33 ` Janusz Dziedzic
@ 2014-03-25 14:42 ` Jouni Malinen
2014-03-25 15:50 ` Ben Greear
1 sibling, 1 reply; 7+ messages in thread
From: Jouni Malinen @ 2014-03-25 14:42 UTC (permalink / raw)
To: Ben Greear; +Cc: hostap@lists.shmoo.com, ath10k
On Mon, Mar 24, 2014 at 11:10:44AM -0700, Ben Greear wrote:
> I notice this issue while trying to scan specific channels with
> an ath10k NIC.
>
> If I configure supplicant to use a specific freq list, it will fail:
>
> 1395683887.458813: nl80211: Scan frequency 5170 MHz
> 1395683887.458823: nl80211: Scan frequency 5180 MHz
...
You need to be quite careful when using freq_list. wpa_supplicant will
use exactly what is provided there and if cfg80211 does not like what it
sees, it will reject this. Apparently duplicate entries would hit that
and so would channels that the driver does not support.
In general, it is much easier to just do "wpa_cli scan freq=4900-6000"
if you just want to scan all the enabled 5 GHz channels.
--
Jouni Malinen PGP id EFC895FA
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Scanning all 5Ghz channels with AC NIC.
2014-03-25 14:42 ` Jouni Malinen
@ 2014-03-25 15:50 ` Ben Greear
0 siblings, 0 replies; 7+ messages in thread
From: Ben Greear @ 2014-03-25 15:50 UTC (permalink / raw)
To: hostap@lists.shmoo.com, ath10k
On 03/25/2014 07:42 AM, Jouni Malinen wrote:
> On Mon, Mar 24, 2014 at 11:10:44AM -0700, Ben Greear wrote:
>> I notice this issue while trying to scan specific channels with
>> an ath10k NIC.
>>
>> If I configure supplicant to use a specific freq list, it will fail:
>>
>> 1395683887.458813: nl80211: Scan frequency 5170 MHz
>> 1395683887.458823: nl80211: Scan frequency 5180 MHz
> ...
>
> You need to be quite careful when using freq_list. wpa_supplicant will
> use exactly what is provided there and if cfg80211 does not like what it
> sees, it will reject this. Apparently duplicate entries would hit that
> and so would channels that the driver does not support.
>
> In general, it is much easier to just do "wpa_cli scan freq=4900-6000"
> if you just want to scan all the enabled 5 GHz channels.
I use the freq_list to effectively disable 2.4Ghz, for instance when trying
to force a station to act like /a only instead of /a/b/g.
Maybe there is a better way? (I don't often use wpa_cli directly,
so that won't help my case...)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-03-25 15:51 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-03-24 18:10 Scanning all 5Ghz channels with AC NIC Ben Greear
2014-03-24 19:33 ` Janusz Dziedzic
2014-03-24 19:47 ` Ben Greear
2014-03-24 20:04 ` Ben Greear
2014-03-24 20:06 ` Janusz Dziedzic
2014-03-25 14:42 ` Jouni Malinen
2014-03-25 15:50 ` Ben Greear
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.