* WLE600VX from PCEngines
@ 2015-09-08 21:31 Marcel H.
[not found] ` <CABkMH_pegBjg987d5Bs_xkGqk1fsYAZqjSVWorNzPnL_L7PhDw@mail.gmail.com>
2015-09-09 5:50 ` Janusz Dziedzic
0 siblings, 2 replies; 22+ messages in thread
From: Marcel H. @ 2015-09-08 21:31 UTC (permalink / raw)
To: ath10k
Hi everyone,
I have an interesting issue - I'm trying to run the QCA9882 based card
in IBSS mode (to be used for BATMAN), however all I can do is to run
in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
80MHz width resolves in the following:
Interface wlan0
ifindex 5
wdev 0x1
addr 04:f0:21:1b:5f:3b
ssid my-mesh-network
type IBSS
wiphy 0
channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
command failed: Invalid argument (-22)
root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
command failed: Invalid argument (-22)
More info:
=====================================================
06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
Network Adapter
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
Expansion ROM at f7600000 [disabled] [size=64K]
Capabilities: [40] Power Management version 2
Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: ath10k_pci
root@voyage2:/opt/ca_node/bin# iw reg get
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A)
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
root@voyage2:/opt/ca_node/bin# uname -a
Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
GMT 2015 i686 GNU/Linux
(todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10 .config)
root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
(this is from the 'main' directory in the
https://github.com/kvalo/ath10k-firmware)
Wiphy phy0
max # scan SSIDs: 16
max scan IEs length: 195 bytes
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Device supports AP-side u-APSD.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
* CMAC (00-0f-ac:6)
Available Antennas: TX 0x3 RX 0x3
Configured Antennas: TX 0x3 RX 0x3
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x19e3
RX LDPC
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x338001b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (30.0 dBm)
* 2417 MHz [2] (30.0 dBm)
* 2422 MHz [3] (30.0 dBm)
* 2427 MHz [4] (30.0 dBm)
* 2432 MHz [5] (30.0 dBm)
* 2437 MHz [6] (30.0 dBm)
* 2442 MHz [7] (30.0 dBm)
* 2447 MHz [8] (30.0 dBm)
* 2452 MHz [9] (30.0 dBm)
* 2457 MHz [10] (30.0 dBm)
* 2462 MHz [11] (30.0 dBm)
* 2467 MHz [12] (disabled)
* 2472 MHz [13] (disabled)
* 2484 MHz [14] (disabled)
Band 2:
Capabilities: 0x19e3
RX LDPC
HT20/HT40
Static SM Power Save
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
Max AMSDU length: 7935 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-15
VHT Capabilities (0x338001b2):
Max MPDU length: 11454
Supported Channel Width: neither 160 nor 80+80
RX LDPC
short GI (80 MHz)
TX STBC
RX antenna pattern consistency
TX antenna pattern consistency
VHT RX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-9
2 streams: MCS 0-9
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5180 MHz [36] (17.0 dBm)
* 5200 MHz [40] (17.0 dBm)
* 5220 MHz [44] (17.0 dBm)
* 5240 MHz [48] (17.0 dBm)
* 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
DFS state: usable (for 1076 sec)
DFS CAC time: 60000 ms
* 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
DFS state: usable (for 1076 sec)
DFS CAC time: 60000 ms
* 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
DFS state: usable (for 1076 sec)
DFS CAC time: 60000 ms
* 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
DFS state: usable (for 1076 sec)
DFS CAC time: 60000 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] (disabled)
* 5745 MHz [149] (30.0 dBm)
* 5765 MHz [153] (30.0 dBm)
* 5785 MHz [157] (30.0 dBm)
* 5805 MHz [161] (30.0 dBm)
* 5825 MHz [165] (30.0 dBm)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* remain_on_channel
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* testmode
* channel_switch
* Unknown command (104)
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
* AP/VLAN
* monitor
valid interface combinations:
* #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
P2P-device } <= 1, #{ AP } <= 7,
total <= 8, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports scan flush.
Device supports per-vif TX power setting
Driver supports a userspace MPM
Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
Device supports static SMPS
=====================================================
I am grateful for any help here and do have some time to help
debugging the issue.
Marcel
--
------------------------------------------------------
This message is not intended to have
contractual effect
------------------------------------------------------
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
[not found] ` <CABkMH_pegBjg987d5Bs_xkGqk1fsYAZqjSVWorNzPnL_L7PhDw@mail.gmail.com>
@ 2015-09-09 4:10 ` Tomasz Skapski
0 siblings, 0 replies; 22+ messages in thread
From: Tomasz Skapski @ 2015-09-09 4:10 UTC (permalink / raw)
To: Marcel H.; +Cc: ath10k
Sending again as a plain text.
Regards,
Tomasz Skąpski
On 8 September 2015 at 21:03, Tomasz Skapski <tomasz.skapski@tieto.com> wrote:
> Hi Marcel,
>
> you are using iw set freq command in a wrong way. You have to also inform
> about the center frequency to use in case of 80 MHz bandwidth. Try this:
>
> iw wlan0 set freq 5745 80 5775
>
> Regards,
> Tomasz Skąpski
>
> On 8 September 2015 at 14:31, Marcel H. <maco@blava.net> wrote:
>>
>> Hi everyone,
>> I have an interesting issue - I'm trying to run the QCA9882 based card
>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>> 80MHz width resolves in the following:
>>
>> Interface wlan0
>> ifindex 5
>> wdev 0x1
>> addr 04:f0:21:1b:5f:3b
>> ssid my-mesh-network
>> type IBSS
>> wiphy 0
>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>> command failed: Invalid argument (-22)
>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>> command failed: Invalid argument (-22)
>>
>>
>> More info:
>> =====================================================
>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
>> Network Adapter
>> Flags: bus master, fast devsel, latency 0, IRQ 27
>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>> Expansion ROM at f7600000 [disabled] [size=64K]
>> Capabilities: [40] Power Management version 2
>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>> Capabilities: [70] Express Endpoint, MSI 00
>> Capabilities: [100] Advanced Error Reporting
>> Capabilities: [140] Virtual Channel
>> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>> Kernel driver in use: ath10k_pci
>>
>> root@voyage2:/opt/ca_node/bin# iw reg get
>> country US: DFS-FCC
>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>
>>
>> root@voyage2:/opt/ca_node/bin# uname -a
>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>> GMT 2015 i686 GNU/Linux
>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10
>> .config)
>>
>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>> (this is from the 'main' directory in the
>> https://github.com/kvalo/ath10k-firmware)
>>
>>
>> Wiphy phy0
>> max # scan SSIDs: 16
>> max scan IEs length: 195 bytes
>> Retry short limit: 7
>> Retry long limit: 4
>> Coverage class: 0 (up to 0m)
>> Device supports RSN-IBSS.
>> Device supports AP-side u-APSD.
>> Supported Ciphers:
>> * WEP40 (00-0f-ac:1)
>> * WEP104 (00-0f-ac:5)
>> * TKIP (00-0f-ac:2)
>> * CCMP (00-0f-ac:4)
>> * CMAC (00-0f-ac:6)
>> Available Antennas: TX 0x3 RX 0x3
>> Configured Antennas: TX 0x3 RX 0x3
>> Supported interface modes:
>> * IBSS
>> * managed
>> * AP
>> * AP/VLAN
>> * monitor
>> * P2P-client
>> * P2P-GO
>> * P2P-device
>> Band 1:
>> Capabilities: 0x19e3
>> RX LDPC
>> HT20/HT40
>> Static SM Power Save
>> RX HT20 SGI
>> RX HT40 SGI
>> TX STBC
>> RX STBC 1-stream
>> Max AMSDU length: 7935 bytes
>> DSSS/CCK HT40
>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>> HT TX/RX MCS rate indexes supported: 0-15
>> VHT Capabilities (0x338001b2):
>> Max MPDU length: 11454
>> Supported Channel Width: neither 160 nor 80+80
>> RX LDPC
>> short GI (80 MHz)
>> TX STBC
>> RX antenna pattern consistency
>> TX antenna pattern consistency
>> VHT RX MCS set:
>> 1 streams: MCS 0-9
>> 2 streams: MCS 0-9
>> 3 streams: not supported
>> 4 streams: not supported
>> 5 streams: not supported
>> 6 streams: not supported
>> 7 streams: not supported
>> 8 streams: not supported
>> VHT RX highest supported: 0 Mbps
>> VHT TX MCS set:
>> 1 streams: MCS 0-9
>> 2 streams: MCS 0-9
>> 3 streams: not supported
>> 4 streams: not supported
>> 5 streams: not supported
>> 6 streams: not supported
>> 7 streams: not supported
>> 8 streams: not supported
>> VHT TX highest supported: 0 Mbps
>> Bitrates (non-HT):
>> * 1.0 Mbps
>> * 2.0 Mbps (short preamble supported)
>> * 5.5 Mbps (short preamble supported)
>> * 11.0 Mbps (short preamble supported)
>> * 6.0 Mbps
>> * 9.0 Mbps
>> * 12.0 Mbps
>> * 18.0 Mbps
>> * 24.0 Mbps
>> * 36.0 Mbps
>> * 48.0 Mbps
>> * 54.0 Mbps
>> Frequencies:
>> * 2412 MHz [1] (30.0 dBm)
>> * 2417 MHz [2] (30.0 dBm)
>> * 2422 MHz [3] (30.0 dBm)
>> * 2427 MHz [4] (30.0 dBm)
>> * 2432 MHz [5] (30.0 dBm)
>> * 2437 MHz [6] (30.0 dBm)
>> * 2442 MHz [7] (30.0 dBm)
>> * 2447 MHz [8] (30.0 dBm)
>> * 2452 MHz [9] (30.0 dBm)
>> * 2457 MHz [10] (30.0 dBm)
>> * 2462 MHz [11] (30.0 dBm)
>> * 2467 MHz [12] (disabled)
>> * 2472 MHz [13] (disabled)
>> * 2484 MHz [14] (disabled)
>> Band 2:
>> Capabilities: 0x19e3
>> RX LDPC
>> HT20/HT40
>> Static SM Power Save
>> RX HT20 SGI
>> RX HT40 SGI
>> TX STBC
>> RX STBC 1-stream
>> Max AMSDU length: 7935 bytes
>> DSSS/CCK HT40
>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>> HT TX/RX MCS rate indexes supported: 0-15
>> VHT Capabilities (0x338001b2):
>> Max MPDU length: 11454
>> Supported Channel Width: neither 160 nor 80+80
>> RX LDPC
>> short GI (80 MHz)
>> TX STBC
>> RX antenna pattern consistency
>> TX antenna pattern consistency
>> VHT RX MCS set:
>> 1 streams: MCS 0-9
>> 2 streams: MCS 0-9
>> 3 streams: not supported
>> 4 streams: not supported
>> 5 streams: not supported
>> 6 streams: not supported
>> 7 streams: not supported
>> 8 streams: not supported
>> VHT RX highest supported: 0 Mbps
>> VHT TX MCS set:
>> 1 streams: MCS 0-9
>> 2 streams: MCS 0-9
>> 3 streams: not supported
>> 4 streams: not supported
>> 5 streams: not supported
>> 6 streams: not supported
>> 7 streams: not supported
>> 8 streams: not supported
>> VHT TX highest supported: 0 Mbps
>> Bitrates (non-HT):
>> * 6.0 Mbps
>> * 9.0 Mbps
>> * 12.0 Mbps
>> * 18.0 Mbps
>> * 24.0 Mbps
>> * 36.0 Mbps
>> * 48.0 Mbps
>> * 54.0 Mbps
>> Frequencies:
>> * 5180 MHz [36] (17.0 dBm)
>> * 5200 MHz [40] (17.0 dBm)
>> * 5220 MHz [44] (17.0 dBm)
>> * 5240 MHz [48] (17.0 dBm)
>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 1076 sec)
>> DFS CAC time: 60000 ms
>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 1076 sec)
>> DFS CAC time: 60000 ms
>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 1076 sec)
>> DFS CAC time: 60000 ms
>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 1076 sec)
>> DFS CAC time: 60000 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] (disabled)
>> * 5745 MHz [149] (30.0 dBm)
>> * 5765 MHz [153] (30.0 dBm)
>> * 5785 MHz [157] (30.0 dBm)
>> * 5805 MHz [161] (30.0 dBm)
>> * 5825 MHz [165] (30.0 dBm)
>> Supported commands:
>> * new_interface
>> * set_interface
>> * new_key
>> * start_ap
>> * new_station
>> * set_bss
>> * authenticate
>> * associate
>> * deauthenticate
>> * disassociate
>> * join_ibss
>> * remain_on_channel
>> * set_tx_bitrate_mask
>> * frame
>> * frame_wait_cancel
>> * set_wiphy_netns
>> * set_channel
>> * set_wds_peer
>> * probe_client
>> * set_noack_map
>> * register_beacons
>> * start_p2p_device
>> * set_mcast_rate
>> * testmode
>> * channel_switch
>> * Unknown command (104)
>> * connect
>> * disconnect
>> Supported TX frame types:
>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
>> 0xb0 0xc0 0xd0 0xe0 0xf0
>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> Supported RX frame types:
>> * IBSS: 0x40 0xb0 0xc0 0xd0
>> * managed: 0x40 0xd0
>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>> * mesh point: 0xb0 0xc0 0xd0
>> * P2P-client: 0x40 0xd0
>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>> * P2P-device: 0x40 0xd0
>> software interface modes (can always be added):
>> * AP/VLAN
>> * monitor
>> valid interface combinations:
>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>> P2P-device } <= 1, #{ AP } <= 7,
>> total <= 8, #channels <= 1, STA/AP BI must match
>> HT Capability overrides:
>> * MCS: ff ff ff ff ff ff ff ff ff ff
>> * maximum A-MSDU length
>> * supported channel width
>> * short GI for 40 MHz
>> * max A-MPDU length exponent
>> * min MPDU start spacing
>> Device supports TX status socket option.
>> Device supports HT-IBSS.
>> Device supports SAE with AUTHENTICATE command
>> Device supports scan flush.
>> Device supports per-vif TX power setting
>> Driver supports a userspace MPM
>> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>> Device supports static SMPS
>> =====================================================
>>
>> I am grateful for any help here and do have some time to help
>> debugging the issue.
>>
>> Marcel
>>
>> --
>>
>> ------------------------------------------------------
>> This message is not intended to have
>> contractual effect
>> ------------------------------------------------------
>>
>> _______________________________________________
>> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-08 21:31 WLE600VX from PCEngines Marcel H.
[not found] ` <CABkMH_pegBjg987d5Bs_xkGqk1fsYAZqjSVWorNzPnL_L7PhDw@mail.gmail.com>
@ 2015-09-09 5:50 ` Janusz Dziedzic
2015-09-09 6:20 ` Jorge Baranda
1 sibling, 1 reply; 22+ messages in thread
From: Janusz Dziedzic @ 2015-09-09 5:50 UTC (permalink / raw)
To: Marcel H.; +Cc: ath10k
On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
> Hi everyone,
> I have an interesting issue - I'm trying to run the QCA9882 based card
> in IBSS mode (to be used for BATMAN), however all I can do is to run
> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
> 80MHz width resolves in the following:
>
You should run IBSS using fresh wpa_supplicant (best latest code). By
default should run in 80MHz.
Other case is your regulatory - are you allow to use 80MHz on channel
157? First try 5180.
eg. of wpa_supplicant config:
network = {
ssid="test_ibss"
key_mgmt=NONE
mode=1
frequency=5180
}
BR
Janusz
> Interface wlan0
> ifindex 5
> wdev 0x1
> addr 04:f0:21:1b:5f:3b
> ssid my-mesh-network
> type IBSS
> wiphy 0
> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
> command failed: Invalid argument (-22)
> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
> command failed: Invalid argument (-22)
>
>
> More info:
> =====================================================
> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
> Network Adapter
> Flags: bus master, fast devsel, latency 0, IRQ 27
> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
> Expansion ROM at f7600000 [disabled] [size=64K]
> Capabilities: [40] Power Management version 2
> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
> Capabilities: [70] Express Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [140] Virtual Channel
> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
> Kernel driver in use: ath10k_pci
>
> root@voyage2:/opt/ca_node/bin# iw reg get
> country US: DFS-FCC
> (2402 - 2472 @ 40), (N/A, 30), (N/A)
> (5170 - 5250 @ 80), (N/A, 17), (N/A)
> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
> (5735 - 5835 @ 80), (N/A, 30), (N/A)
> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>
>
> root@voyage2:/opt/ca_node/bin# uname -a
> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
> GMT 2015 i686 GNU/Linux
> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10 .config)
>
> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
> (this is from the 'main' directory in the
> https://github.com/kvalo/ath10k-firmware)
>
>
> Wiphy phy0
> max # scan SSIDs: 16
> max scan IEs length: 195 bytes
> Retry short limit: 7
> Retry long limit: 4
> Coverage class: 0 (up to 0m)
> Device supports RSN-IBSS.
> Device supports AP-side u-APSD.
> Supported Ciphers:
> * WEP40 (00-0f-ac:1)
> * WEP104 (00-0f-ac:5)
> * TKIP (00-0f-ac:2)
> * CCMP (00-0f-ac:4)
> * CMAC (00-0f-ac:6)
> Available Antennas: TX 0x3 RX 0x3
> Configured Antennas: TX 0x3 RX 0x3
> Supported interface modes:
> * IBSS
> * managed
> * AP
> * AP/VLAN
> * monitor
> * P2P-client
> * P2P-GO
> * P2P-device
> Band 1:
> Capabilities: 0x19e3
> RX LDPC
> HT20/HT40
> Static SM Power Save
> RX HT20 SGI
> RX HT40 SGI
> TX STBC
> RX STBC 1-stream
> Max AMSDU length: 7935 bytes
> DSSS/CCK HT40
> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> Minimum RX AMPDU time spacing: 8 usec (0x06)
> HT TX/RX MCS rate indexes supported: 0-15
> VHT Capabilities (0x338001b2):
> Max MPDU length: 11454
> Supported Channel Width: neither 160 nor 80+80
> RX LDPC
> short GI (80 MHz)
> TX STBC
> RX antenna pattern consistency
> TX antenna pattern consistency
> VHT RX MCS set:
> 1 streams: MCS 0-9
> 2 streams: MCS 0-9
> 3 streams: not supported
> 4 streams: not supported
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> VHT RX highest supported: 0 Mbps
> VHT TX MCS set:
> 1 streams: MCS 0-9
> 2 streams: MCS 0-9
> 3 streams: not supported
> 4 streams: not supported
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> VHT TX highest supported: 0 Mbps
> Bitrates (non-HT):
> * 1.0 Mbps
> * 2.0 Mbps (short preamble supported)
> * 5.5 Mbps (short preamble supported)
> * 11.0 Mbps (short preamble supported)
> * 6.0 Mbps
> * 9.0 Mbps
> * 12.0 Mbps
> * 18.0 Mbps
> * 24.0 Mbps
> * 36.0 Mbps
> * 48.0 Mbps
> * 54.0 Mbps
> Frequencies:
> * 2412 MHz [1] (30.0 dBm)
> * 2417 MHz [2] (30.0 dBm)
> * 2422 MHz [3] (30.0 dBm)
> * 2427 MHz [4] (30.0 dBm)
> * 2432 MHz [5] (30.0 dBm)
> * 2437 MHz [6] (30.0 dBm)
> * 2442 MHz [7] (30.0 dBm)
> * 2447 MHz [8] (30.0 dBm)
> * 2452 MHz [9] (30.0 dBm)
> * 2457 MHz [10] (30.0 dBm)
> * 2462 MHz [11] (30.0 dBm)
> * 2467 MHz [12] (disabled)
> * 2472 MHz [13] (disabled)
> * 2484 MHz [14] (disabled)
> Band 2:
> Capabilities: 0x19e3
> RX LDPC
> HT20/HT40
> Static SM Power Save
> RX HT20 SGI
> RX HT40 SGI
> TX STBC
> RX STBC 1-stream
> Max AMSDU length: 7935 bytes
> DSSS/CCK HT40
> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
> Minimum RX AMPDU time spacing: 8 usec (0x06)
> HT TX/RX MCS rate indexes supported: 0-15
> VHT Capabilities (0x338001b2):
> Max MPDU length: 11454
> Supported Channel Width: neither 160 nor 80+80
> RX LDPC
> short GI (80 MHz)
> TX STBC
> RX antenna pattern consistency
> TX antenna pattern consistency
> VHT RX MCS set:
> 1 streams: MCS 0-9
> 2 streams: MCS 0-9
> 3 streams: not supported
> 4 streams: not supported
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> VHT RX highest supported: 0 Mbps
> VHT TX MCS set:
> 1 streams: MCS 0-9
> 2 streams: MCS 0-9
> 3 streams: not supported
> 4 streams: not supported
> 5 streams: not supported
> 6 streams: not supported
> 7 streams: not supported
> 8 streams: not supported
> VHT TX highest supported: 0 Mbps
> Bitrates (non-HT):
> * 6.0 Mbps
> * 9.0 Mbps
> * 12.0 Mbps
> * 18.0 Mbps
> * 24.0 Mbps
> * 36.0 Mbps
> * 48.0 Mbps
> * 54.0 Mbps
> Frequencies:
> * 5180 MHz [36] (17.0 dBm)
> * 5200 MHz [40] (17.0 dBm)
> * 5220 MHz [44] (17.0 dBm)
> * 5240 MHz [48] (17.0 dBm)
> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 1076 sec)
> DFS CAC time: 60000 ms
> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 1076 sec)
> DFS CAC time: 60000 ms
> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 1076 sec)
> DFS CAC time: 60000 ms
> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 1076 sec)
> DFS CAC time: 60000 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] (disabled)
> * 5745 MHz [149] (30.0 dBm)
> * 5765 MHz [153] (30.0 dBm)
> * 5785 MHz [157] (30.0 dBm)
> * 5805 MHz [161] (30.0 dBm)
> * 5825 MHz [165] (30.0 dBm)
> Supported commands:
> * new_interface
> * set_interface
> * new_key
> * start_ap
> * new_station
> * set_bss
> * authenticate
> * associate
> * deauthenticate
> * disassociate
> * join_ibss
> * remain_on_channel
> * set_tx_bitrate_mask
> * frame
> * frame_wait_cancel
> * set_wiphy_netns
> * set_channel
> * set_wds_peer
> * probe_client
> * set_noack_map
> * register_beacons
> * start_p2p_device
> * set_mcast_rate
> * testmode
> * channel_switch
> * Unknown command (104)
> * connect
> * disconnect
> Supported TX frame types:
> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
> 0xb0 0xc0 0xd0 0xe0 0xf0
> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
> Supported RX frame types:
> * IBSS: 0x40 0xb0 0xc0 0xd0
> * managed: 0x40 0xd0
> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * mesh point: 0xb0 0xc0 0xd0
> * P2P-client: 0x40 0xd0
> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
> * P2P-device: 0x40 0xd0
> software interface modes (can always be added):
> * AP/VLAN
> * monitor
> valid interface combinations:
> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
> P2P-device } <= 1, #{ AP } <= 7,
> total <= 8, #channels <= 1, STA/AP BI must match
> HT Capability overrides:
> * MCS: ff ff ff ff ff ff ff ff ff ff
> * maximum A-MSDU length
> * supported channel width
> * short GI for 40 MHz
> * max A-MPDU length exponent
> * min MPDU start spacing
> Device supports TX status socket option.
> Device supports HT-IBSS.
> Device supports SAE with AUTHENTICATE command
> Device supports scan flush.
> Device supports per-vif TX power setting
> Driver supports a userspace MPM
> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
> Device supports static SMPS
> =====================================================
>
> I am grateful for any help here and do have some time to help
> debugging the issue.
>
> Marcel
>
> --
>
> ------------------------------------------------------
> This message is not intended to have
> contractual effect
> ------------------------------------------------------
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-09 5:50 ` Janusz Dziedzic
@ 2015-09-09 6:20 ` Jorge Baranda
2015-09-09 7:43 ` Janusz Dziedzic
0 siblings, 1 reply; 22+ messages in thread
From: Jorge Baranda @ 2015-09-09 6:20 UTC (permalink / raw)
To: ath10k
Hi everyone,
Reading this thread, I would like to share with people some doubts about
it.
@Marco, I imagine you want to run your WLE600VX device using the
802.11ac protocol, isn't it?
@Janusz, with running wpa_supplicant on both computers, will the ad-hoc
connection be established? I am starting with these tools and now, I am
getting used to know how they work. I was creating the ad-hoc connection
with the iw tool.
Thanks,
El 09/09/15 07:50, Janusz Dziedzic escribió:
> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>> Hi everyone,
>> I have an interesting issue - I'm trying to run the QCA9882 based card
>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>> 80MHz width resolves in the following:
>>
> You should run IBSS using fresh wpa_supplicant (best latest code). By
> default should run in 80MHz.
> Other case is your regulatory - are you allow to use 80MHz on channel
> 157? First try 5180.
>
> eg. of wpa_supplicant config:
>
> network = {
> ssid="test_ibss"
> key_mgmt=NONE
> mode=1
> frequency=5180
> }
>
> BR
> Janusz
>
>> Interface wlan0
>> ifindex 5
>> wdev 0x1
>> addr 04:f0:21:1b:5f:3b
>> ssid my-mesh-network
>> type IBSS
>> wiphy 0
>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>> command failed: Invalid argument (-22)
>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>> command failed: Invalid argument (-22)
>>
>>
>> More info:
>> =====================================================
>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
>> Network Adapter
>> Flags: bus master, fast devsel, latency 0, IRQ 27
>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>> Expansion ROM at f7600000 [disabled] [size=64K]
>> Capabilities: [40] Power Management version 2
>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>> Capabilities: [70] Express Endpoint, MSI 00
>> Capabilities: [100] Advanced Error Reporting
>> Capabilities: [140] Virtual Channel
>> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>> Kernel driver in use: ath10k_pci
>>
>> root@voyage2:/opt/ca_node/bin# iw reg get
>> country US: DFS-FCC
>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>
>>
>> root@voyage2:/opt/ca_node/bin# uname -a
>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>> GMT 2015 i686 GNU/Linux
>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10 .config)
>>
>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>> (this is from the 'main' directory in the
>> https://github.com/kvalo/ath10k-firmware)
>>
>>
>> Wiphy phy0
>> max # scan SSIDs: 16
>> max scan IEs length: 195 bytes
>> Retry short limit: 7
>> Retry long limit: 4
>> Coverage class: 0 (up to 0m)
>> Device supports RSN-IBSS.
>> Device supports AP-side u-APSD.
>> Supported Ciphers:
>> * WEP40 (00-0f-ac:1)
>> * WEP104 (00-0f-ac:5)
>> * TKIP (00-0f-ac:2)
>> * CCMP (00-0f-ac:4)
>> * CMAC (00-0f-ac:6)
>> Available Antennas: TX 0x3 RX 0x3
>> Configured Antennas: TX 0x3 RX 0x3
>> Supported interface modes:
>> * IBSS
>> * managed
>> * AP
>> * AP/VLAN
>> * monitor
>> * P2P-client
>> * P2P-GO
>> * P2P-device
>> Band 1:
>> Capabilities: 0x19e3
>> RX LDPC
>> HT20/HT40
>> Static SM Power Save
>> RX HT20 SGI
>> RX HT40 SGI
>> TX STBC
>> RX STBC 1-stream
>> Max AMSDU length: 7935 bytes
>> DSSS/CCK HT40
>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>> HT TX/RX MCS rate indexes supported: 0-15
>> VHT Capabilities (0x338001b2):
>> Max MPDU length: 11454
>> Supported Channel Width: neither 160 nor 80+80
>> RX LDPC
>> short GI (80 MHz)
>> TX STBC
>> RX antenna pattern consistency
>> TX antenna pattern consistency
>> VHT RX MCS set:
>> 1 streams: MCS 0-9
>> 2 streams: MCS 0-9
>> 3 streams: not supported
>> 4 streams: not supported
>> 5 streams: not supported
>> 6 streams: not supported
>> 7 streams: not supported
>> 8 streams: not supported
>> VHT RX highest supported: 0 Mbps
>> VHT TX MCS set:
>> 1 streams: MCS 0-9
>> 2 streams: MCS 0-9
>> 3 streams: not supported
>> 4 streams: not supported
>> 5 streams: not supported
>> 6 streams: not supported
>> 7 streams: not supported
>> 8 streams: not supported
>> VHT TX highest supported: 0 Mbps
>> Bitrates (non-HT):
>> * 1.0 Mbps
>> * 2.0 Mbps (short preamble supported)
>> * 5.5 Mbps (short preamble supported)
>> * 11.0 Mbps (short preamble supported)
>> * 6.0 Mbps
>> * 9.0 Mbps
>> * 12.0 Mbps
>> * 18.0 Mbps
>> * 24.0 Mbps
>> * 36.0 Mbps
>> * 48.0 Mbps
>> * 54.0 Mbps
>> Frequencies:
>> * 2412 MHz [1] (30.0 dBm)
>> * 2417 MHz [2] (30.0 dBm)
>> * 2422 MHz [3] (30.0 dBm)
>> * 2427 MHz [4] (30.0 dBm)
>> * 2432 MHz [5] (30.0 dBm)
>> * 2437 MHz [6] (30.0 dBm)
>> * 2442 MHz [7] (30.0 dBm)
>> * 2447 MHz [8] (30.0 dBm)
>> * 2452 MHz [9] (30.0 dBm)
>> * 2457 MHz [10] (30.0 dBm)
>> * 2462 MHz [11] (30.0 dBm)
>> * 2467 MHz [12] (disabled)
>> * 2472 MHz [13] (disabled)
>> * 2484 MHz [14] (disabled)
>> Band 2:
>> Capabilities: 0x19e3
>> RX LDPC
>> HT20/HT40
>> Static SM Power Save
>> RX HT20 SGI
>> RX HT40 SGI
>> TX STBC
>> RX STBC 1-stream
>> Max AMSDU length: 7935 bytes
>> DSSS/CCK HT40
>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>> HT TX/RX MCS rate indexes supported: 0-15
>> VHT Capabilities (0x338001b2):
>> Max MPDU length: 11454
>> Supported Channel Width: neither 160 nor 80+80
>> RX LDPC
>> short GI (80 MHz)
>> TX STBC
>> RX antenna pattern consistency
>> TX antenna pattern consistency
>> VHT RX MCS set:
>> 1 streams: MCS 0-9
>> 2 streams: MCS 0-9
>> 3 streams: not supported
>> 4 streams: not supported
>> 5 streams: not supported
>> 6 streams: not supported
>> 7 streams: not supported
>> 8 streams: not supported
>> VHT RX highest supported: 0 Mbps
>> VHT TX MCS set:
>> 1 streams: MCS 0-9
>> 2 streams: MCS 0-9
>> 3 streams: not supported
>> 4 streams: not supported
>> 5 streams: not supported
>> 6 streams: not supported
>> 7 streams: not supported
>> 8 streams: not supported
>> VHT TX highest supported: 0 Mbps
>> Bitrates (non-HT):
>> * 6.0 Mbps
>> * 9.0 Mbps
>> * 12.0 Mbps
>> * 18.0 Mbps
>> * 24.0 Mbps
>> * 36.0 Mbps
>> * 48.0 Mbps
>> * 54.0 Mbps
>> Frequencies:
>> * 5180 MHz [36] (17.0 dBm)
>> * 5200 MHz [40] (17.0 dBm)
>> * 5220 MHz [44] (17.0 dBm)
>> * 5240 MHz [48] (17.0 dBm)
>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 1076 sec)
>> DFS CAC time: 60000 ms
>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 1076 sec)
>> DFS CAC time: 60000 ms
>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 1076 sec)
>> DFS CAC time: 60000 ms
>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 1076 sec)
>> DFS CAC time: 60000 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] (disabled)
>> * 5745 MHz [149] (30.0 dBm)
>> * 5765 MHz [153] (30.0 dBm)
>> * 5785 MHz [157] (30.0 dBm)
>> * 5805 MHz [161] (30.0 dBm)
>> * 5825 MHz [165] (30.0 dBm)
>> Supported commands:
>> * new_interface
>> * set_interface
>> * new_key
>> * start_ap
>> * new_station
>> * set_bss
>> * authenticate
>> * associate
>> * deauthenticate
>> * disassociate
>> * join_ibss
>> * remain_on_channel
>> * set_tx_bitrate_mask
>> * frame
>> * frame_wait_cancel
>> * set_wiphy_netns
>> * set_channel
>> * set_wds_peer
>> * probe_client
>> * set_noack_map
>> * register_beacons
>> * start_p2p_device
>> * set_mcast_rate
>> * testmode
>> * channel_switch
>> * Unknown command (104)
>> * connect
>> * disconnect
>> Supported TX frame types:
>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
>> 0xb0 0xc0 0xd0 0xe0 0xf0
>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>> Supported RX frame types:
>> * IBSS: 0x40 0xb0 0xc0 0xd0
>> * managed: 0x40 0xd0
>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>> * mesh point: 0xb0 0xc0 0xd0
>> * P2P-client: 0x40 0xd0
>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>> * P2P-device: 0x40 0xd0
>> software interface modes (can always be added):
>> * AP/VLAN
>> * monitor
>> valid interface combinations:
>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>> P2P-device } <= 1, #{ AP } <= 7,
>> total <= 8, #channels <= 1, STA/AP BI must match
>> HT Capability overrides:
>> * MCS: ff ff ff ff ff ff ff ff ff ff
>> * maximum A-MSDU length
>> * supported channel width
>> * short GI for 40 MHz
>> * max A-MPDU length exponent
>> * min MPDU start spacing
>> Device supports TX status socket option.
>> Device supports HT-IBSS.
>> Device supports SAE with AUTHENTICATE command
>> Device supports scan flush.
>> Device supports per-vif TX power setting
>> Driver supports a userspace MPM
>> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>> Device supports static SMPS
>> =====================================================
>>
>> I am grateful for any help here and do have some time to help
>> debugging the issue.
>>
>> Marcel
>>
>> --
>>
>> ------------------------------------------------------
>> This message is not intended to have
>> contractual effect
>> ------------------------------------------------------
>>
>> _______________________________________________
>> 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
--
Jorge Baranda
Research Engineer, MSc
jorge.baranda@cttc.es
Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
Av. Carl Friedrich Gauss, 7
08860 Castelldefels, Barcelona (Spain)
Tel: +34 93 645 29 00 Ext: 2171
Fax. +34 93 645 29 01
www.cttc.es
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-09 6:20 ` Jorge Baranda
@ 2015-09-09 7:43 ` Janusz Dziedzic
2015-09-09 7:49 ` Marcel H.
0 siblings, 1 reply; 22+ messages in thread
From: Janusz Dziedzic @ 2015-09-09 7:43 UTC (permalink / raw)
To: Jorge Baranda; +Cc: ath10k
On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
> Hi everyone,
>
> Reading this thread, I would like to share with people some doubts about it.
> @Marco, I imagine you want to run your WLE600VX device using the 802.11ac
> protocol, isn't it?
> @Janusz, with running wpa_supplicant on both computers, will the ad-hoc
> connection be established? I am starting with these tools and now, I am
> getting used to know how they work. I was creating the ad-hoc connection
> with the iw tool.
>
Yes you should use wpa_supplicant on both PC.
In the future probably someone will add IBSS-VHT support also for iw.
BR
Janusz
> Thanks,
>
>
>
> El 09/09/15 07:50, Janusz Dziedzic escribió:
>
>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>
>>> Hi everyone,
>>> I have an interesting issue - I'm trying to run the QCA9882 based card
>>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>>> 80MHz width resolves in the following:
>>>
>> You should run IBSS using fresh wpa_supplicant (best latest code). By
>> default should run in 80MHz.
>> Other case is your regulatory - are you allow to use 80MHz on channel
>> 157? First try 5180.
>>
>> eg. of wpa_supplicant config:
>>
>> network = {
>> ssid="test_ibss"
>> key_mgmt=NONE
>> mode=1
>> frequency=5180
>> }
>>
>> BR
>> Janusz
>>
>>> Interface wlan0
>>> ifindex 5
>>> wdev 0x1
>>> addr 04:f0:21:1b:5f:3b
>>> ssid my-mesh-network
>>> type IBSS
>>> wiphy 0
>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>> command failed: Invalid argument (-22)
>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>> command failed: Invalid argument (-22)
>>>
>>>
>>> More info:
>>> =====================================================
>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
>>> Network Adapter
>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>> Capabilities: [40] Power Management version 2
>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>> Capabilities: [70] Express Endpoint, MSI 00
>>> Capabilities: [100] Advanced Error Reporting
>>> Capabilities: [140] Virtual Channel
>>> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>>> Kernel driver in use: ath10k_pci
>>>
>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>> country US: DFS-FCC
>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>
>>>
>>> root@voyage2:/opt/ca_node/bin# uname -a
>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>>> GMT 2015 i686 GNU/Linux
>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10
>>> .config)
>>>
>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>> (this is from the 'main' directory in the
>>> https://github.com/kvalo/ath10k-firmware)
>>>
>>>
>>> Wiphy phy0
>>> max # scan SSIDs: 16
>>> max scan IEs length: 195 bytes
>>> Retry short limit: 7
>>> Retry long limit: 4
>>> Coverage class: 0 (up to 0m)
>>> Device supports RSN-IBSS.
>>> Device supports AP-side u-APSD.
>>> Supported Ciphers:
>>> * WEP40 (00-0f-ac:1)
>>> * WEP104 (00-0f-ac:5)
>>> * TKIP (00-0f-ac:2)
>>> * CCMP (00-0f-ac:4)
>>> * CMAC (00-0f-ac:6)
>>> Available Antennas: TX 0x3 RX 0x3
>>> Configured Antennas: TX 0x3 RX 0x3
>>> Supported interface modes:
>>> * IBSS
>>> * managed
>>> * AP
>>> * AP/VLAN
>>> * monitor
>>> * P2P-client
>>> * P2P-GO
>>> * P2P-device
>>> Band 1:
>>> Capabilities: 0x19e3
>>> RX LDPC
>>> HT20/HT40
>>> Static SM Power Save
>>> RX HT20 SGI
>>> RX HT40 SGI
>>> TX STBC
>>> RX STBC 1-stream
>>> Max AMSDU length: 7935 bytes
>>> DSSS/CCK HT40
>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>> HT TX/RX MCS rate indexes supported: 0-15
>>> VHT Capabilities (0x338001b2):
>>> Max MPDU length: 11454
>>> Supported Channel Width: neither 160 nor 80+80
>>> RX LDPC
>>> short GI (80 MHz)
>>> TX STBC
>>> RX antenna pattern consistency
>>> TX antenna pattern consistency
>>> VHT RX MCS set:
>>> 1 streams: MCS 0-9
>>> 2 streams: MCS 0-9
>>> 3 streams: not supported
>>> 4 streams: not supported
>>> 5 streams: not supported
>>> 6 streams: not supported
>>> 7 streams: not supported
>>> 8 streams: not supported
>>> VHT RX highest supported: 0 Mbps
>>> VHT TX MCS set:
>>> 1 streams: MCS 0-9
>>> 2 streams: MCS 0-9
>>> 3 streams: not supported
>>> 4 streams: not supported
>>> 5 streams: not supported
>>> 6 streams: not supported
>>> 7 streams: not supported
>>> 8 streams: not supported
>>> VHT TX highest supported: 0 Mbps
>>> Bitrates (non-HT):
>>> * 1.0 Mbps
>>> * 2.0 Mbps (short preamble supported)
>>> * 5.5 Mbps (short preamble supported)
>>> * 11.0 Mbps (short preamble supported)
>>> * 6.0 Mbps
>>> * 9.0 Mbps
>>> * 12.0 Mbps
>>> * 18.0 Mbps
>>> * 24.0 Mbps
>>> * 36.0 Mbps
>>> * 48.0 Mbps
>>> * 54.0 Mbps
>>> Frequencies:
>>> * 2412 MHz [1] (30.0 dBm)
>>> * 2417 MHz [2] (30.0 dBm)
>>> * 2422 MHz [3] (30.0 dBm)
>>> * 2427 MHz [4] (30.0 dBm)
>>> * 2432 MHz [5] (30.0 dBm)
>>> * 2437 MHz [6] (30.0 dBm)
>>> * 2442 MHz [7] (30.0 dBm)
>>> * 2447 MHz [8] (30.0 dBm)
>>> * 2452 MHz [9] (30.0 dBm)
>>> * 2457 MHz [10] (30.0 dBm)
>>> * 2462 MHz [11] (30.0 dBm)
>>> * 2467 MHz [12] (disabled)
>>> * 2472 MHz [13] (disabled)
>>> * 2484 MHz [14] (disabled)
>>> Band 2:
>>> Capabilities: 0x19e3
>>> RX LDPC
>>> HT20/HT40
>>> Static SM Power Save
>>> RX HT20 SGI
>>> RX HT40 SGI
>>> TX STBC
>>> RX STBC 1-stream
>>> Max AMSDU length: 7935 bytes
>>> DSSS/CCK HT40
>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>> HT TX/RX MCS rate indexes supported: 0-15
>>> VHT Capabilities (0x338001b2):
>>> Max MPDU length: 11454
>>> Supported Channel Width: neither 160 nor 80+80
>>> RX LDPC
>>> short GI (80 MHz)
>>> TX STBC
>>> RX antenna pattern consistency
>>> TX antenna pattern consistency
>>> VHT RX MCS set:
>>> 1 streams: MCS 0-9
>>> 2 streams: MCS 0-9
>>> 3 streams: not supported
>>> 4 streams: not supported
>>> 5 streams: not supported
>>> 6 streams: not supported
>>> 7 streams: not supported
>>> 8 streams: not supported
>>> VHT RX highest supported: 0 Mbps
>>> VHT TX MCS set:
>>> 1 streams: MCS 0-9
>>> 2 streams: MCS 0-9
>>> 3 streams: not supported
>>> 4 streams: not supported
>>> 5 streams: not supported
>>> 6 streams: not supported
>>> 7 streams: not supported
>>> 8 streams: not supported
>>> VHT TX highest supported: 0 Mbps
>>> Bitrates (non-HT):
>>> * 6.0 Mbps
>>> * 9.0 Mbps
>>> * 12.0 Mbps
>>> * 18.0 Mbps
>>> * 24.0 Mbps
>>> * 36.0 Mbps
>>> * 48.0 Mbps
>>> * 54.0 Mbps
>>> Frequencies:
>>> * 5180 MHz [36] (17.0 dBm)
>>> * 5200 MHz [40] (17.0 dBm)
>>> * 5220 MHz [44] (17.0 dBm)
>>> * 5240 MHz [48] (17.0 dBm)
>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>> DFS state: usable (for 1076 sec)
>>> DFS CAC time: 60000 ms
>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>> DFS state: usable (for 1076 sec)
>>> DFS CAC time: 60000 ms
>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>> DFS state: usable (for 1076 sec)
>>> DFS CAC time: 60000 ms
>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>> DFS state: usable (for 1076 sec)
>>> DFS CAC time: 60000 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] (disabled)
>>> * 5745 MHz [149] (30.0 dBm)
>>> * 5765 MHz [153] (30.0 dBm)
>>> * 5785 MHz [157] (30.0 dBm)
>>> * 5805 MHz [161] (30.0 dBm)
>>> * 5825 MHz [165] (30.0 dBm)
>>> Supported commands:
>>> * new_interface
>>> * set_interface
>>> * new_key
>>> * start_ap
>>> * new_station
>>> * set_bss
>>> * authenticate
>>> * associate
>>> * deauthenticate
>>> * disassociate
>>> * join_ibss
>>> * remain_on_channel
>>> * set_tx_bitrate_mask
>>> * frame
>>> * frame_wait_cancel
>>> * set_wiphy_netns
>>> * set_channel
>>> * set_wds_peer
>>> * probe_client
>>> * set_noack_map
>>> * register_beacons
>>> * start_p2p_device
>>> * set_mcast_rate
>>> * testmode
>>> * channel_switch
>>> * Unknown command (104)
>>> * connect
>>> * disconnect
>>> Supported TX frame types:
>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>> Supported RX frame types:
>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>> * managed: 0x40 0xd0
>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>> * mesh point: 0xb0 0xc0 0xd0
>>> * P2P-client: 0x40 0xd0
>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>> * P2P-device: 0x40 0xd0
>>> software interface modes (can always be added):
>>> * AP/VLAN
>>> * monitor
>>> valid interface combinations:
>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>> P2P-device } <= 1, #{ AP } <= 7,
>>> total <= 8, #channels <= 1, STA/AP BI must match
>>> HT Capability overrides:
>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>> * maximum A-MSDU length
>>> * supported channel width
>>> * short GI for 40 MHz
>>> * max A-MPDU length exponent
>>> * min MPDU start spacing
>>> Device supports TX status socket option.
>>> Device supports HT-IBSS.
>>> Device supports SAE with AUTHENTICATE command
>>> Device supports scan flush.
>>> Device supports per-vif TX power setting
>>> Driver supports a userspace MPM
>>> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>>> Device supports static SMPS
>>> =====================================================
>>>
>>> I am grateful for any help here and do have some time to help
>>> debugging the issue.
>>>
>>> Marcel
>>>
>>> --
>>>
>>> ------------------------------------------------------
>>> This message is not intended to have
>>> contractual effect
>>> ------------------------------------------------------
>>>
>>> _______________________________________________
>>> 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
>
>
>
> --
> Jorge Baranda
> Research Engineer, MSc
> jorge.baranda@cttc.es
>
> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
> Av. Carl Friedrich Gauss, 7
> 08860 Castelldefels, Barcelona (Spain)
> Tel: +34 93 645 29 00 Ext: 2171
> Fax. +34 93 645 29 01
> www.cttc.es
>
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-09 7:43 ` Janusz Dziedzic
@ 2015-09-09 7:49 ` Marcel H.
2015-09-09 9:46 ` Marcel H.
2015-09-09 11:06 ` Janusz Dziedzic
0 siblings, 2 replies; 22+ messages in thread
From: Marcel H. @ 2015-09-09 7:49 UTC (permalink / raw)
To: ath10k
Thanks for the response, unfortunately this is the result of defining
the center frequency:
root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
command failed: Device or resource busy (-16)
Also, using wpa_supplicant does not work using the following config:
root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
ap_scan=2
ctrl_interface=/run/wpa_supplicant
update_config=1
device_type=0-00000000-0
network={
scan_ssid=1
key_mgmt=NONE
priority=1
ssid="ibss"
mode=1
frequency=5180
}
running as:
wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D nl80211,wext
root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
Interface wlan0
ifindex 5
wdev 0x100000001
addr 04:f0:21:1b:5f:3d
ssid ibss-rsn
type IBSS
wiphy 1
channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
root@voyage1:/opt/ca_node/etc# iw phy phy1 info
Wiphy phy1
DFS state: usable (for 46424 sec)
DFS CAC time: 60000 ms
* 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
DFS state: usable (for 46424 sec)
DFS CAC time: 60000 ms
* 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
DFS state: usable (for 46424 sec)
DFS CAC time: 60000 ms
* 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
DFS state: usable (for 46424 sec)
Its fallbacking to 20MHz channels, which is even less than 40MHz
channels set manually by iw
How recent wpa_supplicat shall I try? I believe this it quite recent:
root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
wpa_supplicant v2.3
Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
Re. the regulatory settings:
root@voyage1:/opt/ca_node/etc# iw reg get
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 17), (N/A)
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
Any other thoughts?
Marcel
On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
<janusz.dziedzic@tieto.com> wrote:
> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>> Hi everyone,
>>
>> Reading this thread, I would like to share with people some doubts about it.
>> @Marco, I imagine you want to run your WLE600VX device using the 802.11ac
>> protocol, isn't it?
>> @Janusz, with running wpa_supplicant on both computers, will the ad-hoc
>> connection be established? I am starting with these tools and now, I am
>> getting used to know how they work. I was creating the ad-hoc connection
>> with the iw tool.
>>
> Yes you should use wpa_supplicant on both PC.
> In the future probably someone will add IBSS-VHT support also for iw.
>
> BR
> Janusz
>
>> Thanks,
>>
>>
>>
>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>
>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>
>>>> Hi everyone,
>>>> I have an interesting issue - I'm trying to run the QCA9882 based card
>>>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>>>> 80MHz width resolves in the following:
>>>>
>>> You should run IBSS using fresh wpa_supplicant (best latest code). By
>>> default should run in 80MHz.
>>> Other case is your regulatory - are you allow to use 80MHz on channel
>>> 157? First try 5180.
>>>
>>> eg. of wpa_supplicant config:
>>>
>>> network = {
>>> ssid="test_ibss"
>>> key_mgmt=NONE
>>> mode=1
>>> frequency=5180
>>> }
>>>
>>> BR
>>> Janusz
>>>
>>>> Interface wlan0
>>>> ifindex 5
>>>> wdev 0x1
>>>> addr 04:f0:21:1b:5f:3b
>>>> ssid my-mesh-network
>>>> type IBSS
>>>> wiphy 0
>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>> command failed: Invalid argument (-22)
>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>> command failed: Invalid argument (-22)
>>>>
>>>>
>>>> More info:
>>>> =====================================================
>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
>>>> Network Adapter
>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>> Capabilities: [40] Power Management version 2
>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>> Capabilities: [100] Advanced Error Reporting
>>>> Capabilities: [140] Virtual Channel
>>>> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>>>> Kernel driver in use: ath10k_pci
>>>>
>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>> country US: DFS-FCC
>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>
>>>>
>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>>>> GMT 2015 i686 GNU/Linux
>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10
>>>> .config)
>>>>
>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>> (this is from the 'main' directory in the
>>>> https://github.com/kvalo/ath10k-firmware)
>>>>
>>>>
>>>> Wiphy phy0
>>>> max # scan SSIDs: 16
>>>> max scan IEs length: 195 bytes
>>>> Retry short limit: 7
>>>> Retry long limit: 4
>>>> Coverage class: 0 (up to 0m)
>>>> Device supports RSN-IBSS.
>>>> Device supports AP-side u-APSD.
>>>> Supported Ciphers:
>>>> * WEP40 (00-0f-ac:1)
>>>> * WEP104 (00-0f-ac:5)
>>>> * TKIP (00-0f-ac:2)
>>>> * CCMP (00-0f-ac:4)
>>>> * CMAC (00-0f-ac:6)
>>>> Available Antennas: TX 0x3 RX 0x3
>>>> Configured Antennas: TX 0x3 RX 0x3
>>>> Supported interface modes:
>>>> * IBSS
>>>> * managed
>>>> * AP
>>>> * AP/VLAN
>>>> * monitor
>>>> * P2P-client
>>>> * P2P-GO
>>>> * P2P-device
>>>> Band 1:
>>>> Capabilities: 0x19e3
>>>> RX LDPC
>>>> HT20/HT40
>>>> Static SM Power Save
>>>> RX HT20 SGI
>>>> RX HT40 SGI
>>>> TX STBC
>>>> RX STBC 1-stream
>>>> Max AMSDU length: 7935 bytes
>>>> DSSS/CCK HT40
>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>> VHT Capabilities (0x338001b2):
>>>> Max MPDU length: 11454
>>>> Supported Channel Width: neither 160 nor 80+80
>>>> RX LDPC
>>>> short GI (80 MHz)
>>>> TX STBC
>>>> RX antenna pattern consistency
>>>> TX antenna pattern consistency
>>>> VHT RX MCS set:
>>>> 1 streams: MCS 0-9
>>>> 2 streams: MCS 0-9
>>>> 3 streams: not supported
>>>> 4 streams: not supported
>>>> 5 streams: not supported
>>>> 6 streams: not supported
>>>> 7 streams: not supported
>>>> 8 streams: not supported
>>>> VHT RX highest supported: 0 Mbps
>>>> VHT TX MCS set:
>>>> 1 streams: MCS 0-9
>>>> 2 streams: MCS 0-9
>>>> 3 streams: not supported
>>>> 4 streams: not supported
>>>> 5 streams: not supported
>>>> 6 streams: not supported
>>>> 7 streams: not supported
>>>> 8 streams: not supported
>>>> VHT TX highest supported: 0 Mbps
>>>> Bitrates (non-HT):
>>>> * 1.0 Mbps
>>>> * 2.0 Mbps (short preamble supported)
>>>> * 5.5 Mbps (short preamble supported)
>>>> * 11.0 Mbps (short preamble supported)
>>>> * 6.0 Mbps
>>>> * 9.0 Mbps
>>>> * 12.0 Mbps
>>>> * 18.0 Mbps
>>>> * 24.0 Mbps
>>>> * 36.0 Mbps
>>>> * 48.0 Mbps
>>>> * 54.0 Mbps
>>>> Frequencies:
>>>> * 2412 MHz [1] (30.0 dBm)
>>>> * 2417 MHz [2] (30.0 dBm)
>>>> * 2422 MHz [3] (30.0 dBm)
>>>> * 2427 MHz [4] (30.0 dBm)
>>>> * 2432 MHz [5] (30.0 dBm)
>>>> * 2437 MHz [6] (30.0 dBm)
>>>> * 2442 MHz [7] (30.0 dBm)
>>>> * 2447 MHz [8] (30.0 dBm)
>>>> * 2452 MHz [9] (30.0 dBm)
>>>> * 2457 MHz [10] (30.0 dBm)
>>>> * 2462 MHz [11] (30.0 dBm)
>>>> * 2467 MHz [12] (disabled)
>>>> * 2472 MHz [13] (disabled)
>>>> * 2484 MHz [14] (disabled)
>>>> Band 2:
>>>> Capabilities: 0x19e3
>>>> RX LDPC
>>>> HT20/HT40
>>>> Static SM Power Save
>>>> RX HT20 SGI
>>>> RX HT40 SGI
>>>> TX STBC
>>>> RX STBC 1-stream
>>>> Max AMSDU length: 7935 bytes
>>>> DSSS/CCK HT40
>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>> VHT Capabilities (0x338001b2):
>>>> Max MPDU length: 11454
>>>> Supported Channel Width: neither 160 nor 80+80
>>>> RX LDPC
>>>> short GI (80 MHz)
>>>> TX STBC
>>>> RX antenna pattern consistency
>>>> TX antenna pattern consistency
>>>> VHT RX MCS set:
>>>> 1 streams: MCS 0-9
>>>> 2 streams: MCS 0-9
>>>> 3 streams: not supported
>>>> 4 streams: not supported
>>>> 5 streams: not supported
>>>> 6 streams: not supported
>>>> 7 streams: not supported
>>>> 8 streams: not supported
>>>> VHT RX highest supported: 0 Mbps
>>>> VHT TX MCS set:
>>>> 1 streams: MCS 0-9
>>>> 2 streams: MCS 0-9
>>>> 3 streams: not supported
>>>> 4 streams: not supported
>>>> 5 streams: not supported
>>>> 6 streams: not supported
>>>> 7 streams: not supported
>>>> 8 streams: not supported
>>>> VHT TX highest supported: 0 Mbps
>>>> Bitrates (non-HT):
>>>> * 6.0 Mbps
>>>> * 9.0 Mbps
>>>> * 12.0 Mbps
>>>> * 18.0 Mbps
>>>> * 24.0 Mbps
>>>> * 36.0 Mbps
>>>> * 48.0 Mbps
>>>> * 54.0 Mbps
>>>> Frequencies:
>>>> * 5180 MHz [36] (17.0 dBm)
>>>> * 5200 MHz [40] (17.0 dBm)
>>>> * 5220 MHz [44] (17.0 dBm)
>>>> * 5240 MHz [48] (17.0 dBm)
>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>> DFS state: usable (for 1076 sec)
>>>> DFS CAC time: 60000 ms
>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>> DFS state: usable (for 1076 sec)
>>>> DFS CAC time: 60000 ms
>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>> DFS state: usable (for 1076 sec)
>>>> DFS CAC time: 60000 ms
>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>> DFS state: usable (for 1076 sec)
>>>> DFS CAC time: 60000 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] (disabled)
>>>> * 5745 MHz [149] (30.0 dBm)
>>>> * 5765 MHz [153] (30.0 dBm)
>>>> * 5785 MHz [157] (30.0 dBm)
>>>> * 5805 MHz [161] (30.0 dBm)
>>>> * 5825 MHz [165] (30.0 dBm)
>>>> Supported commands:
>>>> * new_interface
>>>> * set_interface
>>>> * new_key
>>>> * start_ap
>>>> * new_station
>>>> * set_bss
>>>> * authenticate
>>>> * associate
>>>> * deauthenticate
>>>> * disassociate
>>>> * join_ibss
>>>> * remain_on_channel
>>>> * set_tx_bitrate_mask
>>>> * frame
>>>> * frame_wait_cancel
>>>> * set_wiphy_netns
>>>> * set_channel
>>>> * set_wds_peer
>>>> * probe_client
>>>> * set_noack_map
>>>> * register_beacons
>>>> * start_p2p_device
>>>> * set_mcast_rate
>>>> * testmode
>>>> * channel_switch
>>>> * Unknown command (104)
>>>> * connect
>>>> * disconnect
>>>> Supported TX frame types:
>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>> Supported RX frame types:
>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>> * managed: 0x40 0xd0
>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>> * mesh point: 0xb0 0xc0 0xd0
>>>> * P2P-client: 0x40 0xd0
>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>> * P2P-device: 0x40 0xd0
>>>> software interface modes (can always be added):
>>>> * AP/VLAN
>>>> * monitor
>>>> valid interface combinations:
>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>> HT Capability overrides:
>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>> * maximum A-MSDU length
>>>> * supported channel width
>>>> * short GI for 40 MHz
>>>> * max A-MPDU length exponent
>>>> * min MPDU start spacing
>>>> Device supports TX status socket option.
>>>> Device supports HT-IBSS.
>>>> Device supports SAE with AUTHENTICATE command
>>>> Device supports scan flush.
>>>> Device supports per-vif TX power setting
>>>> Driver supports a userspace MPM
>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>>>> Device supports static SMPS
>>>> =====================================================
>>>>
>>>> I am grateful for any help here and do have some time to help
>>>> debugging the issue.
>>>>
>>>> Marcel
>>>>
>>>> --
>>>>
>>>> ------------------------------------------------------
>>>> This message is not intended to have
>>>> contractual effect
>>>> ------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> 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
>>
>>
>>
>> --
>> Jorge Baranda
>> Research Engineer, MSc
>> jorge.baranda@cttc.es
>>
>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>> Av. Carl Friedrich Gauss, 7
>> 08860 Castelldefels, Barcelona (Spain)
>> Tel: +34 93 645 29 00 Ext: 2171
>> Fax. +34 93 645 29 01
>> www.cttc.es
>>
>>
>>
>> _______________________________________________
>> 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
--
------------------------------------------------------
This message is not intended to have
contractual effect
------------------------------------------------------
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-09 7:49 ` Marcel H.
@ 2015-09-09 9:46 ` Marcel H.
2015-09-09 10:59 ` Harms, Hannes
2015-09-09 11:09 ` Janusz Dziedzic
2015-09-09 11:06 ` Janusz Dziedzic
1 sibling, 2 replies; 22+ messages in thread
From: Marcel H. @ 2015-09-09 9:46 UTC (permalink / raw)
To: ath10k
May I ask someone for support on this one?
We would really like to make this work and I'm running out of ideas -
is there any way do turn detailed debugging on to get a better
understanding why do I get the following message back? ->
root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
command failed: Device or resource busy (-16)
Thanks,
Marcel
On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
> Thanks for the response, unfortunately this is the result of defining
> the center frequency:
>
> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
> command failed: Device or resource busy (-16)
>
> Also, using wpa_supplicant does not work using the following config:
>
> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
> ap_scan=2
> ctrl_interface=/run/wpa_supplicant
> update_config=1
> device_type=0-00000000-0
>
> network={
> scan_ssid=1
> key_mgmt=NONE
> priority=1
> ssid="ibss"
> mode=1
> frequency=5180
> }
>
> running as:
> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D nl80211,wext
>
>
>
> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
> Interface wlan0
> ifindex 5
> wdev 0x100000001
> addr 04:f0:21:1b:5f:3d
> ssid ibss-rsn
> type IBSS
> wiphy 1
> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>
> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
> Wiphy phy1
> DFS state: usable (for 46424 sec)
> DFS CAC time: 60000 ms
> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 46424 sec)
> DFS CAC time: 60000 ms
> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 46424 sec)
> DFS CAC time: 60000 ms
> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 46424 sec)
> Its fallbacking to 20MHz channels, which is even less than 40MHz
> channels set manually by iw
>
>
> How recent wpa_supplicat shall I try? I believe this it quite recent:
>
> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
> wpa_supplicant v2.3
> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>
>
> Re. the regulatory settings:
>
> root@voyage1:/opt/ca_node/etc# iw reg get
> country US: DFS-FCC
> (2402 - 2472 @ 40), (N/A, 30), (N/A)
> (5170 - 5250 @ 80), (N/A, 17), (N/A)
> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
> (5735 - 5835 @ 80), (N/A, 30), (N/A)
> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>
>
> Any other thoughts?
>
> Marcel
>
> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
> <janusz.dziedzic@tieto.com> wrote:
>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>> Hi everyone,
>>>
>>> Reading this thread, I would like to share with people some doubts about it.
>>> @Marco, I imagine you want to run your WLE600VX device using the 802.11ac
>>> protocol, isn't it?
>>> @Janusz, with running wpa_supplicant on both computers, will the ad-hoc
>>> connection be established? I am starting with these tools and now, I am
>>> getting used to know how they work. I was creating the ad-hoc connection
>>> with the iw tool.
>>>
>> Yes you should use wpa_supplicant on both PC.
>> In the future probably someone will add IBSS-VHT support also for iw.
>>
>> BR
>> Janusz
>>
>>> Thanks,
>>>
>>>
>>>
>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>
>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>
>>>>> Hi everyone,
>>>>> I have an interesting issue - I'm trying to run the QCA9882 based card
>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>>>>> 80MHz width resolves in the following:
>>>>>
>>>> You should run IBSS using fresh wpa_supplicant (best latest code). By
>>>> default should run in 80MHz.
>>>> Other case is your regulatory - are you allow to use 80MHz on channel
>>>> 157? First try 5180.
>>>>
>>>> eg. of wpa_supplicant config:
>>>>
>>>> network = {
>>>> ssid="test_ibss"
>>>> key_mgmt=NONE
>>>> mode=1
>>>> frequency=5180
>>>> }
>>>>
>>>> BR
>>>> Janusz
>>>>
>>>>> Interface wlan0
>>>>> ifindex 5
>>>>> wdev 0x1
>>>>> addr 04:f0:21:1b:5f:3b
>>>>> ssid my-mesh-network
>>>>> type IBSS
>>>>> wiphy 0
>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>> command failed: Invalid argument (-22)
>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>> command failed: Invalid argument (-22)
>>>>>
>>>>>
>>>>> More info:
>>>>> =====================================================
>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
>>>>> Network Adapter
>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>> Capabilities: [40] Power Management version 2
>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>> Capabilities: [100] Advanced Error Reporting
>>>>> Capabilities: [140] Virtual Channel
>>>>> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>>>>> Kernel driver in use: ath10k_pci
>>>>>
>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>> country US: DFS-FCC
>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>
>>>>>
>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>>>>> GMT 2015 i686 GNU/Linux
>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10
>>>>> .config)
>>>>>
>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>> (this is from the 'main' directory in the
>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>
>>>>>
>>>>> Wiphy phy0
>>>>> max # scan SSIDs: 16
>>>>> max scan IEs length: 195 bytes
>>>>> Retry short limit: 7
>>>>> Retry long limit: 4
>>>>> Coverage class: 0 (up to 0m)
>>>>> Device supports RSN-IBSS.
>>>>> Device supports AP-side u-APSD.
>>>>> Supported Ciphers:
>>>>> * WEP40 (00-0f-ac:1)
>>>>> * WEP104 (00-0f-ac:5)
>>>>> * TKIP (00-0f-ac:2)
>>>>> * CCMP (00-0f-ac:4)
>>>>> * CMAC (00-0f-ac:6)
>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>> Supported interface modes:
>>>>> * IBSS
>>>>> * managed
>>>>> * AP
>>>>> * AP/VLAN
>>>>> * monitor
>>>>> * P2P-client
>>>>> * P2P-GO
>>>>> * P2P-device
>>>>> Band 1:
>>>>> Capabilities: 0x19e3
>>>>> RX LDPC
>>>>> HT20/HT40
>>>>> Static SM Power Save
>>>>> RX HT20 SGI
>>>>> RX HT40 SGI
>>>>> TX STBC
>>>>> RX STBC 1-stream
>>>>> Max AMSDU length: 7935 bytes
>>>>> DSSS/CCK HT40
>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>> VHT Capabilities (0x338001b2):
>>>>> Max MPDU length: 11454
>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>> RX LDPC
>>>>> short GI (80 MHz)
>>>>> TX STBC
>>>>> RX antenna pattern consistency
>>>>> TX antenna pattern consistency
>>>>> VHT RX MCS set:
>>>>> 1 streams: MCS 0-9
>>>>> 2 streams: MCS 0-9
>>>>> 3 streams: not supported
>>>>> 4 streams: not supported
>>>>> 5 streams: not supported
>>>>> 6 streams: not supported
>>>>> 7 streams: not supported
>>>>> 8 streams: not supported
>>>>> VHT RX highest supported: 0 Mbps
>>>>> VHT TX MCS set:
>>>>> 1 streams: MCS 0-9
>>>>> 2 streams: MCS 0-9
>>>>> 3 streams: not supported
>>>>> 4 streams: not supported
>>>>> 5 streams: not supported
>>>>> 6 streams: not supported
>>>>> 7 streams: not supported
>>>>> 8 streams: not supported
>>>>> VHT TX highest supported: 0 Mbps
>>>>> Bitrates (non-HT):
>>>>> * 1.0 Mbps
>>>>> * 2.0 Mbps (short preamble supported)
>>>>> * 5.5 Mbps (short preamble supported)
>>>>> * 11.0 Mbps (short preamble supported)
>>>>> * 6.0 Mbps
>>>>> * 9.0 Mbps
>>>>> * 12.0 Mbps
>>>>> * 18.0 Mbps
>>>>> * 24.0 Mbps
>>>>> * 36.0 Mbps
>>>>> * 48.0 Mbps
>>>>> * 54.0 Mbps
>>>>> Frequencies:
>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>> * 2467 MHz [12] (disabled)
>>>>> * 2472 MHz [13] (disabled)
>>>>> * 2484 MHz [14] (disabled)
>>>>> Band 2:
>>>>> Capabilities: 0x19e3
>>>>> RX LDPC
>>>>> HT20/HT40
>>>>> Static SM Power Save
>>>>> RX HT20 SGI
>>>>> RX HT40 SGI
>>>>> TX STBC
>>>>> RX STBC 1-stream
>>>>> Max AMSDU length: 7935 bytes
>>>>> DSSS/CCK HT40
>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>> VHT Capabilities (0x338001b2):
>>>>> Max MPDU length: 11454
>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>> RX LDPC
>>>>> short GI (80 MHz)
>>>>> TX STBC
>>>>> RX antenna pattern consistency
>>>>> TX antenna pattern consistency
>>>>> VHT RX MCS set:
>>>>> 1 streams: MCS 0-9
>>>>> 2 streams: MCS 0-9
>>>>> 3 streams: not supported
>>>>> 4 streams: not supported
>>>>> 5 streams: not supported
>>>>> 6 streams: not supported
>>>>> 7 streams: not supported
>>>>> 8 streams: not supported
>>>>> VHT RX highest supported: 0 Mbps
>>>>> VHT TX MCS set:
>>>>> 1 streams: MCS 0-9
>>>>> 2 streams: MCS 0-9
>>>>> 3 streams: not supported
>>>>> 4 streams: not supported
>>>>> 5 streams: not supported
>>>>> 6 streams: not supported
>>>>> 7 streams: not supported
>>>>> 8 streams: not supported
>>>>> VHT TX highest supported: 0 Mbps
>>>>> Bitrates (non-HT):
>>>>> * 6.0 Mbps
>>>>> * 9.0 Mbps
>>>>> * 12.0 Mbps
>>>>> * 18.0 Mbps
>>>>> * 24.0 Mbps
>>>>> * 36.0 Mbps
>>>>> * 48.0 Mbps
>>>>> * 54.0 Mbps
>>>>> Frequencies:
>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>> DFS state: usable (for 1076 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>> DFS state: usable (for 1076 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>> DFS state: usable (for 1076 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>> DFS state: usable (for 1076 sec)
>>>>> DFS CAC time: 60000 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] (disabled)
>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>> Supported commands:
>>>>> * new_interface
>>>>> * set_interface
>>>>> * new_key
>>>>> * start_ap
>>>>> * new_station
>>>>> * set_bss
>>>>> * authenticate
>>>>> * associate
>>>>> * deauthenticate
>>>>> * disassociate
>>>>> * join_ibss
>>>>> * remain_on_channel
>>>>> * set_tx_bitrate_mask
>>>>> * frame
>>>>> * frame_wait_cancel
>>>>> * set_wiphy_netns
>>>>> * set_channel
>>>>> * set_wds_peer
>>>>> * probe_client
>>>>> * set_noack_map
>>>>> * register_beacons
>>>>> * start_p2p_device
>>>>> * set_mcast_rate
>>>>> * testmode
>>>>> * channel_switch
>>>>> * Unknown command (104)
>>>>> * connect
>>>>> * disconnect
>>>>> Supported TX frame types:
>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> Supported RX frame types:
>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>> * managed: 0x40 0xd0
>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>> * P2P-client: 0x40 0xd0
>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>> * P2P-device: 0x40 0xd0
>>>>> software interface modes (can always be added):
>>>>> * AP/VLAN
>>>>> * monitor
>>>>> valid interface combinations:
>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>> HT Capability overrides:
>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>> * maximum A-MSDU length
>>>>> * supported channel width
>>>>> * short GI for 40 MHz
>>>>> * max A-MPDU length exponent
>>>>> * min MPDU start spacing
>>>>> Device supports TX status socket option.
>>>>> Device supports HT-IBSS.
>>>>> Device supports SAE with AUTHENTICATE command
>>>>> Device supports scan flush.
>>>>> Device supports per-vif TX power setting
>>>>> Driver supports a userspace MPM
>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>>>>> Device supports static SMPS
>>>>> =====================================================
>>>>>
>>>>> I am grateful for any help here and do have some time to help
>>>>> debugging the issue.
>>>>>
>>>>> Marcel
>>>>>
>>>>> --
>>>>>
>>>>> ------------------------------------------------------
>>>>> This message is not intended to have
>>>>> contractual effect
>>>>> ------------------------------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>>
>>>
>>> --
>>> Jorge Baranda
>>> Research Engineer, MSc
>>> jorge.baranda@cttc.es
>>>
>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>> Av. Carl Friedrich Gauss, 7
>>> 08860 Castelldefels, Barcelona (Spain)
>>> Tel: +34 93 645 29 00 Ext: 2171
>>> Fax. +34 93 645 29 01
>>> www.cttc.es
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
>
> --
>
> ------------------------------------------------------
> This message is not intended to have
> contractual effect
> ------------------------------------------------------
--
------------------------------------------------------
This message is not intended to have
contractual effect
------------------------------------------------------
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-09 9:46 ` Marcel H.
@ 2015-09-09 10:59 ` Harms, Hannes
2015-09-09 11:08 ` Janusz Dziedzic
2015-09-09 11:08 ` [SPAM] " Jorge Baranda
2015-09-09 11:09 ` Janusz Dziedzic
1 sibling, 2 replies; 22+ messages in thread
From: Harms, Hannes @ 2015-09-09 10:59 UTC (permalink / raw)
To: ath10k
Hi,
I have WLE900VX working in IBSS mode and 80 Mhz with Candela Kernel 4.2.
For me also the latest wpa_supplicant was not able to activate 80MHz by
default , I don't no why.
The only way I found to get it working was to modify
wpa_supplicant/wpa_supplicant.c
Commit following two lines in wpa_supplicant.c like this :
//if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
// return;
That was all for me to get it working.
wpa_supplicant config file:
# Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is ignored)
CONFIG_LIBNL32=y
# Support VHT overrides (disable VHT, mask MCS rates, etc.)
CONFIG_VHT_OVERRIDES=y
# Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
CONFIG_HT_OVERRIDES=y
# IEEE 802.11n (High Throughput) support (mainly for AP mode)
CONFIG_IEEE80211N=y
# IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
# (depends on CONFIG_IEEE80211N)
CONFIG_IEEE80211AC=y
# IEEE 802.11w (management frame protection), also known as PMF
# Driver support is also needed for IEEE 802.11w.
CONFIG_IEEE80211W=y
Am 09.09.2015 um 11:46 schrieb Marcel H.:
> May I ask someone for support on this one?
> We would really like to make this work and I'm running out of ideas -
> is there any way do turn detailed debugging on to get a better
> understanding why do I get the following message back? ->
>
> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
> command failed: Device or resource busy (-16)
>
> Thanks,
> Marcel
>
> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>> Thanks for the response, unfortunately this is the result of defining
>> the center frequency:
>>
>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>> command failed: Device or resource busy (-16)
>>
>> Also, using wpa_supplicant does not work using the following config:
>>
>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>> ap_scan=2
>> ctrl_interface=/run/wpa_supplicant
>> update_config=1
>> device_type=0-00000000-0
>>
>> network={
>> scan_ssid=1
>> key_mgmt=NONE
>> priority=1
>> ssid="ibss"
>> mode=1
>> frequency=5180
>> }
>>
>> running as:
>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D nl80211,wext
>>
>>
>>
>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>> Interface wlan0
>> ifindex 5
>> wdev 0x100000001
>> addr 04:f0:21:1b:5f:3d
>> ssid ibss-rsn
>> type IBSS
>> wiphy 1
>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>
>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>> Wiphy phy1
>> DFS state: usable (for 46424 sec)
>> DFS CAC time: 60000 ms
>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 46424 sec)
>> DFS CAC time: 60000 ms
>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 46424 sec)
>> DFS CAC time: 60000 ms
>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 46424 sec)
>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>> channels set manually by iw
>>
>>
>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>
>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>> wpa_supplicant v2.3
>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>
>>
>> Re. the regulatory settings:
>>
>> root@voyage1:/opt/ca_node/etc# iw reg get
>> country US: DFS-FCC
>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>
>>
>> Any other thoughts?
>>
>> Marcel
>>
>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>> <janusz.dziedzic@tieto.com> wrote:
>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>>> Hi everyone,
>>>>
>>>> Reading this thread, I would like to share with people some doubts about it.
>>>> @Marco, I imagine you want to run your WLE600VX device using the 802.11ac
>>>> protocol, isn't it?
>>>> @Janusz, with running wpa_supplicant on both computers, will the ad-hoc
>>>> connection be established? I am starting with these tools and now, I am
>>>> getting used to know how they work. I was creating the ad-hoc connection
>>>> with the iw tool.
>>>>
>>> Yes you should use wpa_supplicant on both PC.
>>> In the future probably someone will add IBSS-VHT support also for iw.
>>>
>>> BR
>>> Janusz
>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>
>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>> Hi everyone,
>>>>>> I have an interesting issue - I'm trying to run the QCA9882 based card
>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>>>>>> 80MHz width resolves in the following:
>>>>>>
>>>>> You should run IBSS using fresh wpa_supplicant (best latest code). By
>>>>> default should run in 80MHz.
>>>>> Other case is your regulatory - are you allow to use 80MHz on channel
>>>>> 157? First try 5180.
>>>>>
>>>>> eg. of wpa_supplicant config:
>>>>>
>>>>> network = {
>>>>> ssid="test_ibss"
>>>>> key_mgmt=NONE
>>>>> mode=1
>>>>> frequency=5180
>>>>> }
>>>>>
>>>>> BR
>>>>> Janusz
>>>>>
>>>>>> Interface wlan0
>>>>>> ifindex 5
>>>>>> wdev 0x1
>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>> ssid my-mesh-network
>>>>>> type IBSS
>>>>>> wiphy 0
>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>> command failed: Invalid argument (-22)
>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>> command failed: Invalid argument (-22)
>>>>>>
>>>>>>
>>>>>> More info:
>>>>>> =====================================================
>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
>>>>>> Network Adapter
>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>> Capabilities: [40] Power Management version 2
>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>> Capabilities: [140] Virtual Channel
>>>>>> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>>>>>> Kernel driver in use: ath10k_pci
>>>>>>
>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>> country US: DFS-FCC
>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>
>>>>>>
>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>>>>>> GMT 2015 i686 GNU/Linux
>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10
>>>>>> .config)
>>>>>>
>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>> (this is from the 'main' directory in the
>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>
>>>>>>
>>>>>> Wiphy phy0
>>>>>> max # scan SSIDs: 16
>>>>>> max scan IEs length: 195 bytes
>>>>>> Retry short limit: 7
>>>>>> Retry long limit: 4
>>>>>> Coverage class: 0 (up to 0m)
>>>>>> Device supports RSN-IBSS.
>>>>>> Device supports AP-side u-APSD.
>>>>>> Supported Ciphers:
>>>>>> * WEP40 (00-0f-ac:1)
>>>>>> * WEP104 (00-0f-ac:5)
>>>>>> * TKIP (00-0f-ac:2)
>>>>>> * CCMP (00-0f-ac:4)
>>>>>> * CMAC (00-0f-ac:6)
>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>> Supported interface modes:
>>>>>> * IBSS
>>>>>> * managed
>>>>>> * AP
>>>>>> * AP/VLAN
>>>>>> * monitor
>>>>>> * P2P-client
>>>>>> * P2P-GO
>>>>>> * P2P-device
>>>>>> Band 1:
>>>>>> Capabilities: 0x19e3
>>>>>> RX LDPC
>>>>>> HT20/HT40
>>>>>> Static SM Power Save
>>>>>> RX HT20 SGI
>>>>>> RX HT40 SGI
>>>>>> TX STBC
>>>>>> RX STBC 1-stream
>>>>>> Max AMSDU length: 7935 bytes
>>>>>> DSSS/CCK HT40
>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>> VHT Capabilities (0x338001b2):
>>>>>> Max MPDU length: 11454
>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>> RX LDPC
>>>>>> short GI (80 MHz)
>>>>>> TX STBC
>>>>>> RX antenna pattern consistency
>>>>>> TX antenna pattern consistency
>>>>>> VHT RX MCS set:
>>>>>> 1 streams: MCS 0-9
>>>>>> 2 streams: MCS 0-9
>>>>>> 3 streams: not supported
>>>>>> 4 streams: not supported
>>>>>> 5 streams: not supported
>>>>>> 6 streams: not supported
>>>>>> 7 streams: not supported
>>>>>> 8 streams: not supported
>>>>>> VHT RX highest supported: 0 Mbps
>>>>>> VHT TX MCS set:
>>>>>> 1 streams: MCS 0-9
>>>>>> 2 streams: MCS 0-9
>>>>>> 3 streams: not supported
>>>>>> 4 streams: not supported
>>>>>> 5 streams: not supported
>>>>>> 6 streams: not supported
>>>>>> 7 streams: not supported
>>>>>> 8 streams: not supported
>>>>>> VHT TX highest supported: 0 Mbps
>>>>>> Bitrates (non-HT):
>>>>>> * 1.0 Mbps
>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>> * 6.0 Mbps
>>>>>> * 9.0 Mbps
>>>>>> * 12.0 Mbps
>>>>>> * 18.0 Mbps
>>>>>> * 24.0 Mbps
>>>>>> * 36.0 Mbps
>>>>>> * 48.0 Mbps
>>>>>> * 54.0 Mbps
>>>>>> Frequencies:
>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>> * 2467 MHz [12] (disabled)
>>>>>> * 2472 MHz [13] (disabled)
>>>>>> * 2484 MHz [14] (disabled)
>>>>>> Band 2:
>>>>>> Capabilities: 0x19e3
>>>>>> RX LDPC
>>>>>> HT20/HT40
>>>>>> Static SM Power Save
>>>>>> RX HT20 SGI
>>>>>> RX HT40 SGI
>>>>>> TX STBC
>>>>>> RX STBC 1-stream
>>>>>> Max AMSDU length: 7935 bytes
>>>>>> DSSS/CCK HT40
>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>> VHT Capabilities (0x338001b2):
>>>>>> Max MPDU length: 11454
>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>> RX LDPC
>>>>>> short GI (80 MHz)
>>>>>> TX STBC
>>>>>> RX antenna pattern consistency
>>>>>> TX antenna pattern consistency
>>>>>> VHT RX MCS set:
>>>>>> 1 streams: MCS 0-9
>>>>>> 2 streams: MCS 0-9
>>>>>> 3 streams: not supported
>>>>>> 4 streams: not supported
>>>>>> 5 streams: not supported
>>>>>> 6 streams: not supported
>>>>>> 7 streams: not supported
>>>>>> 8 streams: not supported
>>>>>> VHT RX highest supported: 0 Mbps
>>>>>> VHT TX MCS set:
>>>>>> 1 streams: MCS 0-9
>>>>>> 2 streams: MCS 0-9
>>>>>> 3 streams: not supported
>>>>>> 4 streams: not supported
>>>>>> 5 streams: not supported
>>>>>> 6 streams: not supported
>>>>>> 7 streams: not supported
>>>>>> 8 streams: not supported
>>>>>> VHT TX highest supported: 0 Mbps
>>>>>> Bitrates (non-HT):
>>>>>> * 6.0 Mbps
>>>>>> * 9.0 Mbps
>>>>>> * 12.0 Mbps
>>>>>> * 18.0 Mbps
>>>>>> * 24.0 Mbps
>>>>>> * 36.0 Mbps
>>>>>> * 48.0 Mbps
>>>>>> * 54.0 Mbps
>>>>>> Frequencies:
>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>> DFS state: usable (for 1076 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>> DFS state: usable (for 1076 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>> DFS state: usable (for 1076 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>> DFS state: usable (for 1076 sec)
>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>> Supported commands:
>>>>>> * new_interface
>>>>>> * set_interface
>>>>>> * new_key
>>>>>> * start_ap
>>>>>> * new_station
>>>>>> * set_bss
>>>>>> * authenticate
>>>>>> * associate
>>>>>> * deauthenticate
>>>>>> * disassociate
>>>>>> * join_ibss
>>>>>> * remain_on_channel
>>>>>> * set_tx_bitrate_mask
>>>>>> * frame
>>>>>> * frame_wait_cancel
>>>>>> * set_wiphy_netns
>>>>>> * set_channel
>>>>>> * set_wds_peer
>>>>>> * probe_client
>>>>>> * set_noack_map
>>>>>> * register_beacons
>>>>>> * start_p2p_device
>>>>>> * set_mcast_rate
>>>>>> * testmode
>>>>>> * channel_switch
>>>>>> * Unknown command (104)
>>>>>> * connect
>>>>>> * disconnect
>>>>>> Supported TX frame types:
>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> Supported RX frame types:
>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>> * managed: 0x40 0xd0
>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>> * P2P-client: 0x40 0xd0
>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>> * P2P-device: 0x40 0xd0
>>>>>> software interface modes (can always be added):
>>>>>> * AP/VLAN
>>>>>> * monitor
>>>>>> valid interface combinations:
>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>> HT Capability overrides:
>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>> * maximum A-MSDU length
>>>>>> * supported channel width
>>>>>> * short GI for 40 MHz
>>>>>> * max A-MPDU length exponent
>>>>>> * min MPDU start spacing
>>>>>> Device supports TX status socket option.
>>>>>> Device supports HT-IBSS.
>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>> Device supports scan flush.
>>>>>> Device supports per-vif TX power setting
>>>>>> Driver supports a userspace MPM
>>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>>>>>> Device supports static SMPS
>>>>>> =====================================================
>>>>>>
>>>>>> I am grateful for any help here and do have some time to help
>>>>>> debugging the issue.
>>>>>>
>>>>>> Marcel
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ------------------------------------------------------
>>>>>> This message is not intended to have
>>>>>> contractual effect
>>>>>> ------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>>
>>>> --
>>>> Jorge Baranda
>>>> Research Engineer, MSc
>>>> jorge.baranda@cttc.es
>>>>
>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>> Av. Carl Friedrich Gauss, 7
>>>> 08860 Castelldefels, Barcelona (Spain)
>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>> Fax. +34 93 645 29 01
>>>> www.cttc.es
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>>
>> --
>>
>> ------------------------------------------------------
>> This message is not intended to have
>> contractual effect
>> ------------------------------------------------------
>
>
--
Dipl.-Ing. Hannes Harms
Technische Universität Braunschweig
Institut für mobile Maschinen und Nutzfahrzeuge
Langer Kamp 19a
D-38106 Braunschweig
Durchwahl: +49 (0)531 391-7197
E-Mail: hannes.harms@tu-braunschweig.de
http://www.tu-braunschweig.de/imn
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-09 7:49 ` Marcel H.
2015-09-09 9:46 ` Marcel H.
@ 2015-09-09 11:06 ` Janusz Dziedzic
1 sibling, 0 replies; 22+ messages in thread
From: Janusz Dziedzic @ 2015-09-09 11:06 UTC (permalink / raw)
To: Marcel H.; +Cc: ath10k
On 9 September 2015 at 09:49, Marcel H. <maco@blava.net> wrote:
> Thanks for the response, unfortunately this is the result of defining
> the center frequency:
>
> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
> command failed: Device or resource busy (-16)
>
> Also, using wpa_supplicant does not work using the following config:
>
> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
> ap_scan=2
> ctrl_interface=/run/wpa_supplicant
> update_config=1
> device_type=0-00000000-0
>
> network={
> scan_ssid=1
> key_mgmt=NONE
> priority=1
> ssid="ibss"
> mode=1
> frequency=5180
> }
>
> running as:
> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D nl80211,wext
>
>
>
> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
> Interface wlan0
> ifindex 5
> wdev 0x100000001
> addr 04:f0:21:1b:5f:3d
> ssid ibss-rsn
> type IBSS
> wiphy 1
> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>
> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
> Wiphy phy1
> DFS state: usable (for 46424 sec)
> DFS CAC time: 60000 ms
> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 46424 sec)
> DFS CAC time: 60000 ms
> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 46424 sec)
> DFS CAC time: 60000 ms
> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
> DFS state: usable (for 46424 sec)
> Its fallbacking to 20MHz channels, which is even less than 40MHz
> channels set manually by iw
>
Why you didn't paste 5180?
Send dmesg and wpa_supplicant logs.
>
> How recent wpa_supplicat shall I try? I believe this it quite recent:
>
> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
> wpa_supplicant v2.3
> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>
>
> Re. the regulatory settings:
>
> root@voyage1:/opt/ca_node/etc# iw reg get
> country US: DFS-FCC
> (2402 - 2472 @ 40), (N/A, 30), (N/A)
> (5170 - 5250 @ 80), (N/A, 17), (N/A)
> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
> (5735 - 5835 @ 80), (N/A, 30), (N/A)
> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>
>
> Any other thoughts?
>
> Marcel
>
> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
> <janusz.dziedzic@tieto.com> wrote:
>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>> Hi everyone,
>>>
>>> Reading this thread, I would like to share with people some doubts about it.
>>> @Marco, I imagine you want to run your WLE600VX device using the 802.11ac
>>> protocol, isn't it?
>>> @Janusz, with running wpa_supplicant on both computers, will the ad-hoc
>>> connection be established? I am starting with these tools and now, I am
>>> getting used to know how they work. I was creating the ad-hoc connection
>>> with the iw tool.
>>>
>> Yes you should use wpa_supplicant on both PC.
>> In the future probably someone will add IBSS-VHT support also for iw.
>>
>> BR
>> Janusz
>>
>>> Thanks,
>>>
>>>
>>>
>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>
>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>
>>>>> Hi everyone,
>>>>> I have an interesting issue - I'm trying to run the QCA9882 based card
>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>>>>> 80MHz width resolves in the following:
>>>>>
>>>> You should run IBSS using fresh wpa_supplicant (best latest code). By
>>>> default should run in 80MHz.
>>>> Other case is your regulatory - are you allow to use 80MHz on channel
>>>> 157? First try 5180.
>>>>
>>>> eg. of wpa_supplicant config:
>>>>
>>>> network = {
>>>> ssid="test_ibss"
>>>> key_mgmt=NONE
>>>> mode=1
>>>> frequency=5180
>>>> }
>>>>
>>>> BR
>>>> Janusz
>>>>
>>>>> Interface wlan0
>>>>> ifindex 5
>>>>> wdev 0x1
>>>>> addr 04:f0:21:1b:5f:3b
>>>>> ssid my-mesh-network
>>>>> type IBSS
>>>>> wiphy 0
>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>> command failed: Invalid argument (-22)
>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>> command failed: Invalid argument (-22)
>>>>>
>>>>>
>>>>> More info:
>>>>> =====================================================
>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
>>>>> Network Adapter
>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>> Capabilities: [40] Power Management version 2
>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>> Capabilities: [100] Advanced Error Reporting
>>>>> Capabilities: [140] Virtual Channel
>>>>> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>>>>> Kernel driver in use: ath10k_pci
>>>>>
>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>> country US: DFS-FCC
>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>
>>>>>
>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>>>>> GMT 2015 i686 GNU/Linux
>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10
>>>>> .config)
>>>>>
>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>> (this is from the 'main' directory in the
>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>
>>>>>
>>>>> Wiphy phy0
>>>>> max # scan SSIDs: 16
>>>>> max scan IEs length: 195 bytes
>>>>> Retry short limit: 7
>>>>> Retry long limit: 4
>>>>> Coverage class: 0 (up to 0m)
>>>>> Device supports RSN-IBSS.
>>>>> Device supports AP-side u-APSD.
>>>>> Supported Ciphers:
>>>>> * WEP40 (00-0f-ac:1)
>>>>> * WEP104 (00-0f-ac:5)
>>>>> * TKIP (00-0f-ac:2)
>>>>> * CCMP (00-0f-ac:4)
>>>>> * CMAC (00-0f-ac:6)
>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>> Supported interface modes:
>>>>> * IBSS
>>>>> * managed
>>>>> * AP
>>>>> * AP/VLAN
>>>>> * monitor
>>>>> * P2P-client
>>>>> * P2P-GO
>>>>> * P2P-device
>>>>> Band 1:
>>>>> Capabilities: 0x19e3
>>>>> RX LDPC
>>>>> HT20/HT40
>>>>> Static SM Power Save
>>>>> RX HT20 SGI
>>>>> RX HT40 SGI
>>>>> TX STBC
>>>>> RX STBC 1-stream
>>>>> Max AMSDU length: 7935 bytes
>>>>> DSSS/CCK HT40
>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>> VHT Capabilities (0x338001b2):
>>>>> Max MPDU length: 11454
>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>> RX LDPC
>>>>> short GI (80 MHz)
>>>>> TX STBC
>>>>> RX antenna pattern consistency
>>>>> TX antenna pattern consistency
>>>>> VHT RX MCS set:
>>>>> 1 streams: MCS 0-9
>>>>> 2 streams: MCS 0-9
>>>>> 3 streams: not supported
>>>>> 4 streams: not supported
>>>>> 5 streams: not supported
>>>>> 6 streams: not supported
>>>>> 7 streams: not supported
>>>>> 8 streams: not supported
>>>>> VHT RX highest supported: 0 Mbps
>>>>> VHT TX MCS set:
>>>>> 1 streams: MCS 0-9
>>>>> 2 streams: MCS 0-9
>>>>> 3 streams: not supported
>>>>> 4 streams: not supported
>>>>> 5 streams: not supported
>>>>> 6 streams: not supported
>>>>> 7 streams: not supported
>>>>> 8 streams: not supported
>>>>> VHT TX highest supported: 0 Mbps
>>>>> Bitrates (non-HT):
>>>>> * 1.0 Mbps
>>>>> * 2.0 Mbps (short preamble supported)
>>>>> * 5.5 Mbps (short preamble supported)
>>>>> * 11.0 Mbps (short preamble supported)
>>>>> * 6.0 Mbps
>>>>> * 9.0 Mbps
>>>>> * 12.0 Mbps
>>>>> * 18.0 Mbps
>>>>> * 24.0 Mbps
>>>>> * 36.0 Mbps
>>>>> * 48.0 Mbps
>>>>> * 54.0 Mbps
>>>>> Frequencies:
>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>> * 2467 MHz [12] (disabled)
>>>>> * 2472 MHz [13] (disabled)
>>>>> * 2484 MHz [14] (disabled)
>>>>> Band 2:
>>>>> Capabilities: 0x19e3
>>>>> RX LDPC
>>>>> HT20/HT40
>>>>> Static SM Power Save
>>>>> RX HT20 SGI
>>>>> RX HT40 SGI
>>>>> TX STBC
>>>>> RX STBC 1-stream
>>>>> Max AMSDU length: 7935 bytes
>>>>> DSSS/CCK HT40
>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>> VHT Capabilities (0x338001b2):
>>>>> Max MPDU length: 11454
>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>> RX LDPC
>>>>> short GI (80 MHz)
>>>>> TX STBC
>>>>> RX antenna pattern consistency
>>>>> TX antenna pattern consistency
>>>>> VHT RX MCS set:
>>>>> 1 streams: MCS 0-9
>>>>> 2 streams: MCS 0-9
>>>>> 3 streams: not supported
>>>>> 4 streams: not supported
>>>>> 5 streams: not supported
>>>>> 6 streams: not supported
>>>>> 7 streams: not supported
>>>>> 8 streams: not supported
>>>>> VHT RX highest supported: 0 Mbps
>>>>> VHT TX MCS set:
>>>>> 1 streams: MCS 0-9
>>>>> 2 streams: MCS 0-9
>>>>> 3 streams: not supported
>>>>> 4 streams: not supported
>>>>> 5 streams: not supported
>>>>> 6 streams: not supported
>>>>> 7 streams: not supported
>>>>> 8 streams: not supported
>>>>> VHT TX highest supported: 0 Mbps
>>>>> Bitrates (non-HT):
>>>>> * 6.0 Mbps
>>>>> * 9.0 Mbps
>>>>> * 12.0 Mbps
>>>>> * 18.0 Mbps
>>>>> * 24.0 Mbps
>>>>> * 36.0 Mbps
>>>>> * 48.0 Mbps
>>>>> * 54.0 Mbps
>>>>> Frequencies:
>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>> DFS state: usable (for 1076 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>> DFS state: usable (for 1076 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>> DFS state: usable (for 1076 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>> DFS state: usable (for 1076 sec)
>>>>> DFS CAC time: 60000 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] (disabled)
>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>> Supported commands:
>>>>> * new_interface
>>>>> * set_interface
>>>>> * new_key
>>>>> * start_ap
>>>>> * new_station
>>>>> * set_bss
>>>>> * authenticate
>>>>> * associate
>>>>> * deauthenticate
>>>>> * disassociate
>>>>> * join_ibss
>>>>> * remain_on_channel
>>>>> * set_tx_bitrate_mask
>>>>> * frame
>>>>> * frame_wait_cancel
>>>>> * set_wiphy_netns
>>>>> * set_channel
>>>>> * set_wds_peer
>>>>> * probe_client
>>>>> * set_noack_map
>>>>> * register_beacons
>>>>> * start_p2p_device
>>>>> * set_mcast_rate
>>>>> * testmode
>>>>> * channel_switch
>>>>> * Unknown command (104)
>>>>> * connect
>>>>> * disconnect
>>>>> Supported TX frame types:
>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>> Supported RX frame types:
>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>> * managed: 0x40 0xd0
>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>> * P2P-client: 0x40 0xd0
>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>> * P2P-device: 0x40 0xd0
>>>>> software interface modes (can always be added):
>>>>> * AP/VLAN
>>>>> * monitor
>>>>> valid interface combinations:
>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>> HT Capability overrides:
>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>> * maximum A-MSDU length
>>>>> * supported channel width
>>>>> * short GI for 40 MHz
>>>>> * max A-MPDU length exponent
>>>>> * min MPDU start spacing
>>>>> Device supports TX status socket option.
>>>>> Device supports HT-IBSS.
>>>>> Device supports SAE with AUTHENTICATE command
>>>>> Device supports scan flush.
>>>>> Device supports per-vif TX power setting
>>>>> Driver supports a userspace MPM
>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>>>>> Device supports static SMPS
>>>>> =====================================================
>>>>>
>>>>> I am grateful for any help here and do have some time to help
>>>>> debugging the issue.
>>>>>
>>>>> Marcel
>>>>>
>>>>> --
>>>>>
>>>>> ------------------------------------------------------
>>>>> This message is not intended to have
>>>>> contractual effect
>>>>> ------------------------------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>>
>>>
>>> --
>>> Jorge Baranda
>>> Research Engineer, MSc
>>> jorge.baranda@cttc.es
>>>
>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>> Av. Carl Friedrich Gauss, 7
>>> 08860 Castelldefels, Barcelona (Spain)
>>> Tel: +34 93 645 29 00 Ext: 2171
>>> Fax. +34 93 645 29 01
>>> www.cttc.es
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>
>
>
> --
>
> ------------------------------------------------------
> This message is not intended to have
> contractual effect
> ------------------------------------------------------
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-09 10:59 ` Harms, Hannes
@ 2015-09-09 11:08 ` Janusz Dziedzic
2015-09-09 11:08 ` [SPAM] " Jorge Baranda
1 sibling, 0 replies; 22+ messages in thread
From: Janusz Dziedzic @ 2015-09-09 11:08 UTC (permalink / raw)
To: Harms, Hannes; +Cc: ath10k
On 9 September 2015 at 12:59, Harms, Hannes <hannes.harms@tu-bs.de> wrote:
> Hi,
>
> I have WLE900VX working in IBSS mode and 80 Mhz with Candela Kernel 4.2.
> For me also the latest wpa_supplicant was not able to activate 80MHz by
> default , I don't no why.
>
Missing patch [PATCH v2] ath10k: enable VHT for IBSS
BR
Janusz
> The only way I found to get it working was to modify
> wpa_supplicant/wpa_supplicant.c
> Commit following two lines in wpa_supplicant.c like this :
>
> //if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
> // return;
>
:-)
BR
Janusz
> That was all for me to get it working.
>
> wpa_supplicant config file:
> # Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is ignored)
> CONFIG_LIBNL32=y
>
> # Support VHT overrides (disable VHT, mask MCS rates, etc.)
> CONFIG_VHT_OVERRIDES=y
>
> # Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
> CONFIG_HT_OVERRIDES=y
>
> # IEEE 802.11n (High Throughput) support (mainly for AP mode)
> CONFIG_IEEE80211N=y
>
> # IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
> # (depends on CONFIG_IEEE80211N)
> CONFIG_IEEE80211AC=y
>
> # IEEE 802.11w (management frame protection), also known as PMF
> # Driver support is also needed for IEEE 802.11w.
> CONFIG_IEEE80211W=y
>
>
> Am 09.09.2015 um 11:46 schrieb Marcel H.:
>>
>> May I ask someone for support on this one?
>> We would really like to make this work and I'm running out of ideas -
>> is there any way do turn detailed debugging on to get a better
>> understanding why do I get the following message back? ->
>>
>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>> command failed: Device or resource busy (-16)
>>
>> Thanks,
>> Marcel
>>
>> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>>>
>>> Thanks for the response, unfortunately this is the result of defining
>>> the center frequency:
>>>
>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>> command failed: Device or resource busy (-16)
>>>
>>> Also, using wpa_supplicant does not work using the following config:
>>>
>>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>>> ap_scan=2
>>> ctrl_interface=/run/wpa_supplicant
>>> update_config=1
>>> device_type=0-00000000-0
>>>
>>> network={
>>> scan_ssid=1
>>> key_mgmt=NONE
>>> priority=1
>>> ssid="ibss"
>>> mode=1
>>> frequency=5180
>>> }
>>>
>>> running as:
>>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D nl80211,wext
>>>
>>>
>>>
>>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>>> Interface wlan0
>>> ifindex 5
>>> wdev 0x100000001
>>> addr 04:f0:21:1b:5f:3d
>>> ssid ibss-rsn
>>> type IBSS
>>> wiphy 1
>>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>>
>>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>>> Wiphy phy1
>>> DFS state: usable (for 46424 sec)
>>> DFS CAC time: 60000 ms
>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>> detection)
>>> DFS state: usable (for 46424 sec)
>>> DFS CAC time: 60000 ms
>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>> detection)
>>> DFS state: usable (for 46424 sec)
>>> DFS CAC time: 60000 ms
>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>> detection)
>>> DFS state: usable (for 46424 sec)
>>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>>> channels set manually by iw
>>>
>>>
>>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>>
>>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>> wpa_supplicant v2.3
>>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>>
>>>
>>> Re. the regulatory settings:
>>>
>>> root@voyage1:/opt/ca_node/etc# iw reg get
>>> country US: DFS-FCC
>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>
>>>
>>> Any other thoughts?
>>>
>>> Marcel
>>>
>>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>>> <janusz.dziedzic@tieto.com> wrote:
>>>>
>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>>>>
>>>>> Hi everyone,
>>>>>
>>>>> Reading this thread, I would like to share with people some doubts
>>>>> about it.
>>>>> @Marco, I imagine you want to run your WLE600VX device using the
>>>>> 802.11ac
>>>>> protocol, isn't it?
>>>>> @Janusz, with running wpa_supplicant on both computers, will the ad-hoc
>>>>> connection be established? I am starting with these tools and now, I am
>>>>> getting used to know how they work. I was creating the ad-hoc
>>>>> connection
>>>>> with the iw tool.
>>>>>
>>>> Yes you should use wpa_supplicant on both PC.
>>>> In the future probably someone will add IBSS-VHT support also for iw.
>>>>
>>>> BR
>>>> Janusz
>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>>
>>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>>
>>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>>
>>>>>>> Hi everyone,
>>>>>>> I have an interesting issue - I'm trying to run the QCA9882 based
>>>>>>> card
>>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>>>>>>> 80MHz width resolves in the following:
>>>>>>>
>>>>>> You should run IBSS using fresh wpa_supplicant (best latest code). By
>>>>>> default should run in 80MHz.
>>>>>> Other case is your regulatory - are you allow to use 80MHz on channel
>>>>>> 157? First try 5180.
>>>>>>
>>>>>> eg. of wpa_supplicant config:
>>>>>>
>>>>>> network = {
>>>>>> ssid="test_ibss"
>>>>>> key_mgmt=NONE
>>>>>> mode=1
>>>>>> frequency=5180
>>>>>> }
>>>>>>
>>>>>> BR
>>>>>> Janusz
>>>>>>
>>>>>>> Interface wlan0
>>>>>>> ifindex 5
>>>>>>> wdev 0x1
>>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>>> ssid my-mesh-network
>>>>>>> type IBSS
>>>>>>> wiphy 0
>>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>> command failed: Invalid argument (-22)
>>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>> command failed: Invalid argument (-22)
>>>>>>>
>>>>>>>
>>>>>>> More info:
>>>>>>> =====================================================
>>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac
>>>>>>> Wireless
>>>>>>> Network Adapter
>>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>>> Capabilities: [40] Power Management version 2
>>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>>> Capabilities: [140] Virtual Channel
>>>>>>> Capabilities: [160] Device Serial Number
>>>>>>> 00-00-00-00-00-00-00-00
>>>>>>> Kernel driver in use: ath10k_pci
>>>>>>>
>>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>>> country US: DFS-FCC
>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>
>>>>>>>
>>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>>>>>>> GMT 2015 i686 GNU/Linux
>>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux
>>>>>>> 0.10
>>>>>>> .config)
>>>>>>>
>>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum
>>>>>>> ./firmware-2.bin
>>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>>> (this is from the 'main' directory in the
>>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>>
>>>>>>>
>>>>>>> Wiphy phy0
>>>>>>> max # scan SSIDs: 16
>>>>>>> max scan IEs length: 195 bytes
>>>>>>> Retry short limit: 7
>>>>>>> Retry long limit: 4
>>>>>>> Coverage class: 0 (up to 0m)
>>>>>>> Device supports RSN-IBSS.
>>>>>>> Device supports AP-side u-APSD.
>>>>>>> Supported Ciphers:
>>>>>>> * WEP40 (00-0f-ac:1)
>>>>>>> * WEP104 (00-0f-ac:5)
>>>>>>> * TKIP (00-0f-ac:2)
>>>>>>> * CCMP (00-0f-ac:4)
>>>>>>> * CMAC (00-0f-ac:6)
>>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>>> Supported interface modes:
>>>>>>> * IBSS
>>>>>>> * managed
>>>>>>> * AP
>>>>>>> * AP/VLAN
>>>>>>> * monitor
>>>>>>> * P2P-client
>>>>>>> * P2P-GO
>>>>>>> * P2P-device
>>>>>>> Band 1:
>>>>>>> Capabilities: 0x19e3
>>>>>>> RX LDPC
>>>>>>> HT20/HT40
>>>>>>> Static SM Power Save
>>>>>>> RX HT20 SGI
>>>>>>> RX HT40 SGI
>>>>>>> TX STBC
>>>>>>> RX STBC 1-stream
>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>> DSSS/CCK HT40
>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>> Max MPDU length: 11454
>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>> RX LDPC
>>>>>>> short GI (80 MHz)
>>>>>>> TX STBC
>>>>>>> RX antenna pattern consistency
>>>>>>> TX antenna pattern consistency
>>>>>>> VHT RX MCS set:
>>>>>>> 1 streams: MCS 0-9
>>>>>>> 2 streams: MCS 0-9
>>>>>>> 3 streams: not supported
>>>>>>> 4 streams: not supported
>>>>>>> 5 streams: not supported
>>>>>>> 6 streams: not supported
>>>>>>> 7 streams: not supported
>>>>>>> 8 streams: not supported
>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>> VHT TX MCS set:
>>>>>>> 1 streams: MCS 0-9
>>>>>>> 2 streams: MCS 0-9
>>>>>>> 3 streams: not supported
>>>>>>> 4 streams: not supported
>>>>>>> 5 streams: not supported
>>>>>>> 6 streams: not supported
>>>>>>> 7 streams: not supported
>>>>>>> 8 streams: not supported
>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>> Bitrates (non-HT):
>>>>>>> * 1.0 Mbps
>>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>>> * 6.0 Mbps
>>>>>>> * 9.0 Mbps
>>>>>>> * 12.0 Mbps
>>>>>>> * 18.0 Mbps
>>>>>>> * 24.0 Mbps
>>>>>>> * 36.0 Mbps
>>>>>>> * 48.0 Mbps
>>>>>>> * 54.0 Mbps
>>>>>>> Frequencies:
>>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>>> * 2467 MHz [12] (disabled)
>>>>>>> * 2472 MHz [13] (disabled)
>>>>>>> * 2484 MHz [14] (disabled)
>>>>>>> Band 2:
>>>>>>> Capabilities: 0x19e3
>>>>>>> RX LDPC
>>>>>>> HT20/HT40
>>>>>>> Static SM Power Save
>>>>>>> RX HT20 SGI
>>>>>>> RX HT40 SGI
>>>>>>> TX STBC
>>>>>>> RX STBC 1-stream
>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>> DSSS/CCK HT40
>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>> Max MPDU length: 11454
>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>> RX LDPC
>>>>>>> short GI (80 MHz)
>>>>>>> TX STBC
>>>>>>> RX antenna pattern consistency
>>>>>>> TX antenna pattern consistency
>>>>>>> VHT RX MCS set:
>>>>>>> 1 streams: MCS 0-9
>>>>>>> 2 streams: MCS 0-9
>>>>>>> 3 streams: not supported
>>>>>>> 4 streams: not supported
>>>>>>> 5 streams: not supported
>>>>>>> 6 streams: not supported
>>>>>>> 7 streams: not supported
>>>>>>> 8 streams: not supported
>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>> VHT TX MCS set:
>>>>>>> 1 streams: MCS 0-9
>>>>>>> 2 streams: MCS 0-9
>>>>>>> 3 streams: not supported
>>>>>>> 4 streams: not supported
>>>>>>> 5 streams: not supported
>>>>>>> 6 streams: not supported
>>>>>>> 7 streams: not supported
>>>>>>> 8 streams: not supported
>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>> Bitrates (non-HT):
>>>>>>> * 6.0 Mbps
>>>>>>> * 9.0 Mbps
>>>>>>> * 12.0 Mbps
>>>>>>> * 18.0 Mbps
>>>>>>> * 24.0 Mbps
>>>>>>> * 36.0 Mbps
>>>>>>> * 48.0 Mbps
>>>>>>> * 54.0 Mbps
>>>>>>> Frequencies:
>>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>>> Supported commands:
>>>>>>> * new_interface
>>>>>>> * set_interface
>>>>>>> * new_key
>>>>>>> * start_ap
>>>>>>> * new_station
>>>>>>> * set_bss
>>>>>>> * authenticate
>>>>>>> * associate
>>>>>>> * deauthenticate
>>>>>>> * disassociate
>>>>>>> * join_ibss
>>>>>>> * remain_on_channel
>>>>>>> * set_tx_bitrate_mask
>>>>>>> * frame
>>>>>>> * frame_wait_cancel
>>>>>>> * set_wiphy_netns
>>>>>>> * set_channel
>>>>>>> * set_wds_peer
>>>>>>> * probe_client
>>>>>>> * set_noack_map
>>>>>>> * register_beacons
>>>>>>> * start_p2p_device
>>>>>>> * set_mcast_rate
>>>>>>> * testmode
>>>>>>> * channel_switch
>>>>>>> * Unknown command (104)
>>>>>>> * connect
>>>>>>> * disconnect
>>>>>>> Supported TX frame types:
>>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>> 0x90
>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>>> 0xa0
>>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>> 0x90
>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>> 0x90
>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> Supported RX frame types:
>>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>>> * managed: 0x40 0xd0
>>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>>> * P2P-client: 0x40 0xd0
>>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>> * P2P-device: 0x40 0xd0
>>>>>>> software interface modes (can always be added):
>>>>>>> * AP/VLAN
>>>>>>> * monitor
>>>>>>> valid interface combinations:
>>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>>> HT Capability overrides:
>>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>>> * maximum A-MSDU length
>>>>>>> * supported channel width
>>>>>>> * short GI for 40 MHz
>>>>>>> * max A-MPDU length exponent
>>>>>>> * min MPDU start spacing
>>>>>>> Device supports TX status socket option.
>>>>>>> Device supports HT-IBSS.
>>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>>> Device supports scan flush.
>>>>>>> Device supports per-vif TX power setting
>>>>>>> Driver supports a userspace MPM
>>>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO
>>>>>>> mode)
>>>>>>> Device supports static SMPS
>>>>>>> =====================================================
>>>>>>>
>>>>>>> I am grateful for any help here and do have some time to help
>>>>>>> debugging the issue.
>>>>>>>
>>>>>>> Marcel
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> ------------------------------------------------------
>>>>>>> This message is not intended to have
>>>>>>> contractual effect
>>>>>>> ------------------------------------------------------
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jorge Baranda
>>>>> Research Engineer, MSc
>>>>> jorge.baranda@cttc.es
>>>>>
>>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>>> Av. Carl Friedrich Gauss, 7
>>>>> 08860 Castelldefels, Barcelona (Spain)
>>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>>> Fax. +34 93 645 29 01
>>>>> www.cttc.es
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>>
>>>
>>> --
>>>
>>> ------------------------------------------------------
>>> This message is not intended to have
>>> contractual effect
>>> ------------------------------------------------------
>>
>>
>>
>
> --
> Dipl.-Ing. Hannes Harms
> Technische Universität Braunschweig
> Institut für mobile Maschinen und Nutzfahrzeuge
> Langer Kamp 19a
> D-38106 Braunschweig
>
> Durchwahl: +49 (0)531 391-7197
> E-Mail: hannes.harms@tu-braunschweig.de
> http://www.tu-braunschweig.de/imn
>
>
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [SPAM] Re: WLE600VX from PCEngines
2015-09-09 10:59 ` Harms, Hannes
2015-09-09 11:08 ` Janusz Dziedzic
@ 2015-09-09 11:08 ` Jorge Baranda
2015-09-09 11:14 ` Ben Greear
2015-09-09 11:15 ` Harms, Hannes
1 sibling, 2 replies; 22+ messages in thread
From: Jorge Baranda @ 2015-09-09 11:08 UTC (permalink / raw)
To: ath10k
Hi,
Good news!! Harms, could you share full wpa_supplicant configuration files?
(for both computers).
I will download the latest version of wpa_supplicant, apply your changes
and try
to make work IBSS mode and 80MHz with Candela Kernel 4.0.
Thanks,
El 09/09/15 12:59, Harms, Hannes escribió:
> Hi,
>
> I have WLE900VX working in IBSS mode and 80 Mhz with Candela Kernel 4.2.
> For me also the latest wpa_supplicant was not able to activate 80MHz
> by default , I don't no why.
>
> The only way I found to get it working was to modify
> wpa_supplicant/wpa_supplicant.c
> Commit following two lines in wpa_supplicant.c like this :
>
> //if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
> // return;
>
> That was all for me to get it working.
>
> wpa_supplicant config file:
> # Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is
> ignored)
> CONFIG_LIBNL32=y
>
> # Support VHT overrides (disable VHT, mask MCS rates, etc.)
> CONFIG_VHT_OVERRIDES=y
>
> # Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
> CONFIG_HT_OVERRIDES=y
>
> # IEEE 802.11n (High Throughput) support (mainly for AP mode)
> CONFIG_IEEE80211N=y
>
> # IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
> # (depends on CONFIG_IEEE80211N)
> CONFIG_IEEE80211AC=y
>
> # IEEE 802.11w (management frame protection), also known as PMF
> # Driver support is also needed for IEEE 802.11w.
> CONFIG_IEEE80211W=y
>
> Am 09.09.2015 um 11:46 schrieb Marcel H.:
>> May I ask someone for support on this one?
>> We would really like to make this work and I'm running out of ideas -
>> is there any way do turn detailed debugging on to get a better
>> understanding why do I get the following message back? ->
>>
>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>> command failed: Device or resource busy (-16)
>>
>> Thanks,
>> Marcel
>>
>> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>>> Thanks for the response, unfortunately this is the result of defining
>>> the center frequency:
>>>
>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>> command failed: Device or resource busy (-16)
>>>
>>> Also, using wpa_supplicant does not work using the following config:
>>>
>>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>>> ap_scan=2
>>> ctrl_interface=/run/wpa_supplicant
>>> update_config=1
>>> device_type=0-00000000-0
>>>
>>> network={
>>> scan_ssid=1
>>> key_mgmt=NONE
>>> priority=1
>>> ssid="ibss"
>>> mode=1
>>> frequency=5180
>>> }
>>>
>>> running as:
>>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D
>>> nl80211,wext
>>>
>>>
>>>
>>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>>> Interface wlan0
>>> ifindex 5
>>> wdev 0x100000001
>>> addr 04:f0:21:1b:5f:3d
>>> ssid ibss-rsn
>>> type IBSS
>>> wiphy 1
>>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>>
>>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>>> Wiphy phy1
>>> DFS state: usable (for 46424 sec)
>>> DFS CAC time: 60000 ms
>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>> detection)
>>> DFS state: usable (for 46424 sec)
>>> DFS CAC time: 60000 ms
>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>> detection)
>>> DFS state: usable (for 46424 sec)
>>> DFS CAC time: 60000 ms
>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>> detection)
>>> DFS state: usable (for 46424 sec)
>>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>>> channels set manually by iw
>>>
>>>
>>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>>
>>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>> wpa_supplicant v2.3
>>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>>
>>>
>>> Re. the regulatory settings:
>>>
>>> root@voyage1:/opt/ca_node/etc# iw reg get
>>> country US: DFS-FCC
>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>
>>>
>>> Any other thoughts?
>>>
>>> Marcel
>>>
>>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>>> <janusz.dziedzic@tieto.com> wrote:
>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>>>> Hi everyone,
>>>>>
>>>>> Reading this thread, I would like to share with people some doubts
>>>>> about it.
>>>>> @Marco, I imagine you want to run your WLE600VX device using the
>>>>> 802.11ac
>>>>> protocol, isn't it?
>>>>> @Janusz, with running wpa_supplicant on both computers, will the
>>>>> ad-hoc
>>>>> connection be established? I am starting with these tools and now,
>>>>> I am
>>>>> getting used to know how they work. I was creating the ad-hoc
>>>>> connection
>>>>> with the iw tool.
>>>>>
>>>> Yes you should use wpa_supplicant on both PC.
>>>> In the future probably someone will add IBSS-VHT support also for iw.
>>>>
>>>> BR
>>>> Janusz
>>>>
>>>>> Thanks,
>>>>>
>>>>>
>>>>>
>>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>>
>>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>> Hi everyone,
>>>>>>> I have an interesting issue - I'm trying to run the QCA9882
>>>>>>> based card
>>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to
>>>>>>> run
>>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run
>>>>>>> it in
>>>>>>> 80MHz width resolves in the following:
>>>>>>>
>>>>>> You should run IBSS using fresh wpa_supplicant (best latest
>>>>>> code). By
>>>>>> default should run in 80MHz.
>>>>>> Other case is your regulatory - are you allow to use 80MHz on
>>>>>> channel
>>>>>> 157? First try 5180.
>>>>>>
>>>>>> eg. of wpa_supplicant config:
>>>>>>
>>>>>> network = {
>>>>>> ssid="test_ibss"
>>>>>> key_mgmt=NONE
>>>>>> mode=1
>>>>>> frequency=5180
>>>>>> }
>>>>>>
>>>>>> BR
>>>>>> Janusz
>>>>>>
>>>>>>> Interface wlan0
>>>>>>> ifindex 5
>>>>>>> wdev 0x1
>>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>>> ssid my-mesh-network
>>>>>>> type IBSS
>>>>>>> wiphy 0
>>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>> command failed: Invalid argument (-22)
>>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>> command failed: Invalid argument (-22)
>>>>>>>
>>>>>>>
>>>>>>> More info:
>>>>>>> =====================================================
>>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac
>>>>>>> Wireless
>>>>>>> Network Adapter
>>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>>> Capabilities: [40] Power Management version 2
>>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>>> Capabilities: [140] Virtual Channel
>>>>>>> Capabilities: [160] Device Serial Number
>>>>>>> 00-00-00-00-00-00-00-00
>>>>>>> Kernel driver in use: ath10k_pci
>>>>>>>
>>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>>> country US: DFS-FCC
>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>
>>>>>>>
>>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8
>>>>>>> 14:03:33
>>>>>>> GMT 2015 i686 GNU/Linux
>>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage
>>>>>>> Linux 0.10
>>>>>>> .config)
>>>>>>>
>>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum
>>>>>>> ./firmware-2.bin
>>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>>> (this is from the 'main' directory in the
>>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>>
>>>>>>>
>>>>>>> Wiphy phy0
>>>>>>> max # scan SSIDs: 16
>>>>>>> max scan IEs length: 195 bytes
>>>>>>> Retry short limit: 7
>>>>>>> Retry long limit: 4
>>>>>>> Coverage class: 0 (up to 0m)
>>>>>>> Device supports RSN-IBSS.
>>>>>>> Device supports AP-side u-APSD.
>>>>>>> Supported Ciphers:
>>>>>>> * WEP40 (00-0f-ac:1)
>>>>>>> * WEP104 (00-0f-ac:5)
>>>>>>> * TKIP (00-0f-ac:2)
>>>>>>> * CCMP (00-0f-ac:4)
>>>>>>> * CMAC (00-0f-ac:6)
>>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>>> Supported interface modes:
>>>>>>> * IBSS
>>>>>>> * managed
>>>>>>> * AP
>>>>>>> * AP/VLAN
>>>>>>> * monitor
>>>>>>> * P2P-client
>>>>>>> * P2P-GO
>>>>>>> * P2P-device
>>>>>>> Band 1:
>>>>>>> Capabilities: 0x19e3
>>>>>>> RX LDPC
>>>>>>> HT20/HT40
>>>>>>> Static SM Power Save
>>>>>>> RX HT20 SGI
>>>>>>> RX HT40 SGI
>>>>>>> TX STBC
>>>>>>> RX STBC 1-stream
>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>> DSSS/CCK HT40
>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>> Max MPDU length: 11454
>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>> RX LDPC
>>>>>>> short GI (80 MHz)
>>>>>>> TX STBC
>>>>>>> RX antenna pattern consistency
>>>>>>> TX antenna pattern consistency
>>>>>>> VHT RX MCS set:
>>>>>>> 1 streams: MCS 0-9
>>>>>>> 2 streams: MCS 0-9
>>>>>>> 3 streams: not supported
>>>>>>> 4 streams: not supported
>>>>>>> 5 streams: not supported
>>>>>>> 6 streams: not supported
>>>>>>> 7 streams: not supported
>>>>>>> 8 streams: not supported
>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>> VHT TX MCS set:
>>>>>>> 1 streams: MCS 0-9
>>>>>>> 2 streams: MCS 0-9
>>>>>>> 3 streams: not supported
>>>>>>> 4 streams: not supported
>>>>>>> 5 streams: not supported
>>>>>>> 6 streams: not supported
>>>>>>> 7 streams: not supported
>>>>>>> 8 streams: not supported
>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>> Bitrates (non-HT):
>>>>>>> * 1.0 Mbps
>>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>>> * 6.0 Mbps
>>>>>>> * 9.0 Mbps
>>>>>>> * 12.0 Mbps
>>>>>>> * 18.0 Mbps
>>>>>>> * 24.0 Mbps
>>>>>>> * 36.0 Mbps
>>>>>>> * 48.0 Mbps
>>>>>>> * 54.0 Mbps
>>>>>>> Frequencies:
>>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>>> * 2467 MHz [12] (disabled)
>>>>>>> * 2472 MHz [13] (disabled)
>>>>>>> * 2484 MHz [14] (disabled)
>>>>>>> Band 2:
>>>>>>> Capabilities: 0x19e3
>>>>>>> RX LDPC
>>>>>>> HT20/HT40
>>>>>>> Static SM Power Save
>>>>>>> RX HT20 SGI
>>>>>>> RX HT40 SGI
>>>>>>> TX STBC
>>>>>>> RX STBC 1-stream
>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>> DSSS/CCK HT40
>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>> Max MPDU length: 11454
>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>> RX LDPC
>>>>>>> short GI (80 MHz)
>>>>>>> TX STBC
>>>>>>> RX antenna pattern consistency
>>>>>>> TX antenna pattern consistency
>>>>>>> VHT RX MCS set:
>>>>>>> 1 streams: MCS 0-9
>>>>>>> 2 streams: MCS 0-9
>>>>>>> 3 streams: not supported
>>>>>>> 4 streams: not supported
>>>>>>> 5 streams: not supported
>>>>>>> 6 streams: not supported
>>>>>>> 7 streams: not supported
>>>>>>> 8 streams: not supported
>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>> VHT TX MCS set:
>>>>>>> 1 streams: MCS 0-9
>>>>>>> 2 streams: MCS 0-9
>>>>>>> 3 streams: not supported
>>>>>>> 4 streams: not supported
>>>>>>> 5 streams: not supported
>>>>>>> 6 streams: not supported
>>>>>>> 7 streams: not supported
>>>>>>> 8 streams: not supported
>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>> Bitrates (non-HT):
>>>>>>> * 6.0 Mbps
>>>>>>> * 9.0 Mbps
>>>>>>> * 12.0 Mbps
>>>>>>> * 18.0 Mbps
>>>>>>> * 24.0 Mbps
>>>>>>> * 36.0 Mbps
>>>>>>> * 48.0 Mbps
>>>>>>> * 54.0 Mbps
>>>>>>> Frequencies:
>>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>>> Supported commands:
>>>>>>> * new_interface
>>>>>>> * set_interface
>>>>>>> * new_key
>>>>>>> * start_ap
>>>>>>> * new_station
>>>>>>> * set_bss
>>>>>>> * authenticate
>>>>>>> * associate
>>>>>>> * deauthenticate
>>>>>>> * disassociate
>>>>>>> * join_ibss
>>>>>>> * remain_on_channel
>>>>>>> * set_tx_bitrate_mask
>>>>>>> * frame
>>>>>>> * frame_wait_cancel
>>>>>>> * set_wiphy_netns
>>>>>>> * set_channel
>>>>>>> * set_wds_peer
>>>>>>> * probe_client
>>>>>>> * set_noack_map
>>>>>>> * register_beacons
>>>>>>> * start_p2p_device
>>>>>>> * set_mcast_rate
>>>>>>> * testmode
>>>>>>> * channel_switch
>>>>>>> * Unknown command (104)
>>>>>>> * connect
>>>>>>> * disconnect
>>>>>>> Supported TX frame types:
>>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>> 0x90
>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>> 0x80 0x90
>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>> 0x90 0xa0
>>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>> 0x80 0x90
>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>> 0x80
>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>> 0x80
>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>> 0x80 0x90
>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>> 0x80
>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>> Supported RX frame types:
>>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>>> * managed: 0x40 0xd0
>>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>>> * P2P-client: 0x40 0xd0
>>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>> * P2P-device: 0x40 0xd0
>>>>>>> software interface modes (can always be added):
>>>>>>> * AP/VLAN
>>>>>>> * monitor
>>>>>>> valid interface combinations:
>>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>>> HT Capability overrides:
>>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>>> * maximum A-MSDU length
>>>>>>> * supported channel width
>>>>>>> * short GI for 40 MHz
>>>>>>> * max A-MPDU length exponent
>>>>>>> * min MPDU start spacing
>>>>>>> Device supports TX status socket option.
>>>>>>> Device supports HT-IBSS.
>>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>>> Device supports scan flush.
>>>>>>> Device supports per-vif TX power setting
>>>>>>> Driver supports a userspace MPM
>>>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO
>>>>>>> mode)
>>>>>>> Device supports static SMPS
>>>>>>> =====================================================
>>>>>>>
>>>>>>> I am grateful for any help here and do have some time to help
>>>>>>> debugging the issue.
>>>>>>>
>>>>>>> Marcel
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> ------------------------------------------------------
>>>>>>> This message is not intended to have
>>>>>>> contractual effect
>>>>>>> ------------------------------------------------------
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>>
>>>>> --
>>>>> Jorge Baranda
>>>>> Research Engineer, MSc
>>>>> jorge.baranda@cttc.es
>>>>>
>>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>>> Av. Carl Friedrich Gauss, 7
>>>>> 08860 Castelldefels, Barcelona (Spain)
>>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>>> Fax. +34 93 645 29 01
>>>>> www.cttc.es
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>>
>>> --
>>>
>>> ------------------------------------------------------
>>> This message is not intended to have
>>> contractual effect
>>> ------------------------------------------------------
>>
>>
>
--
Jorge Baranda
Research Engineer, MSc
jorge.baranda@cttc.es
Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
Av. Carl Friedrich Gauss, 7
08860 Castelldefels, Barcelona (Spain)
Tel: +34 93 645 29 00 Ext: 2171
Fax. +34 93 645 29 01
www.cttc.es
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-09 9:46 ` Marcel H.
2015-09-09 10:59 ` Harms, Hannes
@ 2015-09-09 11:09 ` Janusz Dziedzic
1 sibling, 0 replies; 22+ messages in thread
From: Janusz Dziedzic @ 2015-09-09 11:09 UTC (permalink / raw)
To: Marcel H.; +Cc: ath10k
On 9 September 2015 at 11:46, Marcel H. <maco@blava.net> wrote:
> May I ask someone for support on this one?
> We would really like to make this work and I'm running out of ideas -
> is there any way do turn detailed debugging on to get a better
> understanding why do I get the following message back? ->
>
> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
> command failed: Device or resource busy (-16)
>
You shouldn't use iw while wpa_supplicant can setup this correctly.
This command is not needed.
BR
Janusz
> Thanks,
> Marcel
>
> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>> Thanks for the response, unfortunately this is the result of defining
>> the center frequency:
>>
>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>> command failed: Device or resource busy (-16)
>>
>> Also, using wpa_supplicant does not work using the following config:
>>
>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>> ap_scan=2
>> ctrl_interface=/run/wpa_supplicant
>> update_config=1
>> device_type=0-00000000-0
>>
>> network={
>> scan_ssid=1
>> key_mgmt=NONE
>> priority=1
>> ssid="ibss"
>> mode=1
>> frequency=5180
>> }
>>
>> running as:
>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D nl80211,wext
>>
>>
>>
>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>> Interface wlan0
>> ifindex 5
>> wdev 0x100000001
>> addr 04:f0:21:1b:5f:3d
>> ssid ibss-rsn
>> type IBSS
>> wiphy 1
>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>
>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>> Wiphy phy1
>> DFS state: usable (for 46424 sec)
>> DFS CAC time: 60000 ms
>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 46424 sec)
>> DFS CAC time: 60000 ms
>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 46424 sec)
>> DFS CAC time: 60000 ms
>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>> DFS state: usable (for 46424 sec)
>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>> channels set manually by iw
>>
>>
>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>
>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>> wpa_supplicant v2.3
>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>
>>
>> Re. the regulatory settings:
>>
>> root@voyage1:/opt/ca_node/etc# iw reg get
>> country US: DFS-FCC
>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>
>>
>> Any other thoughts?
>>
>> Marcel
>>
>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>> <janusz.dziedzic@tieto.com> wrote:
>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>>> Hi everyone,
>>>>
>>>> Reading this thread, I would like to share with people some doubts about it.
>>>> @Marco, I imagine you want to run your WLE600VX device using the 802.11ac
>>>> protocol, isn't it?
>>>> @Janusz, with running wpa_supplicant on both computers, will the ad-hoc
>>>> connection be established? I am starting with these tools and now, I am
>>>> getting used to know how they work. I was creating the ad-hoc connection
>>>> with the iw tool.
>>>>
>>> Yes you should use wpa_supplicant on both PC.
>>> In the future probably someone will add IBSS-VHT support also for iw.
>>>
>>> BR
>>> Janusz
>>>
>>>> Thanks,
>>>>
>>>>
>>>>
>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>
>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>
>>>>>> Hi everyone,
>>>>>> I have an interesting issue - I'm trying to run the QCA9882 based card
>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to run
>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it in
>>>>>> 80MHz width resolves in the following:
>>>>>>
>>>>> You should run IBSS using fresh wpa_supplicant (best latest code). By
>>>>> default should run in 80MHz.
>>>>> Other case is your regulatory - are you allow to use 80MHz on channel
>>>>> 157? First try 5180.
>>>>>
>>>>> eg. of wpa_supplicant config:
>>>>>
>>>>> network = {
>>>>> ssid="test_ibss"
>>>>> key_mgmt=NONE
>>>>> mode=1
>>>>> frequency=5180
>>>>> }
>>>>>
>>>>> BR
>>>>> Janusz
>>>>>
>>>>>> Interface wlan0
>>>>>> ifindex 5
>>>>>> wdev 0x1
>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>> ssid my-mesh-network
>>>>>> type IBSS
>>>>>> wiphy 0
>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>> command failed: Invalid argument (-22)
>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>> command failed: Invalid argument (-22)
>>>>>>
>>>>>>
>>>>>> More info:
>>>>>> =====================================================
>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac Wireless
>>>>>> Network Adapter
>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>> Capabilities: [40] Power Management version 2
>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>> Capabilities: [140] Virtual Channel
>>>>>> Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
>>>>>> Kernel driver in use: ath10k_pci
>>>>>>
>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>> country US: DFS-FCC
>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>
>>>>>>
>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8 14:03:33
>>>>>> GMT 2015 i686 GNU/Linux
>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux 0.10
>>>>>> .config)
>>>>>>
>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum ./firmware-2.bin
>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>> (this is from the 'main' directory in the
>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>
>>>>>>
>>>>>> Wiphy phy0
>>>>>> max # scan SSIDs: 16
>>>>>> max scan IEs length: 195 bytes
>>>>>> Retry short limit: 7
>>>>>> Retry long limit: 4
>>>>>> Coverage class: 0 (up to 0m)
>>>>>> Device supports RSN-IBSS.
>>>>>> Device supports AP-side u-APSD.
>>>>>> Supported Ciphers:
>>>>>> * WEP40 (00-0f-ac:1)
>>>>>> * WEP104 (00-0f-ac:5)
>>>>>> * TKIP (00-0f-ac:2)
>>>>>> * CCMP (00-0f-ac:4)
>>>>>> * CMAC (00-0f-ac:6)
>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>> Supported interface modes:
>>>>>> * IBSS
>>>>>> * managed
>>>>>> * AP
>>>>>> * AP/VLAN
>>>>>> * monitor
>>>>>> * P2P-client
>>>>>> * P2P-GO
>>>>>> * P2P-device
>>>>>> Band 1:
>>>>>> Capabilities: 0x19e3
>>>>>> RX LDPC
>>>>>> HT20/HT40
>>>>>> Static SM Power Save
>>>>>> RX HT20 SGI
>>>>>> RX HT40 SGI
>>>>>> TX STBC
>>>>>> RX STBC 1-stream
>>>>>> Max AMSDU length: 7935 bytes
>>>>>> DSSS/CCK HT40
>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>> VHT Capabilities (0x338001b2):
>>>>>> Max MPDU length: 11454
>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>> RX LDPC
>>>>>> short GI (80 MHz)
>>>>>> TX STBC
>>>>>> RX antenna pattern consistency
>>>>>> TX antenna pattern consistency
>>>>>> VHT RX MCS set:
>>>>>> 1 streams: MCS 0-9
>>>>>> 2 streams: MCS 0-9
>>>>>> 3 streams: not supported
>>>>>> 4 streams: not supported
>>>>>> 5 streams: not supported
>>>>>> 6 streams: not supported
>>>>>> 7 streams: not supported
>>>>>> 8 streams: not supported
>>>>>> VHT RX highest supported: 0 Mbps
>>>>>> VHT TX MCS set:
>>>>>> 1 streams: MCS 0-9
>>>>>> 2 streams: MCS 0-9
>>>>>> 3 streams: not supported
>>>>>> 4 streams: not supported
>>>>>> 5 streams: not supported
>>>>>> 6 streams: not supported
>>>>>> 7 streams: not supported
>>>>>> 8 streams: not supported
>>>>>> VHT TX highest supported: 0 Mbps
>>>>>> Bitrates (non-HT):
>>>>>> * 1.0 Mbps
>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>> * 6.0 Mbps
>>>>>> * 9.0 Mbps
>>>>>> * 12.0 Mbps
>>>>>> * 18.0 Mbps
>>>>>> * 24.0 Mbps
>>>>>> * 36.0 Mbps
>>>>>> * 48.0 Mbps
>>>>>> * 54.0 Mbps
>>>>>> Frequencies:
>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>> * 2467 MHz [12] (disabled)
>>>>>> * 2472 MHz [13] (disabled)
>>>>>> * 2484 MHz [14] (disabled)
>>>>>> Band 2:
>>>>>> Capabilities: 0x19e3
>>>>>> RX LDPC
>>>>>> HT20/HT40
>>>>>> Static SM Power Save
>>>>>> RX HT20 SGI
>>>>>> RX HT40 SGI
>>>>>> TX STBC
>>>>>> RX STBC 1-stream
>>>>>> Max AMSDU length: 7935 bytes
>>>>>> DSSS/CCK HT40
>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>> VHT Capabilities (0x338001b2):
>>>>>> Max MPDU length: 11454
>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>> RX LDPC
>>>>>> short GI (80 MHz)
>>>>>> TX STBC
>>>>>> RX antenna pattern consistency
>>>>>> TX antenna pattern consistency
>>>>>> VHT RX MCS set:
>>>>>> 1 streams: MCS 0-9
>>>>>> 2 streams: MCS 0-9
>>>>>> 3 streams: not supported
>>>>>> 4 streams: not supported
>>>>>> 5 streams: not supported
>>>>>> 6 streams: not supported
>>>>>> 7 streams: not supported
>>>>>> 8 streams: not supported
>>>>>> VHT RX highest supported: 0 Mbps
>>>>>> VHT TX MCS set:
>>>>>> 1 streams: MCS 0-9
>>>>>> 2 streams: MCS 0-9
>>>>>> 3 streams: not supported
>>>>>> 4 streams: not supported
>>>>>> 5 streams: not supported
>>>>>> 6 streams: not supported
>>>>>> 7 streams: not supported
>>>>>> 8 streams: not supported
>>>>>> VHT TX highest supported: 0 Mbps
>>>>>> Bitrates (non-HT):
>>>>>> * 6.0 Mbps
>>>>>> * 9.0 Mbps
>>>>>> * 12.0 Mbps
>>>>>> * 18.0 Mbps
>>>>>> * 24.0 Mbps
>>>>>> * 36.0 Mbps
>>>>>> * 48.0 Mbps
>>>>>> * 54.0 Mbps
>>>>>> Frequencies:
>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>> DFS state: usable (for 1076 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>> DFS state: usable (for 1076 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>> DFS state: usable (for 1076 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>> DFS state: usable (for 1076 sec)
>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>> Supported commands:
>>>>>> * new_interface
>>>>>> * set_interface
>>>>>> * new_key
>>>>>> * start_ap
>>>>>> * new_station
>>>>>> * set_bss
>>>>>> * authenticate
>>>>>> * associate
>>>>>> * deauthenticate
>>>>>> * disassociate
>>>>>> * join_ibss
>>>>>> * remain_on_channel
>>>>>> * set_tx_bitrate_mask
>>>>>> * frame
>>>>>> * frame_wait_cancel
>>>>>> * set_wiphy_netns
>>>>>> * set_channel
>>>>>> * set_wds_peer
>>>>>> * probe_client
>>>>>> * set_noack_map
>>>>>> * register_beacons
>>>>>> * start_p2p_device
>>>>>> * set_mcast_rate
>>>>>> * testmode
>>>>>> * channel_switch
>>>>>> * Unknown command (104)
>>>>>> * connect
>>>>>> * disconnect
>>>>>> Supported TX frame types:
>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0
>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>> Supported RX frame types:
>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>> * managed: 0x40 0xd0
>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>> * P2P-client: 0x40 0xd0
>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>> * P2P-device: 0x40 0xd0
>>>>>> software interface modes (can always be added):
>>>>>> * AP/VLAN
>>>>>> * monitor
>>>>>> valid interface combinations:
>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>> HT Capability overrides:
>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>> * maximum A-MSDU length
>>>>>> * supported channel width
>>>>>> * short GI for 40 MHz
>>>>>> * max A-MPDU length exponent
>>>>>> * min MPDU start spacing
>>>>>> Device supports TX status socket option.
>>>>>> Device supports HT-IBSS.
>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>> Device supports scan flush.
>>>>>> Device supports per-vif TX power setting
>>>>>> Driver supports a userspace MPM
>>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
>>>>>> Device supports static SMPS
>>>>>> =====================================================
>>>>>>
>>>>>> I am grateful for any help here and do have some time to help
>>>>>> debugging the issue.
>>>>>>
>>>>>> Marcel
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ------------------------------------------------------
>>>>>> This message is not intended to have
>>>>>> contractual effect
>>>>>> ------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>>
>>>>
>>>> --
>>>> Jorge Baranda
>>>> Research Engineer, MSc
>>>> jorge.baranda@cttc.es
>>>>
>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>> Av. Carl Friedrich Gauss, 7
>>>> 08860 Castelldefels, Barcelona (Spain)
>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>> Fax. +34 93 645 29 01
>>>> www.cttc.es
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>
>>
>>
>> --
>>
>> ------------------------------------------------------
>> This message is not intended to have
>> contractual effect
>> ------------------------------------------------------
>
>
>
> --
>
> ------------------------------------------------------
> This message is not intended to have
> contractual effect
> ------------------------------------------------------
>
> _______________________________________________
> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [SPAM] Re: WLE600VX from PCEngines
2015-09-09 11:08 ` [SPAM] " Jorge Baranda
@ 2015-09-09 11:14 ` Ben Greear
2015-09-09 11:15 ` Harms, Hannes
1 sibling, 0 replies; 22+ messages in thread
From: Ben Greear @ 2015-09-09 11:14 UTC (permalink / raw)
To: Jorge Baranda, ath10k
On 09/09/2015 04:08 AM, Jorge Baranda wrote:
> Hi,
>
> Good news!! Harms, could you share full wpa_supplicant configuration files?
> (for both computers).
> I will download the latest version of wpa_supplicant, apply your changes and try
> to make work IBSS mode and 80MHz with Candela Kernel 4.0.
If you are using our kernel, you probably want to use our CT ath10k firmware
as well. Otherwise, you might as well stick with stock upstream
kernels for most applications.
http://www.candelatech.com/ath10k.php
We do most testing with WLE900VX, but I think WLE600VX should also
work OK.
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] 22+ messages in thread
* Re: [SPAM] Re: WLE600VX from PCEngines
2015-09-09 11:08 ` [SPAM] " Jorge Baranda
2015-09-09 11:14 ` Ben Greear
@ 2015-09-09 11:15 ` Harms, Hannes
2015-09-09 11:34 ` Marcel H.
2015-09-17 10:27 ` [SPAM] " Jorge Baranda
1 sibling, 2 replies; 22+ messages in thread
From: Harms, Hannes @ 2015-09-09 11:15 UTC (permalink / raw)
To: ath10k
My wpa_supplicant config:
ctrl_interface=DIR=/run/wpa_supplicant
ap_scan=2
network={
ssid="test"
bssid=02:12:34:56:78:9A
key_mgmt=NONE
mode=1
frequency=5180
disable_ht=0
disable_vht=0
disable_max_amsdu=1 # not sure, works also without this flag
}
Regards
Hannes
Am 09.09.2015 um 13:08 schrieb Jorge Baranda:
> Hi,
>
> Good news!! Harms, could you share full wpa_supplicant configuration
> files?
> (for both computers).
> I will download the latest version of wpa_supplicant, apply your
> changes and try
> to make work IBSS mode and 80MHz with Candela Kernel 4.0.
>
> Thanks,
>
> El 09/09/15 12:59, Harms, Hannes escribió:
>> Hi,
>>
>> I have WLE900VX working in IBSS mode and 80 Mhz with Candela Kernel
>> 4.2.
>> For me also the latest wpa_supplicant was not able to activate 80MHz
>> by default , I don't no why.
>>
>> The only way I found to get it working was to modify
>> wpa_supplicant/wpa_supplicant.c
>> Commit following two lines in wpa_supplicant.c like this :
>>
>> //if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
>> // return;
>>
>> That was all for me to get it working.
>>
>> wpa_supplicant config file:
>> # Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is
>> ignored)
>> CONFIG_LIBNL32=y
>>
>> # Support VHT overrides (disable VHT, mask MCS rates, etc.)
>> CONFIG_VHT_OVERRIDES=y
>>
>> # Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
>> CONFIG_HT_OVERRIDES=y
>>
>> # IEEE 802.11n (High Throughput) support (mainly for AP mode)
>> CONFIG_IEEE80211N=y
>>
>> # IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
>> # (depends on CONFIG_IEEE80211N)
>> CONFIG_IEEE80211AC=y
>>
>> # IEEE 802.11w (management frame protection), also known as PMF
>> # Driver support is also needed for IEEE 802.11w.
>> CONFIG_IEEE80211W=y
>>
>> Am 09.09.2015 um 11:46 schrieb Marcel H.:
>>> May I ask someone for support on this one?
>>> We would really like to make this work and I'm running out of ideas -
>>> is there any way do turn detailed debugging on to get a better
>>> understanding why do I get the following message back? ->
>>>
>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>> command failed: Device or resource busy (-16)
>>>
>>> Thanks,
>>> Marcel
>>>
>>> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>>>> Thanks for the response, unfortunately this is the result of defining
>>>> the center frequency:
>>>>
>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>> command failed: Device or resource busy (-16)
>>>>
>>>> Also, using wpa_supplicant does not work using the following config:
>>>>
>>>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>>>> ap_scan=2
>>>> ctrl_interface=/run/wpa_supplicant
>>>> update_config=1
>>>> device_type=0-00000000-0
>>>>
>>>> network={
>>>> scan_ssid=1
>>>> key_mgmt=NONE
>>>> priority=1
>>>> ssid="ibss"
>>>> mode=1
>>>> frequency=5180
>>>> }
>>>>
>>>> running as:
>>>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D
>>>> nl80211,wext
>>>>
>>>>
>>>>
>>>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>>>> Interface wlan0
>>>> ifindex 5
>>>> wdev 0x100000001
>>>> addr 04:f0:21:1b:5f:3d
>>>> ssid ibss-rsn
>>>> type IBSS
>>>> wiphy 1
>>>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>>>
>>>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>>>> Wiphy phy1
>>>> DFS state: usable (for 46424 sec)
>>>> DFS CAC time: 60000 ms
>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>>> detection)
>>>> DFS state: usable (for 46424 sec)
>>>> DFS CAC time: 60000 ms
>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>>> detection)
>>>> DFS state: usable (for 46424 sec)
>>>> DFS CAC time: 60000 ms
>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>>> detection)
>>>> DFS state: usable (for 46424 sec)
>>>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>>>> channels set manually by iw
>>>>
>>>>
>>>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>>>
>>>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>>> wpa_supplicant v2.3
>>>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>>>
>>>>
>>>> Re. the regulatory settings:
>>>>
>>>> root@voyage1:/opt/ca_node/etc# iw reg get
>>>> country US: DFS-FCC
>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>
>>>>
>>>> Any other thoughts?
>>>>
>>>> Marcel
>>>>
>>>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>>>> <janusz.dziedzic@tieto.com> wrote:
>>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>>>>> Hi everyone,
>>>>>>
>>>>>> Reading this thread, I would like to share with people some
>>>>>> doubts about it.
>>>>>> @Marco, I imagine you want to run your WLE600VX device using the
>>>>>> 802.11ac
>>>>>> protocol, isn't it?
>>>>>> @Janusz, with running wpa_supplicant on both computers, will the
>>>>>> ad-hoc
>>>>>> connection be established? I am starting with these tools and
>>>>>> now, I am
>>>>>> getting used to know how they work. I was creating the ad-hoc
>>>>>> connection
>>>>>> with the iw tool.
>>>>>>
>>>>> Yes you should use wpa_supplicant on both PC.
>>>>> In the future probably someone will add IBSS-VHT support also for iw.
>>>>>
>>>>> BR
>>>>> Janusz
>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>>
>>>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>>>
>>>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>>> Hi everyone,
>>>>>>>> I have an interesting issue - I'm trying to run the QCA9882
>>>>>>>> based card
>>>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is
>>>>>>>> to run
>>>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run
>>>>>>>> it in
>>>>>>>> 80MHz width resolves in the following:
>>>>>>>>
>>>>>>> You should run IBSS using fresh wpa_supplicant (best latest
>>>>>>> code). By
>>>>>>> default should run in 80MHz.
>>>>>>> Other case is your regulatory - are you allow to use 80MHz on
>>>>>>> channel
>>>>>>> 157? First try 5180.
>>>>>>>
>>>>>>> eg. of wpa_supplicant config:
>>>>>>>
>>>>>>> network = {
>>>>>>> ssid="test_ibss"
>>>>>>> key_mgmt=NONE
>>>>>>> mode=1
>>>>>>> frequency=5180
>>>>>>> }
>>>>>>>
>>>>>>> BR
>>>>>>> Janusz
>>>>>>>
>>>>>>>> Interface wlan0
>>>>>>>> ifindex 5
>>>>>>>> wdev 0x1
>>>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>>>> ssid my-mesh-network
>>>>>>>> type IBSS
>>>>>>>> wiphy 0
>>>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>
>>>>>>>>
>>>>>>>> More info:
>>>>>>>> =====================================================
>>>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac
>>>>>>>> Wireless
>>>>>>>> Network Adapter
>>>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>>>> Capabilities: [40] Power Management version 2
>>>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>>>> Capabilities: [140] Virtual Channel
>>>>>>>> Capabilities: [160] Device Serial Number
>>>>>>>> 00-00-00-00-00-00-00-00
>>>>>>>> Kernel driver in use: ath10k_pci
>>>>>>>>
>>>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>>>> country US: DFS-FCC
>>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>>
>>>>>>>>
>>>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8
>>>>>>>> 14:03:33
>>>>>>>> GMT 2015 i686 GNU/Linux
>>>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage
>>>>>>>> Linux 0.10
>>>>>>>> .config)
>>>>>>>>
>>>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum
>>>>>>>> ./firmware-2.bin
>>>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>>>> (this is from the 'main' directory in the
>>>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>>>
>>>>>>>>
>>>>>>>> Wiphy phy0
>>>>>>>> max # scan SSIDs: 16
>>>>>>>> max scan IEs length: 195 bytes
>>>>>>>> Retry short limit: 7
>>>>>>>> Retry long limit: 4
>>>>>>>> Coverage class: 0 (up to 0m)
>>>>>>>> Device supports RSN-IBSS.
>>>>>>>> Device supports AP-side u-APSD.
>>>>>>>> Supported Ciphers:
>>>>>>>> * WEP40 (00-0f-ac:1)
>>>>>>>> * WEP104 (00-0f-ac:5)
>>>>>>>> * TKIP (00-0f-ac:2)
>>>>>>>> * CCMP (00-0f-ac:4)
>>>>>>>> * CMAC (00-0f-ac:6)
>>>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>>>> Supported interface modes:
>>>>>>>> * IBSS
>>>>>>>> * managed
>>>>>>>> * AP
>>>>>>>> * AP/VLAN
>>>>>>>> * monitor
>>>>>>>> * P2P-client
>>>>>>>> * P2P-GO
>>>>>>>> * P2P-device
>>>>>>>> Band 1:
>>>>>>>> Capabilities: 0x19e3
>>>>>>>> RX LDPC
>>>>>>>> HT20/HT40
>>>>>>>> Static SM Power Save
>>>>>>>> RX HT20 SGI
>>>>>>>> RX HT40 SGI
>>>>>>>> TX STBC
>>>>>>>> RX STBC 1-stream
>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>> DSSS/CCK HT40
>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>> Max MPDU length: 11454
>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>> RX LDPC
>>>>>>>> short GI (80 MHz)
>>>>>>>> TX STBC
>>>>>>>> RX antenna pattern consistency
>>>>>>>> TX antenna pattern consistency
>>>>>>>> VHT RX MCS set:
>>>>>>>> 1 streams: MCS 0-9
>>>>>>>> 2 streams: MCS 0-9
>>>>>>>> 3 streams: not supported
>>>>>>>> 4 streams: not supported
>>>>>>>> 5 streams: not supported
>>>>>>>> 6 streams: not supported
>>>>>>>> 7 streams: not supported
>>>>>>>> 8 streams: not supported
>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>> VHT TX MCS set:
>>>>>>>> 1 streams: MCS 0-9
>>>>>>>> 2 streams: MCS 0-9
>>>>>>>> 3 streams: not supported
>>>>>>>> 4 streams: not supported
>>>>>>>> 5 streams: not supported
>>>>>>>> 6 streams: not supported
>>>>>>>> 7 streams: not supported
>>>>>>>> 8 streams: not supported
>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>> Bitrates (non-HT):
>>>>>>>> * 1.0 Mbps
>>>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>>>> * 6.0 Mbps
>>>>>>>> * 9.0 Mbps
>>>>>>>> * 12.0 Mbps
>>>>>>>> * 18.0 Mbps
>>>>>>>> * 24.0 Mbps
>>>>>>>> * 36.0 Mbps
>>>>>>>> * 48.0 Mbps
>>>>>>>> * 54.0 Mbps
>>>>>>>> Frequencies:
>>>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>>>> * 2467 MHz [12] (disabled)
>>>>>>>> * 2472 MHz [13] (disabled)
>>>>>>>> * 2484 MHz [14] (disabled)
>>>>>>>> Band 2:
>>>>>>>> Capabilities: 0x19e3
>>>>>>>> RX LDPC
>>>>>>>> HT20/HT40
>>>>>>>> Static SM Power Save
>>>>>>>> RX HT20 SGI
>>>>>>>> RX HT40 SGI
>>>>>>>> TX STBC
>>>>>>>> RX STBC 1-stream
>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>> DSSS/CCK HT40
>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>> Max MPDU length: 11454
>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>> RX LDPC
>>>>>>>> short GI (80 MHz)
>>>>>>>> TX STBC
>>>>>>>> RX antenna pattern consistency
>>>>>>>> TX antenna pattern consistency
>>>>>>>> VHT RX MCS set:
>>>>>>>> 1 streams: MCS 0-9
>>>>>>>> 2 streams: MCS 0-9
>>>>>>>> 3 streams: not supported
>>>>>>>> 4 streams: not supported
>>>>>>>> 5 streams: not supported
>>>>>>>> 6 streams: not supported
>>>>>>>> 7 streams: not supported
>>>>>>>> 8 streams: not supported
>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>> VHT TX MCS set:
>>>>>>>> 1 streams: MCS 0-9
>>>>>>>> 2 streams: MCS 0-9
>>>>>>>> 3 streams: not supported
>>>>>>>> 4 streams: not supported
>>>>>>>> 5 streams: not supported
>>>>>>>> 6 streams: not supported
>>>>>>>> 7 streams: not supported
>>>>>>>> 8 streams: not supported
>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>> Bitrates (non-HT):
>>>>>>>> * 6.0 Mbps
>>>>>>>> * 9.0 Mbps
>>>>>>>> * 12.0 Mbps
>>>>>>>> * 18.0 Mbps
>>>>>>>> * 24.0 Mbps
>>>>>>>> * 36.0 Mbps
>>>>>>>> * 48.0 Mbps
>>>>>>>> * 54.0 Mbps
>>>>>>>> Frequencies:
>>>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>>>> Supported commands:
>>>>>>>> * new_interface
>>>>>>>> * set_interface
>>>>>>>> * new_key
>>>>>>>> * start_ap
>>>>>>>> * new_station
>>>>>>>> * set_bss
>>>>>>>> * authenticate
>>>>>>>> * associate
>>>>>>>> * deauthenticate
>>>>>>>> * disassociate
>>>>>>>> * join_ibss
>>>>>>>> * remain_on_channel
>>>>>>>> * set_tx_bitrate_mask
>>>>>>>> * frame
>>>>>>>> * frame_wait_cancel
>>>>>>>> * set_wiphy_netns
>>>>>>>> * set_channel
>>>>>>>> * set_wds_peer
>>>>>>>> * probe_client
>>>>>>>> * set_noack_map
>>>>>>>> * register_beacons
>>>>>>>> * start_p2p_device
>>>>>>>> * set_mcast_rate
>>>>>>>> * testmode
>>>>>>>> * channel_switch
>>>>>>>> * Unknown command (104)
>>>>>>>> * connect
>>>>>>>> * disconnect
>>>>>>>> Supported TX frame types:
>>>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>> 0x90
>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>> 0x80 0x90
>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>> 0x90 0xa0
>>>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>> 0x80 0x90
>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>> 0x70 0x80
>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>> 0x70 0x80
>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>> 0x80 0x90
>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>> 0x70 0x80
>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>> Supported RX frame types:
>>>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>>>> * managed: 0x40 0xd0
>>>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>>>> * P2P-client: 0x40 0xd0
>>>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>> * P2P-device: 0x40 0xd0
>>>>>>>> software interface modes (can always be added):
>>>>>>>> * AP/VLAN
>>>>>>>> * monitor
>>>>>>>> valid interface combinations:
>>>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>>>> HT Capability overrides:
>>>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>>>> * maximum A-MSDU length
>>>>>>>> * supported channel width
>>>>>>>> * short GI for 40 MHz
>>>>>>>> * max A-MPDU length exponent
>>>>>>>> * min MPDU start spacing
>>>>>>>> Device supports TX status socket option.
>>>>>>>> Device supports HT-IBSS.
>>>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>>>> Device supports scan flush.
>>>>>>>> Device supports per-vif TX power setting
>>>>>>>> Driver supports a userspace MPM
>>>>>>>> Driver/device bandwidth changes during BSS lifetime
>>>>>>>> (AP/GO mode)
>>>>>>>> Device supports static SMPS
>>>>>>>> =====================================================
>>>>>>>>
>>>>>>>> I am grateful for any help here and do have some time to help
>>>>>>>> debugging the issue.
>>>>>>>>
>>>>>>>> Marcel
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> ------------------------------------------------------
>>>>>>>> This message is not intended to have
>>>>>>>> contractual effect
>>>>>>>> ------------------------------------------------------
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jorge Baranda
>>>>>> Research Engineer, MSc
>>>>>> jorge.baranda@cttc.es
>>>>>>
>>>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>>>> Av. Carl Friedrich Gauss, 7
>>>>>> 08860 Castelldefels, Barcelona (Spain)
>>>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>>>> Fax. +34 93 645 29 01
>>>>>> www.cttc.es
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>>
>>>> --
>>>>
>>>> ------------------------------------------------------
>>>> This message is not intended to have
>>>> contractual effect
>>>> ------------------------------------------------------
>>>
>>>
>>
>
>
--
Dipl.-Ing. Hannes Harms
Technische Universität Braunschweig
Institut für mobile Maschinen und Nutzfahrzeuge
Langer Kamp 19a
D-38106 Braunschweig
Durchwahl: +49 (0)531 391-7197
E-Mail: hannes.harms@tu-braunschweig.de
http://www.tu-braunschweig.de/imn
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [SPAM] Re: WLE600VX from PCEngines
2015-09-09 11:15 ` Harms, Hannes
@ 2015-09-09 11:34 ` Marcel H.
2015-09-09 11:40 ` Marcel H.
2015-09-17 10:27 ` [SPAM] " Jorge Baranda
1 sibling, 1 reply; 22+ messages in thread
From: Marcel H. @ 2015-09-09 11:34 UTC (permalink / raw)
To: ath10k
I got the card working on 80MHz chan width using the _latest_ (as of
today) wpa_supplicant git checkout and a custom-build github/kvalo/ath
kernel as mentioned previously by me in this thread.
The wpa_supplicant config:
ap_scan=2
update_config=1
network={
scan_ssid=1
key_mgmt=NONE
priority=1
ssid="ibss"
mode=1
frequency=5180
}
The test:
(half-duplex) [ 3] 0.0-10.0 sec 331 MBytes 277 Mbits/sec
Interface wlan0
ifindex 5
wdev 0x100000001
addr 04:f0:21:1b:5f:3d
ssid ibss
type IBSS
wiphy 1
channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
This is good enough for my current deployment, but was wondering whats
the deal with 80+80MHz and 160MHz channel width config.
Can this be enforced?
Thanks to everyone for your help,
Marcel
On Wed, Sep 9, 2015 at 1:15 PM, Harms, Hannes <hannes.harms@tu-bs.de> wrote:
> My wpa_supplicant config:
>
>
> ctrl_interface=DIR=/run/wpa_supplicant
> ap_scan=2
>
> network={
> ssid="test"
> bssid=02:12:34:56:78:9A
> key_mgmt=NONE
> mode=1
> frequency=5180
> disable_ht=0
> disable_vht=0
> disable_max_amsdu=1 # not sure, works also without this flag
> }
>
>
> Regards
> Hannes
>
>
> Am 09.09.2015 um 13:08 schrieb Jorge Baranda:
>>
>> Hi,
>>
>> Good news!! Harms, could you share full wpa_supplicant configuration
>> files?
>> (for both computers).
>> I will download the latest version of wpa_supplicant, apply your changes
>> and try
>> to make work IBSS mode and 80MHz with Candela Kernel 4.0.
>>
>> Thanks,
>>
>> El 09/09/15 12:59, Harms, Hannes escribió:
>>>
>>> Hi,
>>>
>>> I have WLE900VX working in IBSS mode and 80 Mhz with Candela Kernel 4.2.
>>> For me also the latest wpa_supplicant was not able to activate 80MHz by
>>> default , I don't no why.
>>>
>>> The only way I found to get it working was to modify
>>> wpa_supplicant/wpa_supplicant.c
>>> Commit following two lines in wpa_supplicant.c like this :
>>>
>>> //if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
>>> // return;
>>>
>>> That was all for me to get it working.
>>>
>>> wpa_supplicant config file:
>>> # Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is
>>> ignored)
>>> CONFIG_LIBNL32=y
>>>
>>> # Support VHT overrides (disable VHT, mask MCS rates, etc.)
>>> CONFIG_VHT_OVERRIDES=y
>>>
>>> # Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
>>> CONFIG_HT_OVERRIDES=y
>>>
>>> # IEEE 802.11n (High Throughput) support (mainly for AP mode)
>>> CONFIG_IEEE80211N=y
>>>
>>> # IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
>>> # (depends on CONFIG_IEEE80211N)
>>> CONFIG_IEEE80211AC=y
>>>
>>> # IEEE 802.11w (management frame protection), also known as PMF
>>> # Driver support is also needed for IEEE 802.11w.
>>> CONFIG_IEEE80211W=y
>>>
>>> Am 09.09.2015 um 11:46 schrieb Marcel H.:
>>>>
>>>> May I ask someone for support on this one?
>>>> We would really like to make this work and I'm running out of ideas -
>>>> is there any way do turn detailed debugging on to get a better
>>>> understanding why do I get the following message back? ->
>>>>
>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>> command failed: Device or resource busy (-16)
>>>>
>>>> Thanks,
>>>> Marcel
>>>>
>>>> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>>>>>
>>>>> Thanks for the response, unfortunately this is the result of defining
>>>>> the center frequency:
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>>> command failed: Device or resource busy (-16)
>>>>>
>>>>> Also, using wpa_supplicant does not work using the following config:
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>>>>> ap_scan=2
>>>>> ctrl_interface=/run/wpa_supplicant
>>>>> update_config=1
>>>>> device_type=0-00000000-0
>>>>>
>>>>> network={
>>>>> scan_ssid=1
>>>>> key_mgmt=NONE
>>>>> priority=1
>>>>> ssid="ibss"
>>>>> mode=1
>>>>> frequency=5180
>>>>> }
>>>>>
>>>>> running as:
>>>>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D
>>>>> nl80211,wext
>>>>>
>>>>>
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>>>>> Interface wlan0
>>>>> ifindex 5
>>>>> wdev 0x100000001
>>>>> addr 04:f0:21:1b:5f:3d
>>>>> ssid ibss-rsn
>>>>> type IBSS
>>>>> wiphy 1
>>>>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>>>>> Wiphy phy1
>>>>> DFS state: usable (for 46424 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>>>> detection)
>>>>> DFS state: usable (for 46424 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>>>> detection)
>>>>> DFS state: usable (for 46424 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>>>> detection)
>>>>> DFS state: usable (for 46424 sec)
>>>>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>>>>> channels set manually by iw
>>>>>
>>>>>
>>>>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>>>> wpa_supplicant v2.3
>>>>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>>>>
>>>>>
>>>>> Re. the regulatory settings:
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw reg get
>>>>> country US: DFS-FCC
>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>
>>>>>
>>>>> Any other thoughts?
>>>>>
>>>>> Marcel
>>>>>
>>>>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>>>>> <janusz.dziedzic@tieto.com> wrote:
>>>>>>
>>>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>>>>>>
>>>>>>> Hi everyone,
>>>>>>>
>>>>>>> Reading this thread, I would like to share with people some doubts
>>>>>>> about it.
>>>>>>> @Marco, I imagine you want to run your WLE600VX device using the
>>>>>>> 802.11ac
>>>>>>> protocol, isn't it?
>>>>>>> @Janusz, with running wpa_supplicant on both computers, will the
>>>>>>> ad-hoc
>>>>>>> connection be established? I am starting with these tools and now, I
>>>>>>> am
>>>>>>> getting used to know how they work. I was creating the ad-hoc
>>>>>>> connection
>>>>>>> with the iw tool.
>>>>>>>
>>>>>> Yes you should use wpa_supplicant on both PC.
>>>>>> In the future probably someone will add IBSS-VHT support also for iw.
>>>>>>
>>>>>> BR
>>>>>> Janusz
>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>>>>
>>>>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>>>>
>>>>>>>>> Hi everyone,
>>>>>>>>> I have an interesting issue - I'm trying to run the QCA9882 based
>>>>>>>>> card
>>>>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to
>>>>>>>>> run
>>>>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it
>>>>>>>>> in
>>>>>>>>> 80MHz width resolves in the following:
>>>>>>>>>
>>>>>>>> You should run IBSS using fresh wpa_supplicant (best latest code).
>>>>>>>> By
>>>>>>>> default should run in 80MHz.
>>>>>>>> Other case is your regulatory - are you allow to use 80MHz on
>>>>>>>> channel
>>>>>>>> 157? First try 5180.
>>>>>>>>
>>>>>>>> eg. of wpa_supplicant config:
>>>>>>>>
>>>>>>>> network = {
>>>>>>>> ssid="test_ibss"
>>>>>>>> key_mgmt=NONE
>>>>>>>> mode=1
>>>>>>>> frequency=5180
>>>>>>>> }
>>>>>>>>
>>>>>>>> BR
>>>>>>>> Janusz
>>>>>>>>
>>>>>>>>> Interface wlan0
>>>>>>>>> ifindex 5
>>>>>>>>> wdev 0x1
>>>>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>>>>> ssid my-mesh-network
>>>>>>>>> type IBSS
>>>>>>>>> wiphy 0
>>>>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> More info:
>>>>>>>>> =====================================================
>>>>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac
>>>>>>>>> Wireless
>>>>>>>>> Network Adapter
>>>>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>>>>> Capabilities: [40] Power Management version 2
>>>>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>>>>> Capabilities: [140] Virtual Channel
>>>>>>>>> Capabilities: [160] Device Serial Number
>>>>>>>>> 00-00-00-00-00-00-00-00
>>>>>>>>> Kernel driver in use: ath10k_pci
>>>>>>>>>
>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>>>>> country US: DFS-FCC
>>>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8
>>>>>>>>> 14:03:33
>>>>>>>>> GMT 2015 i686 GNU/Linux
>>>>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux
>>>>>>>>> 0.10
>>>>>>>>> .config)
>>>>>>>>>
>>>>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum
>>>>>>>>> ./firmware-2.bin
>>>>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>>>>> (this is from the 'main' directory in the
>>>>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Wiphy phy0
>>>>>>>>> max # scan SSIDs: 16
>>>>>>>>> max scan IEs length: 195 bytes
>>>>>>>>> Retry short limit: 7
>>>>>>>>> Retry long limit: 4
>>>>>>>>> Coverage class: 0 (up to 0m)
>>>>>>>>> Device supports RSN-IBSS.
>>>>>>>>> Device supports AP-side u-APSD.
>>>>>>>>> Supported Ciphers:
>>>>>>>>> * WEP40 (00-0f-ac:1)
>>>>>>>>> * WEP104 (00-0f-ac:5)
>>>>>>>>> * TKIP (00-0f-ac:2)
>>>>>>>>> * CCMP (00-0f-ac:4)
>>>>>>>>> * CMAC (00-0f-ac:6)
>>>>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>>>>> Supported interface modes:
>>>>>>>>> * IBSS
>>>>>>>>> * managed
>>>>>>>>> * AP
>>>>>>>>> * AP/VLAN
>>>>>>>>> * monitor
>>>>>>>>> * P2P-client
>>>>>>>>> * P2P-GO
>>>>>>>>> * P2P-device
>>>>>>>>> Band 1:
>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>> RX LDPC
>>>>>>>>> HT20/HT40
>>>>>>>>> Static SM Power Save
>>>>>>>>> RX HT20 SGI
>>>>>>>>> RX HT40 SGI
>>>>>>>>> TX STBC
>>>>>>>>> RX STBC 1-stream
>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>> DSSS/CCK HT40
>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>> Max MPDU length: 11454
>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>> RX LDPC
>>>>>>>>> short GI (80 MHz)
>>>>>>>>> TX STBC
>>>>>>>>> RX antenna pattern consistency
>>>>>>>>> TX antenna pattern consistency
>>>>>>>>> VHT RX MCS set:
>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>> 3 streams: not supported
>>>>>>>>> 4 streams: not supported
>>>>>>>>> 5 streams: not supported
>>>>>>>>> 6 streams: not supported
>>>>>>>>> 7 streams: not supported
>>>>>>>>> 8 streams: not supported
>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>> VHT TX MCS set:
>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>> 3 streams: not supported
>>>>>>>>> 4 streams: not supported
>>>>>>>>> 5 streams: not supported
>>>>>>>>> 6 streams: not supported
>>>>>>>>> 7 streams: not supported
>>>>>>>>> 8 streams: not supported
>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>> Bitrates (non-HT):
>>>>>>>>> * 1.0 Mbps
>>>>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>>>>> * 6.0 Mbps
>>>>>>>>> * 9.0 Mbps
>>>>>>>>> * 12.0 Mbps
>>>>>>>>> * 18.0 Mbps
>>>>>>>>> * 24.0 Mbps
>>>>>>>>> * 36.0 Mbps
>>>>>>>>> * 48.0 Mbps
>>>>>>>>> * 54.0 Mbps
>>>>>>>>> Frequencies:
>>>>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>>>>> * 2467 MHz [12] (disabled)
>>>>>>>>> * 2472 MHz [13] (disabled)
>>>>>>>>> * 2484 MHz [14] (disabled)
>>>>>>>>> Band 2:
>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>> RX LDPC
>>>>>>>>> HT20/HT40
>>>>>>>>> Static SM Power Save
>>>>>>>>> RX HT20 SGI
>>>>>>>>> RX HT40 SGI
>>>>>>>>> TX STBC
>>>>>>>>> RX STBC 1-stream
>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>> DSSS/CCK HT40
>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>> Max MPDU length: 11454
>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>> RX LDPC
>>>>>>>>> short GI (80 MHz)
>>>>>>>>> TX STBC
>>>>>>>>> RX antenna pattern consistency
>>>>>>>>> TX antenna pattern consistency
>>>>>>>>> VHT RX MCS set:
>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>> 3 streams: not supported
>>>>>>>>> 4 streams: not supported
>>>>>>>>> 5 streams: not supported
>>>>>>>>> 6 streams: not supported
>>>>>>>>> 7 streams: not supported
>>>>>>>>> 8 streams: not supported
>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>> VHT TX MCS set:
>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>> 3 streams: not supported
>>>>>>>>> 4 streams: not supported
>>>>>>>>> 5 streams: not supported
>>>>>>>>> 6 streams: not supported
>>>>>>>>> 7 streams: not supported
>>>>>>>>> 8 streams: not supported
>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>> Bitrates (non-HT):
>>>>>>>>> * 6.0 Mbps
>>>>>>>>> * 9.0 Mbps
>>>>>>>>> * 12.0 Mbps
>>>>>>>>> * 18.0 Mbps
>>>>>>>>> * 24.0 Mbps
>>>>>>>>> * 36.0 Mbps
>>>>>>>>> * 48.0 Mbps
>>>>>>>>> * 54.0 Mbps
>>>>>>>>> Frequencies:
>>>>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>>>>> Supported commands:
>>>>>>>>> * new_interface
>>>>>>>>> * set_interface
>>>>>>>>> * new_key
>>>>>>>>> * start_ap
>>>>>>>>> * new_station
>>>>>>>>> * set_bss
>>>>>>>>> * authenticate
>>>>>>>>> * associate
>>>>>>>>> * deauthenticate
>>>>>>>>> * disassociate
>>>>>>>>> * join_ibss
>>>>>>>>> * remain_on_channel
>>>>>>>>> * set_tx_bitrate_mask
>>>>>>>>> * frame
>>>>>>>>> * frame_wait_cancel
>>>>>>>>> * set_wiphy_netns
>>>>>>>>> * set_channel
>>>>>>>>> * set_wds_peer
>>>>>>>>> * probe_client
>>>>>>>>> * set_noack_map
>>>>>>>>> * register_beacons
>>>>>>>>> * start_p2p_device
>>>>>>>>> * set_mcast_rate
>>>>>>>>> * testmode
>>>>>>>>> * channel_switch
>>>>>>>>> * Unknown command (104)
>>>>>>>>> * connect
>>>>>>>>> * disconnect
>>>>>>>>> Supported TX frame types:
>>>>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>> 0x90
>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>> 0x90
>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>>>>> 0xa0
>>>>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>> 0x90
>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>> 0x80
>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>> 0x80
>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>> 0x90
>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>> 0x80
>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> Supported RX frame types:
>>>>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>>>>> * managed: 0x40 0xd0
>>>>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>>>>> * P2P-client: 0x40 0xd0
>>>>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>> * P2P-device: 0x40 0xd0
>>>>>>>>> software interface modes (can always be added):
>>>>>>>>> * AP/VLAN
>>>>>>>>> * monitor
>>>>>>>>> valid interface combinations:
>>>>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>>>>> HT Capability overrides:
>>>>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>>>>> * maximum A-MSDU length
>>>>>>>>> * supported channel width
>>>>>>>>> * short GI for 40 MHz
>>>>>>>>> * max A-MPDU length exponent
>>>>>>>>> * min MPDU start spacing
>>>>>>>>> Device supports TX status socket option.
>>>>>>>>> Device supports HT-IBSS.
>>>>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>>>>> Device supports scan flush.
>>>>>>>>> Device supports per-vif TX power setting
>>>>>>>>> Driver supports a userspace MPM
>>>>>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO
>>>>>>>>> mode)
>>>>>>>>> Device supports static SMPS
>>>>>>>>> =====================================================
>>>>>>>>>
>>>>>>>>> I am grateful for any help here and do have some time to help
>>>>>>>>> debugging the issue.
>>>>>>>>>
>>>>>>>>> Marcel
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------
>>>>>>>>> This message is not intended to have
>>>>>>>>> contractual effect
>>>>>>>>> ------------------------------------------------------
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jorge Baranda
>>>>>>> Research Engineer, MSc
>>>>>>> jorge.baranda@cttc.es
>>>>>>>
>>>>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>>>>> Av. Carl Friedrich Gauss, 7
>>>>>>> 08860 Castelldefels, Barcelona (Spain)
>>>>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>>>>> Fax. +34 93 645 29 01
>>>>>>> www.cttc.es
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> ------------------------------------------------------
>>>>> This message is not intended to have
>>>>> contractual effect
>>>>> ------------------------------------------------------
>>>>
>>>>
>>>>
>>>
>>
>>
>
> --
> Dipl.-Ing. Hannes Harms
> Technische Universität Braunschweig
> Institut für mobile Maschinen und Nutzfahrzeuge
> Langer Kamp 19a
> D-38106 Braunschweig
>
> Durchwahl: +49 (0)531 391-7197
> E-Mail: hannes.harms@tu-braunschweig.de
> http://www.tu-braunschweig.de/imn
>
>
> _______________________________________________
> ath10k mailing list
> ath10k@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
--
------------------------------------------------------
This message is not intended to have
contractual effect
------------------------------------------------------
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [SPAM] Re: WLE600VX from PCEngines
2015-09-09 11:34 ` Marcel H.
@ 2015-09-09 11:40 ` Marcel H.
2015-09-09 18:22 ` Ben Greear
0 siblings, 1 reply; 22+ messages in thread
From: Marcel H. @ 2015-09-09 11:40 UTC (permalink / raw)
To: ath10k
One other things comes to mind - whats the relationship between the
Candelatech's kernel branch and the kvalo's
https://github.com/kvalo/ath/ ?
Using the 'main' firmware for ath10k (to support IBSS ad-hoc mode) Im
not entirely sure which kernel is leading development of the ath10k
driver.
Also, is 636 firmware the best / latest / recommended the most for the
IBSS mode? Or shall I have a look into other version from Candelatech
/ Kvalos repo?
Thanks!
Marcel
On Wed, Sep 9, 2015 at 1:34 PM, Marcel H. <maco@blava.net> wrote:
> I got the card working on 80MHz chan width using the _latest_ (as of
> today) wpa_supplicant git checkout and a custom-build github/kvalo/ath
> kernel as mentioned previously by me in this thread.
>
> The wpa_supplicant config:
>
> ap_scan=2
> update_config=1
>
> network={
> scan_ssid=1
> key_mgmt=NONE
> priority=1
> ssid="ibss"
> mode=1
> frequency=5180
> }
>
> The test:
> (half-duplex) [ 3] 0.0-10.0 sec 331 MBytes 277 Mbits/sec
>
> Interface wlan0
> ifindex 5
> wdev 0x100000001
> addr 04:f0:21:1b:5f:3d
> ssid ibss
> type IBSS
> wiphy 1
> channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
>
> This is good enough for my current deployment, but was wondering whats
> the deal with 80+80MHz and 160MHz channel width config.
> Can this be enforced?
>
> Thanks to everyone for your help,
> Marcel
>
> On Wed, Sep 9, 2015 at 1:15 PM, Harms, Hannes <hannes.harms@tu-bs.de> wrote:
>> My wpa_supplicant config:
>>
>>
>> ctrl_interface=DIR=/run/wpa_supplicant
>> ap_scan=2
>>
>> network={
>> ssid="test"
>> bssid=02:12:34:56:78:9A
>> key_mgmt=NONE
>> mode=1
>> frequency=5180
>> disable_ht=0
>> disable_vht=0
>> disable_max_amsdu=1 # not sure, works also without this flag
>> }
>>
>>
>> Regards
>> Hannes
>>
>>
>> Am 09.09.2015 um 13:08 schrieb Jorge Baranda:
>>>
>>> Hi,
>>>
>>> Good news!! Harms, could you share full wpa_supplicant configuration
>>> files?
>>> (for both computers).
>>> I will download the latest version of wpa_supplicant, apply your changes
>>> and try
>>> to make work IBSS mode and 80MHz with Candela Kernel 4.0.
>>>
>>> Thanks,
>>>
>>> El 09/09/15 12:59, Harms, Hannes escribió:
>>>>
>>>> Hi,
>>>>
>>>> I have WLE900VX working in IBSS mode and 80 Mhz with Candela Kernel 4.2.
>>>> For me also the latest wpa_supplicant was not able to activate 80MHz by
>>>> default , I don't no why.
>>>>
>>>> The only way I found to get it working was to modify
>>>> wpa_supplicant/wpa_supplicant.c
>>>> Commit following two lines in wpa_supplicant.c like this :
>>>>
>>>> //if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
>>>> // return;
>>>>
>>>> That was all for me to get it working.
>>>>
>>>> wpa_supplicant config file:
>>>> # Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is
>>>> ignored)
>>>> CONFIG_LIBNL32=y
>>>>
>>>> # Support VHT overrides (disable VHT, mask MCS rates, etc.)
>>>> CONFIG_VHT_OVERRIDES=y
>>>>
>>>> # Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
>>>> CONFIG_HT_OVERRIDES=y
>>>>
>>>> # IEEE 802.11n (High Throughput) support (mainly for AP mode)
>>>> CONFIG_IEEE80211N=y
>>>>
>>>> # IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
>>>> # (depends on CONFIG_IEEE80211N)
>>>> CONFIG_IEEE80211AC=y
>>>>
>>>> # IEEE 802.11w (management frame protection), also known as PMF
>>>> # Driver support is also needed for IEEE 802.11w.
>>>> CONFIG_IEEE80211W=y
>>>>
>>>> Am 09.09.2015 um 11:46 schrieb Marcel H.:
>>>>>
>>>>> May I ask someone for support on this one?
>>>>> We would really like to make this work and I'm running out of ideas -
>>>>> is there any way do turn detailed debugging on to get a better
>>>>> understanding why do I get the following message back? ->
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>>> command failed: Device or resource busy (-16)
>>>>>
>>>>> Thanks,
>>>>> Marcel
>>>>>
>>>>> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>>>>>>
>>>>>> Thanks for the response, unfortunately this is the result of defining
>>>>>> the center frequency:
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>>>> command failed: Device or resource busy (-16)
>>>>>>
>>>>>> Also, using wpa_supplicant does not work using the following config:
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>>>>>> ap_scan=2
>>>>>> ctrl_interface=/run/wpa_supplicant
>>>>>> update_config=1
>>>>>> device_type=0-00000000-0
>>>>>>
>>>>>> network={
>>>>>> scan_ssid=1
>>>>>> key_mgmt=NONE
>>>>>> priority=1
>>>>>> ssid="ibss"
>>>>>> mode=1
>>>>>> frequency=5180
>>>>>> }
>>>>>>
>>>>>> running as:
>>>>>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D
>>>>>> nl80211,wext
>>>>>>
>>>>>>
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>>>>>> Interface wlan0
>>>>>> ifindex 5
>>>>>> wdev 0x100000001
>>>>>> addr 04:f0:21:1b:5f:3d
>>>>>> ssid ibss-rsn
>>>>>> type IBSS
>>>>>> wiphy 1
>>>>>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>>>>>> Wiphy phy1
>>>>>> DFS state: usable (for 46424 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>>>>> detection)
>>>>>> DFS state: usable (for 46424 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>>>>> detection)
>>>>>> DFS state: usable (for 46424 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>>>>> detection)
>>>>>> DFS state: usable (for 46424 sec)
>>>>>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>>>>>> channels set manually by iw
>>>>>>
>>>>>>
>>>>>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>>>>> wpa_supplicant v2.3
>>>>>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>>>>>
>>>>>>
>>>>>> Re. the regulatory settings:
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw reg get
>>>>>> country US: DFS-FCC
>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>
>>>>>>
>>>>>> Any other thoughts?
>>>>>>
>>>>>> Marcel
>>>>>>
>>>>>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>>>>>> <janusz.dziedzic@tieto.com> wrote:
>>>>>>>
>>>>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es> wrote:
>>>>>>>>
>>>>>>>> Hi everyone,
>>>>>>>>
>>>>>>>> Reading this thread, I would like to share with people some doubts
>>>>>>>> about it.
>>>>>>>> @Marco, I imagine you want to run your WLE600VX device using the
>>>>>>>> 802.11ac
>>>>>>>> protocol, isn't it?
>>>>>>>> @Janusz, with running wpa_supplicant on both computers, will the
>>>>>>>> ad-hoc
>>>>>>>> connection be established? I am starting with these tools and now, I
>>>>>>>> am
>>>>>>>> getting used to know how they work. I was creating the ad-hoc
>>>>>>>> connection
>>>>>>>> with the iw tool.
>>>>>>>>
>>>>>>> Yes you should use wpa_supplicant on both PC.
>>>>>>> In the future probably someone will add IBSS-VHT support also for iw.
>>>>>>>
>>>>>>> BR
>>>>>>> Janusz
>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>>>>>
>>>>>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi everyone,
>>>>>>>>>> I have an interesting issue - I'm trying to run the QCA9882 based
>>>>>>>>>> card
>>>>>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to
>>>>>>>>>> run
>>>>>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it
>>>>>>>>>> in
>>>>>>>>>> 80MHz width resolves in the following:
>>>>>>>>>>
>>>>>>>>> You should run IBSS using fresh wpa_supplicant (best latest code).
>>>>>>>>> By
>>>>>>>>> default should run in 80MHz.
>>>>>>>>> Other case is your regulatory - are you allow to use 80MHz on
>>>>>>>>> channel
>>>>>>>>> 157? First try 5180.
>>>>>>>>>
>>>>>>>>> eg. of wpa_supplicant config:
>>>>>>>>>
>>>>>>>>> network = {
>>>>>>>>> ssid="test_ibss"
>>>>>>>>> key_mgmt=NONE
>>>>>>>>> mode=1
>>>>>>>>> frequency=5180
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> BR
>>>>>>>>> Janusz
>>>>>>>>>
>>>>>>>>>> Interface wlan0
>>>>>>>>>> ifindex 5
>>>>>>>>>> wdev 0x1
>>>>>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>>>>>> ssid my-mesh-network
>>>>>>>>>> type IBSS
>>>>>>>>>> wiphy 0
>>>>>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> More info:
>>>>>>>>>> =====================================================
>>>>>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac
>>>>>>>>>> Wireless
>>>>>>>>>> Network Adapter
>>>>>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>>>>>> Capabilities: [40] Power Management version 2
>>>>>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>>>>>> Capabilities: [140] Virtual Channel
>>>>>>>>>> Capabilities: [160] Device Serial Number
>>>>>>>>>> 00-00-00-00-00-00-00-00
>>>>>>>>>> Kernel driver in use: ath10k_pci
>>>>>>>>>>
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>>>>>> country US: DFS-FCC
>>>>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8
>>>>>>>>>> 14:03:33
>>>>>>>>>> GMT 2015 i686 GNU/Linux
>>>>>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux
>>>>>>>>>> 0.10
>>>>>>>>>> .config)
>>>>>>>>>>
>>>>>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum
>>>>>>>>>> ./firmware-2.bin
>>>>>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>>>>>> (this is from the 'main' directory in the
>>>>>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Wiphy phy0
>>>>>>>>>> max # scan SSIDs: 16
>>>>>>>>>> max scan IEs length: 195 bytes
>>>>>>>>>> Retry short limit: 7
>>>>>>>>>> Retry long limit: 4
>>>>>>>>>> Coverage class: 0 (up to 0m)
>>>>>>>>>> Device supports RSN-IBSS.
>>>>>>>>>> Device supports AP-side u-APSD.
>>>>>>>>>> Supported Ciphers:
>>>>>>>>>> * WEP40 (00-0f-ac:1)
>>>>>>>>>> * WEP104 (00-0f-ac:5)
>>>>>>>>>> * TKIP (00-0f-ac:2)
>>>>>>>>>> * CCMP (00-0f-ac:4)
>>>>>>>>>> * CMAC (00-0f-ac:6)
>>>>>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>>>>>> Supported interface modes:
>>>>>>>>>> * IBSS
>>>>>>>>>> * managed
>>>>>>>>>> * AP
>>>>>>>>>> * AP/VLAN
>>>>>>>>>> * monitor
>>>>>>>>>> * P2P-client
>>>>>>>>>> * P2P-GO
>>>>>>>>>> * P2P-device
>>>>>>>>>> Band 1:
>>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>>> RX LDPC
>>>>>>>>>> HT20/HT40
>>>>>>>>>> Static SM Power Save
>>>>>>>>>> RX HT20 SGI
>>>>>>>>>> RX HT40 SGI
>>>>>>>>>> TX STBC
>>>>>>>>>> RX STBC 1-stream
>>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>>> DSSS/CCK HT40
>>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>>> Max MPDU length: 11454
>>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>>> RX LDPC
>>>>>>>>>> short GI (80 MHz)
>>>>>>>>>> TX STBC
>>>>>>>>>> RX antenna pattern consistency
>>>>>>>>>> TX antenna pattern consistency
>>>>>>>>>> VHT RX MCS set:
>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>> 3 streams: not supported
>>>>>>>>>> 4 streams: not supported
>>>>>>>>>> 5 streams: not supported
>>>>>>>>>> 6 streams: not supported
>>>>>>>>>> 7 streams: not supported
>>>>>>>>>> 8 streams: not supported
>>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>>> VHT TX MCS set:
>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>> 3 streams: not supported
>>>>>>>>>> 4 streams: not supported
>>>>>>>>>> 5 streams: not supported
>>>>>>>>>> 6 streams: not supported
>>>>>>>>>> 7 streams: not supported
>>>>>>>>>> 8 streams: not supported
>>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>>> Bitrates (non-HT):
>>>>>>>>>> * 1.0 Mbps
>>>>>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>>>>>> * 6.0 Mbps
>>>>>>>>>> * 9.0 Mbps
>>>>>>>>>> * 12.0 Mbps
>>>>>>>>>> * 18.0 Mbps
>>>>>>>>>> * 24.0 Mbps
>>>>>>>>>> * 36.0 Mbps
>>>>>>>>>> * 48.0 Mbps
>>>>>>>>>> * 54.0 Mbps
>>>>>>>>>> Frequencies:
>>>>>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>>>>>> * 2467 MHz [12] (disabled)
>>>>>>>>>> * 2472 MHz [13] (disabled)
>>>>>>>>>> * 2484 MHz [14] (disabled)
>>>>>>>>>> Band 2:
>>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>>> RX LDPC
>>>>>>>>>> HT20/HT40
>>>>>>>>>> Static SM Power Save
>>>>>>>>>> RX HT20 SGI
>>>>>>>>>> RX HT40 SGI
>>>>>>>>>> TX STBC
>>>>>>>>>> RX STBC 1-stream
>>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>>> DSSS/CCK HT40
>>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>>> Max MPDU length: 11454
>>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>>> RX LDPC
>>>>>>>>>> short GI (80 MHz)
>>>>>>>>>> TX STBC
>>>>>>>>>> RX antenna pattern consistency
>>>>>>>>>> TX antenna pattern consistency
>>>>>>>>>> VHT RX MCS set:
>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>> 3 streams: not supported
>>>>>>>>>> 4 streams: not supported
>>>>>>>>>> 5 streams: not supported
>>>>>>>>>> 6 streams: not supported
>>>>>>>>>> 7 streams: not supported
>>>>>>>>>> 8 streams: not supported
>>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>>> VHT TX MCS set:
>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>> 3 streams: not supported
>>>>>>>>>> 4 streams: not supported
>>>>>>>>>> 5 streams: not supported
>>>>>>>>>> 6 streams: not supported
>>>>>>>>>> 7 streams: not supported
>>>>>>>>>> 8 streams: not supported
>>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>>> Bitrates (non-HT):
>>>>>>>>>> * 6.0 Mbps
>>>>>>>>>> * 9.0 Mbps
>>>>>>>>>> * 12.0 Mbps
>>>>>>>>>> * 18.0 Mbps
>>>>>>>>>> * 24.0 Mbps
>>>>>>>>>> * 36.0 Mbps
>>>>>>>>>> * 48.0 Mbps
>>>>>>>>>> * 54.0 Mbps
>>>>>>>>>> Frequencies:
>>>>>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>>>>>> Supported commands:
>>>>>>>>>> * new_interface
>>>>>>>>>> * set_interface
>>>>>>>>>> * new_key
>>>>>>>>>> * start_ap
>>>>>>>>>> * new_station
>>>>>>>>>> * set_bss
>>>>>>>>>> * authenticate
>>>>>>>>>> * associate
>>>>>>>>>> * deauthenticate
>>>>>>>>>> * disassociate
>>>>>>>>>> * join_ibss
>>>>>>>>>> * remain_on_channel
>>>>>>>>>> * set_tx_bitrate_mask
>>>>>>>>>> * frame
>>>>>>>>>> * frame_wait_cancel
>>>>>>>>>> * set_wiphy_netns
>>>>>>>>>> * set_channel
>>>>>>>>>> * set_wds_peer
>>>>>>>>>> * probe_client
>>>>>>>>>> * set_noack_map
>>>>>>>>>> * register_beacons
>>>>>>>>>> * start_p2p_device
>>>>>>>>>> * set_mcast_rate
>>>>>>>>>> * testmode
>>>>>>>>>> * channel_switch
>>>>>>>>>> * Unknown command (104)
>>>>>>>>>> * connect
>>>>>>>>>> * disconnect
>>>>>>>>>> Supported TX frame types:
>>>>>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>>> 0x90
>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>>> 0x90
>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90
>>>>>>>>>> 0xa0
>>>>>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>>> 0x90
>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>> 0x80
>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>> 0x80
>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>>> 0x90
>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>> 0x80
>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> Supported RX frame types:
>>>>>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>>>>>> * managed: 0x40 0xd0
>>>>>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>>>>>> * P2P-client: 0x40 0xd0
>>>>>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>> * P2P-device: 0x40 0xd0
>>>>>>>>>> software interface modes (can always be added):
>>>>>>>>>> * AP/VLAN
>>>>>>>>>> * monitor
>>>>>>>>>> valid interface combinations:
>>>>>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>>>>>> HT Capability overrides:
>>>>>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>>>>>> * maximum A-MSDU length
>>>>>>>>>> * supported channel width
>>>>>>>>>> * short GI for 40 MHz
>>>>>>>>>> * max A-MPDU length exponent
>>>>>>>>>> * min MPDU start spacing
>>>>>>>>>> Device supports TX status socket option.
>>>>>>>>>> Device supports HT-IBSS.
>>>>>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>>>>>> Device supports scan flush.
>>>>>>>>>> Device supports per-vif TX power setting
>>>>>>>>>> Driver supports a userspace MPM
>>>>>>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO
>>>>>>>>>> mode)
>>>>>>>>>> Device supports static SMPS
>>>>>>>>>> =====================================================
>>>>>>>>>>
>>>>>>>>>> I am grateful for any help here and do have some time to help
>>>>>>>>>> debugging the issue.
>>>>>>>>>>
>>>>>>>>>> Marcel
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------
>>>>>>>>>> This message is not intended to have
>>>>>>>>>> contractual effect
>>>>>>>>>> ------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jorge Baranda
>>>>>>>> Research Engineer, MSc
>>>>>>>> jorge.baranda@cttc.es
>>>>>>>>
>>>>>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>>>>>> Av. Carl Friedrich Gauss, 7
>>>>>>>> 08860 Castelldefels, Barcelona (Spain)
>>>>>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>>>>>> Fax. +34 93 645 29 01
>>>>>>>> www.cttc.es
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ------------------------------------------------------
>>>>>> This message is not intended to have
>>>>>> contractual effect
>>>>>> ------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>> --
>> Dipl.-Ing. Hannes Harms
>> Technische Universität Braunschweig
>> Institut für mobile Maschinen und Nutzfahrzeuge
>> Langer Kamp 19a
>> D-38106 Braunschweig
>>
>> Durchwahl: +49 (0)531 391-7197
>> E-Mail: hannes.harms@tu-braunschweig.de
>> http://www.tu-braunschweig.de/imn
>>
>>
>> _______________________________________________
>> ath10k mailing list
>> ath10k@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath10k
>
>
>
> --
>
> ------------------------------------------------------
> This message is not intended to have
> contractual effect
> ------------------------------------------------------
--
------------------------------------------------------
This message is not intended to have
contractual effect
------------------------------------------------------
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [SPAM] Re: WLE600VX from PCEngines
2015-09-09 11:40 ` Marcel H.
@ 2015-09-09 18:22 ` Ben Greear
0 siblings, 0 replies; 22+ messages in thread
From: Ben Greear @ 2015-09-09 18:22 UTC (permalink / raw)
To: Marcel H., ath10k
On 09/09/2015 04:40 AM, Marcel H. wrote:
> One other things comes to mind - whats the relationship between the
> Candelatech's kernel branch and the kvalo's
> https://github.com/kvalo/ath/ ?
> Using the 'main' firmware for ath10k (to support IBSS ad-hoc mode) Im
> not entirely sure which kernel is leading development of the ath10k
> driver.
CT kernels are normally based on upstream (Linus) kernels, but I do sometimes
grab patches from kvalo/ath.
In general, CT kernels have support for some additional features that CT
firmware provides (that are not necessarily available in official ath10k firmware).
>
> Also, is 636 firmware the best / latest / recommended the most for the
> IBSS mode? Or shall I have a look into other version from Candelatech
> / Kvalos repo?
I'm biased, but I think CT firmware would be a better choice that 636,
especially if you can run our CT kernel patches.
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] 22+ messages in thread
* Re: [SPAM] Re: [SPAM] Re: WLE600VX from PCEngines
2015-09-09 11:15 ` Harms, Hannes
2015-09-09 11:34 ` Marcel H.
@ 2015-09-17 10:27 ` Jorge Baranda
2015-09-17 15:39 ` Jorge Baranda
1 sibling, 1 reply; 22+ messages in thread
From: Jorge Baranda @ 2015-09-17 10:27 UTC (permalink / raw)
To: ath10k, Harms, Hannes
[-- Attachment #1: Type: text/plain, Size: 25160 bytes --]
Dear Hannes and all,
I have tried to replicate Hannes' setup to make work wpa_supplicant with
Candela Kernel 4.0 (and Candela firmware 10.1.467-ct-14), but I have not
been successful.
I downloaded the last version of wpa_supplicant from
http://w1.fi/wpa_supplicant/ website, applied your changes in the
wpa_supplicant.c file and your .config file.
Then I used your wpa_supplicant.conf file but it failed to start
(attached the full log). The error says that "the ctrl_interface exists
and seems to be in use"
I have checked with ps aux to see if there is a wpa_supplicant process
but after kill it, it restarts again.
This is the result of ps aux | grep wpa_supplicant:
root 2368 0.0 0.0 30868 6140 ? Ss 11:40 0:00
/sbin/wpa_supplicant -u -s -O /var/run/wpa_supplicant
monet 2690 0.0 0.0 13688 2372 pts/9 S+ 12:10 0:00 grep
--color=auto wpa_supplicant
Browsing in the internet I have not found any answer to solve this
problem :(. Have you faced it?
Then I have tried removing the "ctrl_interface line" from the
wpa_supplicant.conf file (resulting in a file similar to the one sent by
Marcel H.) and the program started in a loop (see attached
wpa_supplicant2.log). It seems like it tries to connect to the ssid
"test" but it is not able to find it (normal, because we want to create it).
Apart from this, in this setup, do I have to make any change also in the
/etc/network/interfaces file?
Thank you very much for your time and attention,
Regards,
Jordi
El 09/09/15 13:15, Harms, Hannes escribió:
> My wpa_supplicant config:
>
>
> ctrl_interface=DIR=/run/wpa_supplicant
> ap_scan=2
>
> network={
> ssid="test"
> bssid=02:12:34:56:78:9A
> key_mgmt=NONE
> mode=1
> frequency=5180
> disable_ht=0
> disable_vht=0
> disable_max_amsdu=1 # not sure, works also without this flag
> }
>
>
> Regards
> Hannes
>
> Am 09.09.2015 um 13:08 schrieb Jorge Baranda:
>> Hi,
>>
>> Good news!! Harms, could you share full wpa_supplicant configuration
>> files?
>> (for both computers).
>> I will download the latest version of wpa_supplicant, apply your
>> changes and try
>> to make work IBSS mode and 80MHz with Candela Kernel 4.0.
>>
>> Thanks,
>>
>> El 09/09/15 12:59, Harms, Hannes escribió:
>>> Hi,
>>>
>>> I have WLE900VX working in IBSS mode and 80 Mhz with Candela Kernel
>>> 4.2.
>>> For me also the latest wpa_supplicant was not able to activate 80MHz
>>> by default , I don't no why.
>>>
>>> The only way I found to get it working was to modify
>>> wpa_supplicant/wpa_supplicant.c
>>> Commit following two lines in wpa_supplicant.c like this :
>>>
>>> //if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
>>> // return;
>>>
>>> That was all for me to get it working.
>>>
>>> wpa_supplicant config file:
>>> # Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is
>>> ignored)
>>> CONFIG_LIBNL32=y
>>>
>>> # Support VHT overrides (disable VHT, mask MCS rates, etc.)
>>> CONFIG_VHT_OVERRIDES=y
>>>
>>> # Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
>>> CONFIG_HT_OVERRIDES=y
>>>
>>> # IEEE 802.11n (High Throughput) support (mainly for AP mode)
>>> CONFIG_IEEE80211N=y
>>>
>>> # IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
>>> # (depends on CONFIG_IEEE80211N)
>>> CONFIG_IEEE80211AC=y
>>>
>>> # IEEE 802.11w (management frame protection), also known as PMF
>>> # Driver support is also needed for IEEE 802.11w.
>>> CONFIG_IEEE80211W=y
>>>
>>> Am 09.09.2015 um 11:46 schrieb Marcel H.:
>>>> May I ask someone for support on this one?
>>>> We would really like to make this work and I'm running out of ideas -
>>>> is there any way do turn detailed debugging on to get a better
>>>> understanding why do I get the following message back? ->
>>>>
>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>> command failed: Device or resource busy (-16)
>>>>
>>>> Thanks,
>>>> Marcel
>>>>
>>>> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>>>>> Thanks for the response, unfortunately this is the result of defining
>>>>> the center frequency:
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>>> command failed: Device or resource busy (-16)
>>>>>
>>>>> Also, using wpa_supplicant does not work using the following config:
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>>>>> ap_scan=2
>>>>> ctrl_interface=/run/wpa_supplicant
>>>>> update_config=1
>>>>> device_type=0-00000000-0
>>>>>
>>>>> network={
>>>>> scan_ssid=1
>>>>> key_mgmt=NONE
>>>>> priority=1
>>>>> ssid="ibss"
>>>>> mode=1
>>>>> frequency=5180
>>>>> }
>>>>>
>>>>> running as:
>>>>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D
>>>>> nl80211,wext
>>>>>
>>>>>
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>>>>> Interface wlan0
>>>>> ifindex 5
>>>>> wdev 0x100000001
>>>>> addr 04:f0:21:1b:5f:3d
>>>>> ssid ibss-rsn
>>>>> type IBSS
>>>>> wiphy 1
>>>>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>>>>> Wiphy phy1
>>>>> DFS state: usable (for 46424 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>>>> detection)
>>>>> DFS state: usable (for 46424 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>>>> detection)
>>>>> DFS state: usable (for 46424 sec)
>>>>> DFS CAC time: 60000 ms
>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>>>> detection)
>>>>> DFS state: usable (for 46424 sec)
>>>>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>>>>> channels set manually by iw
>>>>>
>>>>>
>>>>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>>>> wpa_supplicant v2.3
>>>>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>>>>
>>>>>
>>>>> Re. the regulatory settings:
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw reg get
>>>>> country US: DFS-FCC
>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>
>>>>>
>>>>> Any other thoughts?
>>>>>
>>>>> Marcel
>>>>>
>>>>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>>>>> <janusz.dziedzic@tieto.com> wrote:
>>>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es>
>>>>>> wrote:
>>>>>>> Hi everyone,
>>>>>>>
>>>>>>> Reading this thread, I would like to share with people some
>>>>>>> doubts about it.
>>>>>>> @Marco, I imagine you want to run your WLE600VX device using the
>>>>>>> 802.11ac
>>>>>>> protocol, isn't it?
>>>>>>> @Janusz, with running wpa_supplicant on both computers, will the
>>>>>>> ad-hoc
>>>>>>> connection be established? I am starting with these tools and
>>>>>>> now, I am
>>>>>>> getting used to know how they work. I was creating the ad-hoc
>>>>>>> connection
>>>>>>> with the iw tool.
>>>>>>>
>>>>>> Yes you should use wpa_supplicant on both PC.
>>>>>> In the future probably someone will add IBSS-VHT support also for
>>>>>> iw.
>>>>>>
>>>>>> BR
>>>>>> Janusz
>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>>>>
>>>>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>>>> Hi everyone,
>>>>>>>>> I have an interesting issue - I'm trying to run the QCA9882
>>>>>>>>> based card
>>>>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is
>>>>>>>>> to run
>>>>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run
>>>>>>>>> it in
>>>>>>>>> 80MHz width resolves in the following:
>>>>>>>>>
>>>>>>>> You should run IBSS using fresh wpa_supplicant (best latest
>>>>>>>> code). By
>>>>>>>> default should run in 80MHz.
>>>>>>>> Other case is your regulatory - are you allow to use 80MHz on
>>>>>>>> channel
>>>>>>>> 157? First try 5180.
>>>>>>>>
>>>>>>>> eg. of wpa_supplicant config:
>>>>>>>>
>>>>>>>> network = {
>>>>>>>> ssid="test_ibss"
>>>>>>>> key_mgmt=NONE
>>>>>>>> mode=1
>>>>>>>> frequency=5180
>>>>>>>> }
>>>>>>>>
>>>>>>>> BR
>>>>>>>> Janusz
>>>>>>>>
>>>>>>>>> Interface wlan0
>>>>>>>>> ifindex 5
>>>>>>>>> wdev 0x1
>>>>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>>>>> ssid my-mesh-network
>>>>>>>>> type IBSS
>>>>>>>>> wiphy 0
>>>>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> More info:
>>>>>>>>> =====================================================
>>>>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac
>>>>>>>>> Wireless
>>>>>>>>> Network Adapter
>>>>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>>>>> Capabilities: [40] Power Management version 2
>>>>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>>>>> Capabilities: [140] Virtual Channel
>>>>>>>>> Capabilities: [160] Device Serial Number
>>>>>>>>> 00-00-00-00-00-00-00-00
>>>>>>>>> Kernel driver in use: ath10k_pci
>>>>>>>>>
>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>>>>> country US: DFS-FCC
>>>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8
>>>>>>>>> 14:03:33
>>>>>>>>> GMT 2015 i686 GNU/Linux
>>>>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage
>>>>>>>>> Linux 0.10
>>>>>>>>> .config)
>>>>>>>>>
>>>>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum
>>>>>>>>> ./firmware-2.bin
>>>>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>>>>> (this is from the 'main' directory in the
>>>>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Wiphy phy0
>>>>>>>>> max # scan SSIDs: 16
>>>>>>>>> max scan IEs length: 195 bytes
>>>>>>>>> Retry short limit: 7
>>>>>>>>> Retry long limit: 4
>>>>>>>>> Coverage class: 0 (up to 0m)
>>>>>>>>> Device supports RSN-IBSS.
>>>>>>>>> Device supports AP-side u-APSD.
>>>>>>>>> Supported Ciphers:
>>>>>>>>> * WEP40 (00-0f-ac:1)
>>>>>>>>> * WEP104 (00-0f-ac:5)
>>>>>>>>> * TKIP (00-0f-ac:2)
>>>>>>>>> * CCMP (00-0f-ac:4)
>>>>>>>>> * CMAC (00-0f-ac:6)
>>>>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>>>>> Supported interface modes:
>>>>>>>>> * IBSS
>>>>>>>>> * managed
>>>>>>>>> * AP
>>>>>>>>> * AP/VLAN
>>>>>>>>> * monitor
>>>>>>>>> * P2P-client
>>>>>>>>> * P2P-GO
>>>>>>>>> * P2P-device
>>>>>>>>> Band 1:
>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>> RX LDPC
>>>>>>>>> HT20/HT40
>>>>>>>>> Static SM Power Save
>>>>>>>>> RX HT20 SGI
>>>>>>>>> RX HT40 SGI
>>>>>>>>> TX STBC
>>>>>>>>> RX STBC 1-stream
>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>> DSSS/CCK HT40
>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>> Max MPDU length: 11454
>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>> RX LDPC
>>>>>>>>> short GI (80 MHz)
>>>>>>>>> TX STBC
>>>>>>>>> RX antenna pattern consistency
>>>>>>>>> TX antenna pattern consistency
>>>>>>>>> VHT RX MCS set:
>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>> 3 streams: not supported
>>>>>>>>> 4 streams: not supported
>>>>>>>>> 5 streams: not supported
>>>>>>>>> 6 streams: not supported
>>>>>>>>> 7 streams: not supported
>>>>>>>>> 8 streams: not supported
>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>> VHT TX MCS set:
>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>> 3 streams: not supported
>>>>>>>>> 4 streams: not supported
>>>>>>>>> 5 streams: not supported
>>>>>>>>> 6 streams: not supported
>>>>>>>>> 7 streams: not supported
>>>>>>>>> 8 streams: not supported
>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>> Bitrates (non-HT):
>>>>>>>>> * 1.0 Mbps
>>>>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>>>>> * 6.0 Mbps
>>>>>>>>> * 9.0 Mbps
>>>>>>>>> * 12.0 Mbps
>>>>>>>>> * 18.0 Mbps
>>>>>>>>> * 24.0 Mbps
>>>>>>>>> * 36.0 Mbps
>>>>>>>>> * 48.0 Mbps
>>>>>>>>> * 54.0 Mbps
>>>>>>>>> Frequencies:
>>>>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>>>>> * 2467 MHz [12] (disabled)
>>>>>>>>> * 2472 MHz [13] (disabled)
>>>>>>>>> * 2484 MHz [14] (disabled)
>>>>>>>>> Band 2:
>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>> RX LDPC
>>>>>>>>> HT20/HT40
>>>>>>>>> Static SM Power Save
>>>>>>>>> RX HT20 SGI
>>>>>>>>> RX HT40 SGI
>>>>>>>>> TX STBC
>>>>>>>>> RX STBC 1-stream
>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>> DSSS/CCK HT40
>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>> Max MPDU length: 11454
>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>> RX LDPC
>>>>>>>>> short GI (80 MHz)
>>>>>>>>> TX STBC
>>>>>>>>> RX antenna pattern consistency
>>>>>>>>> TX antenna pattern consistency
>>>>>>>>> VHT RX MCS set:
>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>> 3 streams: not supported
>>>>>>>>> 4 streams: not supported
>>>>>>>>> 5 streams: not supported
>>>>>>>>> 6 streams: not supported
>>>>>>>>> 7 streams: not supported
>>>>>>>>> 8 streams: not supported
>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>> VHT TX MCS set:
>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>> 3 streams: not supported
>>>>>>>>> 4 streams: not supported
>>>>>>>>> 5 streams: not supported
>>>>>>>>> 6 streams: not supported
>>>>>>>>> 7 streams: not supported
>>>>>>>>> 8 streams: not supported
>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>> Bitrates (non-HT):
>>>>>>>>> * 6.0 Mbps
>>>>>>>>> * 9.0 Mbps
>>>>>>>>> * 12.0 Mbps
>>>>>>>>> * 18.0 Mbps
>>>>>>>>> * 24.0 Mbps
>>>>>>>>> * 36.0 Mbps
>>>>>>>>> * 48.0 Mbps
>>>>>>>>> * 54.0 Mbps
>>>>>>>>> Frequencies:
>>>>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>>>>> Supported commands:
>>>>>>>>> * new_interface
>>>>>>>>> * set_interface
>>>>>>>>> * new_key
>>>>>>>>> * start_ap
>>>>>>>>> * new_station
>>>>>>>>> * set_bss
>>>>>>>>> * authenticate
>>>>>>>>> * associate
>>>>>>>>> * deauthenticate
>>>>>>>>> * disassociate
>>>>>>>>> * join_ibss
>>>>>>>>> * remain_on_channel
>>>>>>>>> * set_tx_bitrate_mask
>>>>>>>>> * frame
>>>>>>>>> * frame_wait_cancel
>>>>>>>>> * set_wiphy_netns
>>>>>>>>> * set_channel
>>>>>>>>> * set_wds_peer
>>>>>>>>> * probe_client
>>>>>>>>> * set_noack_map
>>>>>>>>> * register_beacons
>>>>>>>>> * start_p2p_device
>>>>>>>>> * set_mcast_rate
>>>>>>>>> * testmode
>>>>>>>>> * channel_switch
>>>>>>>>> * Unknown command (104)
>>>>>>>>> * connect
>>>>>>>>> * disconnect
>>>>>>>>> Supported TX frame types:
>>>>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>> 0x80 0x90
>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>> 0x80 0x90
>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>> 0x90 0xa0
>>>>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>> 0x80 0x90
>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>>> 0x70 0x80
>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>>> 0x70 0x80
>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>> 0x80 0x90
>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>>> 0x70 0x80
>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>> Supported RX frame types:
>>>>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>>>>> * managed: 0x40 0xd0
>>>>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>>>>> * P2P-client: 0x40 0xd0
>>>>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>> * P2P-device: 0x40 0xd0
>>>>>>>>> software interface modes (can always be added):
>>>>>>>>> * AP/VLAN
>>>>>>>>> * monitor
>>>>>>>>> valid interface combinations:
>>>>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>>>>> HT Capability overrides:
>>>>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>>>>> * maximum A-MSDU length
>>>>>>>>> * supported channel width
>>>>>>>>> * short GI for 40 MHz
>>>>>>>>> * max A-MPDU length exponent
>>>>>>>>> * min MPDU start spacing
>>>>>>>>> Device supports TX status socket option.
>>>>>>>>> Device supports HT-IBSS.
>>>>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>>>>> Device supports scan flush.
>>>>>>>>> Device supports per-vif TX power setting
>>>>>>>>> Driver supports a userspace MPM
>>>>>>>>> Driver/device bandwidth changes during BSS lifetime
>>>>>>>>> (AP/GO mode)
>>>>>>>>> Device supports static SMPS
>>>>>>>>> =====================================================
>>>>>>>>>
>>>>>>>>> I am grateful for any help here and do have some time to help
>>>>>>>>> debugging the issue.
>>>>>>>>>
>>>>>>>>> Marcel
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------
>>>>>>>>> This message is not intended to have
>>>>>>>>> contractual effect
>>>>>>>>> ------------------------------------------------------
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jorge Baranda
>>>>>>> Research Engineer, MSc
>>>>>>> jorge.baranda@cttc.es
>>>>>>>
>>>>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>>>>> Av. Carl Friedrich Gauss, 7
>>>>>>> 08860 Castelldefels, Barcelona (Spain)
>>>>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>>>>> Fax. +34 93 645 29 01
>>>>>>> www.cttc.es
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> ------------------------------------------------------
>>>>> This message is not intended to have
>>>>> contractual effect
>>>>> ------------------------------------------------------
>>>>
>>>>
>>>
>>
>>
>
--
Jorge Baranda
Research Engineer, MSc
jorge.baranda@cttc.es
Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
Av. Carl Friedrich Gauss, 7
08860 Castelldefels, Barcelona (Spain)
Tel: +34 93 645 29 00 Ext: 2171
Fax. +34 93 645 29 01
www.cttc.es
[-- Attachment #2: wpa_supplicant.log --]
[-- Type: text/x-log, Size: 5465 bytes --]
wpa_supplicant v2.4
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan3' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='DIR=/run/wpa_supplicant'
ctrl_interface_group='wheel'
ap_scan=2
Priority group 0
id=0 ssid='test'
rfkill: initial event: idx=0 type=2 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=2 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=3 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=4 type=1 op=0 soft=0 hard=0
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:6
nl80211: Using driver-based off-channel TX
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: use P2P_DEVICE support
nl80211: interface wlan3 in phy phy3
nl80211: Set mode ifindex 7 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0x16fc2a0
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fc2a0 match=0801
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 08 01
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fc2a0 match=06
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=1): 06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fc2a0 match=0a07
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fc2a0 match=0a11
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fc2a0 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fc2a0 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x16fc2a0 match=0505
nl80211: Failed to register Action frame processing - ignore for now
netlink: Operstate: ifindex=7 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
nl80211: driver param='(null)'
Add interface wlan3 to a new radio phy3
nl80211: Regulatory information - country=98 (DFS-FCC)
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 5170-5250 @ 80 MHz 17 mBm (no outdoor)
nl80211: 5250-5330 @ 80 MHz 20 mBm (no outdoor) (DFS)
nl80211: 5490-5725 @ 160 MHz 23 mBm (DFS)
nl80211: 57240-63720 @ 2160 MHz 40 mBm
nl80211: Added 802.11b mode based on 802.11g information
wlan3: Own MAC address: 04:f0:21:18:24:71
wpa_driver_nl80211_set_key: ifindex=7 (wlan3) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=7 (wlan3) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=7 (wlan3) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=7 (wlan3) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=7 (wlan3) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=7 (wlan3) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0
wlan3: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlan3: Setting scan request: 0.100000 sec
ENGINE: Loading dynamic engine
ENGINE: Loading dynamic engine
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Using existing control interface directory.
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists and seems to be in use - cannot override it
Delete '/run/wpa_supplicant/wlan3' manually if it is not used anymore
Failed to initialize control interface 'DIR=/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.
Failed to add interface wlan3
wlan3: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 state=DISCONNECTED
wlan3: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlan3 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=7 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wlan3: WPA: Clear old PMK and PTK
wlan3: Cancelling scan request
wlan3: Cancelling authentication timeout
Remove interface wlan3 from radio phy3
Remove radio phy3
nl80211: deinit ifname=wlan3 disabled_11b_rates=0
nl80211: Remove monitor interface: refcount=0
netlink: Operstate: ifindex=7 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 7 iftype 2 (STATION)
nl80211: Unsubscribe mgmt frames handle 0x8888888889e74a29 (mode change)
[-- Attachment #3: wpa_supplicant2.log --]
[-- Type: text/x-log, Size: 3795 bytes --]
wlan3: State: DISCONNECTED -> SCANNING
wlan3: Re-association to the same ESS
wlan3: Add radio work 'connect'@0x1da10d0
wlan3: First radio work item in the queue - schedule start immediately
wlan3: Starting radio work 'connect'@0x1da10d0 after 0.000010 second wait
wlan3: Trying to associate with SSID 'test'
wlan3: Cancelling scan request
wlan3: WPA: clearing own WPA/RSN IE
wlan3: Automatic auth_alg selection: 0x1
wlan3: WPA: clearing AP WPA IE
wlan3: WPA: clearing AP RSN IE
wlan3: WPA: clearing own WPA/RSN IE
wlan3: State: SCANNING -> ASSOCIATING
nl80211: Set wlan3 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=7 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
nl80211: Received scan results (11 BSSes)
wlan3: BSS: Start scan result update 6
IBSS/mesh: setup freq channel 36, sec_channel_offset 1
IBSS: VHT setup freq cf1 5210, cf2 0, bw 80
wlan3: set_disable_max_amsdu: 1
wlan3: set_ampdu_factor: -1
wlan3: set_ampdu_density: -1
wlan3: set_disable_ht40: 0
wlan3: set_disable_sgi: 0
wlan3: set_disable_ldpc: 0
nl80211: Join IBSS (ifindex=7)
nl80211: Set mode ifindex 7 iftype 1 (ADHOC)
nl80211: Unsubscribe mgmt frames handle 0x888888888950ba29 (mode change)
nl80211: Subscribe to mgmt frames with non-AP handle 0x1d832a0
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x1d832a0 match=
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1d832a0 match=0801
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 08 01
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1d832a0 match=06
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=1): 06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1d832a0 match=0a07
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1d832a0 match=0a11
nl80211: Register frame command failed (type=208): ret=-114 (Operation already in progress)
nl80211: Register frame match - hexdump(len=2): 0a 11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1d832a0 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1d832a0 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1d832a0 match=0505
nl80211: Failed to register Action frame processing - ignore for now
* SSID - hexdump_ascii(len=4):
74 65 73 74 test
* freq=5180
* vht_enabled=1
* ht_enabled=1
* bandwidth=80
* channel_width=3
* center_freq1=5210
* center_freq2=0
* BSSID=02:12:34:56:78:9a
* Extra IEs for Beacon/Probe Response frames - hexdump(len=10): 7f 08 00 00 00 00 00 00 00 40
* htcaps - hexdump(len=26): 63 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* htcaps_mask - hexdump(len=26): 63 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps_mask - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
nl80211: Join IBSS failed: ret=-22 (Invalid argument)
wlan3: Association request to the driver failed
wlan3: Radio work 'connect'@0x1da10d0 done in 0.000498 seconds
BSSID 00:00:00:00:00:00 blacklist count incremented to 5
wlan3: Blacklist count 5 --> request scan in 10000 ms
wlan3: Setting scan request: 10.000000 sec
wlan3: State: ASSOCIATING -> DISCONNECTED
nl80211: Set wlan3 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=7 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
[-- Attachment #4: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-17 10:27 ` [SPAM] " Jorge Baranda
@ 2015-09-17 15:39 ` Jorge Baranda
2015-09-17 16:02 ` Marcel H.
2015-09-17 16:11 ` Ben Greear
0 siblings, 2 replies; 22+ messages in thread
From: Jorge Baranda @ 2015-09-17 15:39 UTC (permalink / raw)
To: ath10k, Marcel H.
[-- Attachment #1: Type: text/plain, Size: 26917 bytes --]
Dear Marcel and all,
I have also followed your setup for trying to configure the
wpa_supplicant program to setup a 80MHz link but it has not been possible.
After downloading the last version of wpa_supplicant with git (version
2.5), and using your wpa_supplicant.conf file, the link was not possible
to be setup (the log file is attached) .
It results that nl80211 driver is not compatible with ap_scan=2 option.
If using ap_scan=1, the result is the same.
I have to use the wext driver to establish the link but it is a 20Mhz
link . The output of iw dev wlan2 info is:
Interface wlan2
ifindex 6
wdev 0x200000001
addr 04:f0:21:18:24:71
ssid SC224SC225
type IBSS
wiphy 2
channel 36 (5180 MHz), width: 20 MHz (no HT), center1: 5180 MHz
Anyone faced the same problem?
Maybe is not possible to setup the 80MHz link with the Candela Kernel 4.0.
Thank you very much in advance for your time and attention,
Regards,
Jordi
El 17/09/15 12:27, Jorge Baranda escribió:
> Dear Hannes and all,
>
> I have tried to replicate Hannes' setup to make work wpa_supplicant
> with Candela Kernel 4.0 (and Candela firmware 10.1.467-ct-14), but I
> have not been successful.
> I downloaded the last version of wpa_supplicant from
> http://w1.fi/wpa_supplicant/ website, applied your changes in the
> wpa_supplicant.c file and your .config file.
> Then I used your wpa_supplicant.conf file but it failed to start
> (attached the full log). The error says that "the ctrl_interface
> exists and seems to be in use"
>
> I have checked with ps aux to see if there is a wpa_supplicant process
> but after kill it, it restarts again.
> This is the result of ps aux | grep wpa_supplicant:
>
> root 2368 0.0 0.0 30868 6140 ? Ss 11:40 0:00
> /sbin/wpa_supplicant -u -s -O /var/run/wpa_supplicant
> monet 2690 0.0 0.0 13688 2372 pts/9 S+ 12:10 0:00 grep
> --color=auto wpa_supplicant
>
> Browsing in the internet I have not found any answer to solve this
> problem :(. Have you faced it?
>
> Then I have tried removing the "ctrl_interface line" from the
> wpa_supplicant.conf file (resulting in a file similar to the one sent
> by Marcel H.) and the program started in a loop (see attached
> wpa_supplicant2.log). It seems like it tries to connect to the ssid
> "test" but it is not able to find it (normal, because we want to
> create it).
>
> Apart from this, in this setup, do I have to make any change also in
> the /etc/network/interfaces file?
>
> Thank you very much for your time and attention,
>
> Regards,
>
> Jordi
>
>
>
> El 09/09/15 13:15, Harms, Hannes escribió:
>> My wpa_supplicant config:
>>
>>
>> ctrl_interface=DIR=/run/wpa_supplicant
>> ap_scan=2
>>
>> network={
>> ssid="test"
>> bssid=02:12:34:56:78:9A
>> key_mgmt=NONE
>> mode=1
>> frequency=5180
>> disable_ht=0
>> disable_vht=0
>> disable_max_amsdu=1 # not sure, works also without this flag
>> }
>>
>>
>> Regards
>> Hannes
>>
>> Am 09.09.2015 um 13:08 schrieb Jorge Baranda:
>>> Hi,
>>>
>>> Good news!! Harms, could you share full wpa_supplicant configuration
>>> files?
>>> (for both computers).
>>> I will download the latest version of wpa_supplicant, apply your
>>> changes and try
>>> to make work IBSS mode and 80MHz with Candela Kernel 4.0.
>>>
>>> Thanks,
>>>
>>> El 09/09/15 12:59, Harms, Hannes escribió:
>>>> Hi,
>>>>
>>>> I have WLE900VX working in IBSS mode and 80 Mhz with Candela
>>>> Kernel 4.2.
>>>> For me also the latest wpa_supplicant was not able to activate
>>>> 80MHz by default , I don't no why.
>>>>
>>>> The only way I found to get it working was to modify
>>>> wpa_supplicant/wpa_supplicant.c
>>>> Commit following two lines in wpa_supplicant.c like this :
>>>>
>>>> //if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
>>>> // return;
>>>>
>>>> That was all for me to get it working.
>>>>
>>>> wpa_supplicant config file:
>>>> # Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is
>>>> ignored)
>>>> CONFIG_LIBNL32=y
>>>>
>>>> # Support VHT overrides (disable VHT, mask MCS rates, etc.)
>>>> CONFIG_VHT_OVERRIDES=y
>>>>
>>>> # Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
>>>> CONFIG_HT_OVERRIDES=y
>>>>
>>>> # IEEE 802.11n (High Throughput) support (mainly for AP mode)
>>>> CONFIG_IEEE80211N=y
>>>>
>>>> # IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
>>>> # (depends on CONFIG_IEEE80211N)
>>>> CONFIG_IEEE80211AC=y
>>>>
>>>> # IEEE 802.11w (management frame protection), also known as PMF
>>>> # Driver support is also needed for IEEE 802.11w.
>>>> CONFIG_IEEE80211W=y
>>>>
>>>> Am 09.09.2015 um 11:46 schrieb Marcel H.:
>>>>> May I ask someone for support on this one?
>>>>> We would really like to make this work and I'm running out of ideas -
>>>>> is there any way do turn detailed debugging on to get a better
>>>>> understanding why do I get the following message back? ->
>>>>>
>>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>>> command failed: Device or resource busy (-16)
>>>>>
>>>>> Thanks,
>>>>> Marcel
>>>>>
>>>>> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>>>>>> Thanks for the response, unfortunately this is the result of
>>>>>> defining
>>>>>> the center frequency:
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>>>> command failed: Device or resource busy (-16)
>>>>>>
>>>>>> Also, using wpa_supplicant does not work using the following config:
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>>>>>> ap_scan=2
>>>>>> ctrl_interface=/run/wpa_supplicant
>>>>>> update_config=1
>>>>>> device_type=0-00000000-0
>>>>>>
>>>>>> network={
>>>>>> scan_ssid=1
>>>>>> key_mgmt=NONE
>>>>>> priority=1
>>>>>> ssid="ibss"
>>>>>> mode=1
>>>>>> frequency=5180
>>>>>> }
>>>>>>
>>>>>> running as:
>>>>>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D
>>>>>> nl80211,wext
>>>>>>
>>>>>>
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>>>>>> Interface wlan0
>>>>>> ifindex 5
>>>>>> wdev 0x100000001
>>>>>> addr 04:f0:21:1b:5f:3d
>>>>>> ssid ibss-rsn
>>>>>> type IBSS
>>>>>> wiphy 1
>>>>>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>>>>>> Wiphy phy1
>>>>>> DFS state: usable (for 46424 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>>>>> detection)
>>>>>> DFS state: usable (for 46424 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>>>>> detection)
>>>>>> DFS state: usable (for 46424 sec)
>>>>>> DFS CAC time: 60000 ms
>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>>>>> detection)
>>>>>> DFS state: usable (for 46424 sec)
>>>>>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>>>>>> channels set manually by iw
>>>>>>
>>>>>>
>>>>>> How recent wpa_supplicat shall I try? I believe this it quite
>>>>>> recent:
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>>>>> wpa_supplicant v2.3
>>>>>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>>>>>
>>>>>>
>>>>>> Re. the regulatory settings:
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw reg get
>>>>>> country US: DFS-FCC
>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>
>>>>>>
>>>>>> Any other thoughts?
>>>>>>
>>>>>> Marcel
>>>>>>
>>>>>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>>>>>> <janusz.dziedzic@tieto.com> wrote:
>>>>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es>
>>>>>>> wrote:
>>>>>>>> Hi everyone,
>>>>>>>>
>>>>>>>> Reading this thread, I would like to share with people some
>>>>>>>> doubts about it.
>>>>>>>> @Marco, I imagine you want to run your WLE600VX device using
>>>>>>>> the 802.11ac
>>>>>>>> protocol, isn't it?
>>>>>>>> @Janusz, with running wpa_supplicant on both computers, will
>>>>>>>> the ad-hoc
>>>>>>>> connection be established? I am starting with these tools and
>>>>>>>> now, I am
>>>>>>>> getting used to know how they work. I was creating the ad-hoc
>>>>>>>> connection
>>>>>>>> with the iw tool.
>>>>>>>>
>>>>>>> Yes you should use wpa_supplicant on both PC.
>>>>>>> In the future probably someone will add IBSS-VHT support also
>>>>>>> for iw.
>>>>>>>
>>>>>>> BR
>>>>>>> Janusz
>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>>>>>
>>>>>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>>>>> Hi everyone,
>>>>>>>>>> I have an interesting issue - I'm trying to run the QCA9882
>>>>>>>>>> based card
>>>>>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is
>>>>>>>>>> to run
>>>>>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to
>>>>>>>>>> run it in
>>>>>>>>>> 80MHz width resolves in the following:
>>>>>>>>>>
>>>>>>>>> You should run IBSS using fresh wpa_supplicant (best latest
>>>>>>>>> code). By
>>>>>>>>> default should run in 80MHz.
>>>>>>>>> Other case is your regulatory - are you allow to use 80MHz on
>>>>>>>>> channel
>>>>>>>>> 157? First try 5180.
>>>>>>>>>
>>>>>>>>> eg. of wpa_supplicant config:
>>>>>>>>>
>>>>>>>>> network = {
>>>>>>>>> ssid="test_ibss"
>>>>>>>>> key_mgmt=NONE
>>>>>>>>> mode=1
>>>>>>>>> frequency=5180
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> BR
>>>>>>>>> Janusz
>>>>>>>>>
>>>>>>>>>> Interface wlan0
>>>>>>>>>> ifindex 5
>>>>>>>>>> wdev 0x1
>>>>>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>>>>>> ssid my-mesh-network
>>>>>>>>>> type IBSS
>>>>>>>>>> wiphy 0
>>>>>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> More info:
>>>>>>>>>> =====================================================
>>>>>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac
>>>>>>>>>> Wireless
>>>>>>>>>> Network Adapter
>>>>>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>>>>>> Capabilities: [40] Power Management version 2
>>>>>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>>>>>> Capabilities: [140] Virtual Channel
>>>>>>>>>> Capabilities: [160] Device Serial Number
>>>>>>>>>> 00-00-00-00-00-00-00-00
>>>>>>>>>> Kernel driver in use: ath10k_pci
>>>>>>>>>>
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>>>>>> country US: DFS-FCC
>>>>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8
>>>>>>>>>> 14:03:33
>>>>>>>>>> GMT 2015 i686 GNU/Linux
>>>>>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage
>>>>>>>>>> Linux 0.10
>>>>>>>>>> .config)
>>>>>>>>>>
>>>>>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum
>>>>>>>>>> ./firmware-2.bin
>>>>>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>>>>>> (this is from the 'main' directory in the
>>>>>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Wiphy phy0
>>>>>>>>>> max # scan SSIDs: 16
>>>>>>>>>> max scan IEs length: 195 bytes
>>>>>>>>>> Retry short limit: 7
>>>>>>>>>> Retry long limit: 4
>>>>>>>>>> Coverage class: 0 (up to 0m)
>>>>>>>>>> Device supports RSN-IBSS.
>>>>>>>>>> Device supports AP-side u-APSD.
>>>>>>>>>> Supported Ciphers:
>>>>>>>>>> * WEP40 (00-0f-ac:1)
>>>>>>>>>> * WEP104 (00-0f-ac:5)
>>>>>>>>>> * TKIP (00-0f-ac:2)
>>>>>>>>>> * CCMP (00-0f-ac:4)
>>>>>>>>>> * CMAC (00-0f-ac:6)
>>>>>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>>>>>> Supported interface modes:
>>>>>>>>>> * IBSS
>>>>>>>>>> * managed
>>>>>>>>>> * AP
>>>>>>>>>> * AP/VLAN
>>>>>>>>>> * monitor
>>>>>>>>>> * P2P-client
>>>>>>>>>> * P2P-GO
>>>>>>>>>> * P2P-device
>>>>>>>>>> Band 1:
>>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>>> RX LDPC
>>>>>>>>>> HT20/HT40
>>>>>>>>>> Static SM Power Save
>>>>>>>>>> RX HT20 SGI
>>>>>>>>>> RX HT40 SGI
>>>>>>>>>> TX STBC
>>>>>>>>>> RX STBC 1-stream
>>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>>> DSSS/CCK HT40
>>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>>> Max MPDU length: 11454
>>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>>> RX LDPC
>>>>>>>>>> short GI (80 MHz)
>>>>>>>>>> TX STBC
>>>>>>>>>> RX antenna pattern consistency
>>>>>>>>>> TX antenna pattern consistency
>>>>>>>>>> VHT RX MCS set:
>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>> 3 streams: not supported
>>>>>>>>>> 4 streams: not supported
>>>>>>>>>> 5 streams: not supported
>>>>>>>>>> 6 streams: not supported
>>>>>>>>>> 7 streams: not supported
>>>>>>>>>> 8 streams: not supported
>>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>>> VHT TX MCS set:
>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>> 3 streams: not supported
>>>>>>>>>> 4 streams: not supported
>>>>>>>>>> 5 streams: not supported
>>>>>>>>>> 6 streams: not supported
>>>>>>>>>> 7 streams: not supported
>>>>>>>>>> 8 streams: not supported
>>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>>> Bitrates (non-HT):
>>>>>>>>>> * 1.0 Mbps
>>>>>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>>>>>> * 6.0 Mbps
>>>>>>>>>> * 9.0 Mbps
>>>>>>>>>> * 12.0 Mbps
>>>>>>>>>> * 18.0 Mbps
>>>>>>>>>> * 24.0 Mbps
>>>>>>>>>> * 36.0 Mbps
>>>>>>>>>> * 48.0 Mbps
>>>>>>>>>> * 54.0 Mbps
>>>>>>>>>> Frequencies:
>>>>>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>>>>>> * 2467 MHz [12] (disabled)
>>>>>>>>>> * 2472 MHz [13] (disabled)
>>>>>>>>>> * 2484 MHz [14] (disabled)
>>>>>>>>>> Band 2:
>>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>>> RX LDPC
>>>>>>>>>> HT20/HT40
>>>>>>>>>> Static SM Power Save
>>>>>>>>>> RX HT20 SGI
>>>>>>>>>> RX HT40 SGI
>>>>>>>>>> TX STBC
>>>>>>>>>> RX STBC 1-stream
>>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>>> DSSS/CCK HT40
>>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>>> Max MPDU length: 11454
>>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>>> RX LDPC
>>>>>>>>>> short GI (80 MHz)
>>>>>>>>>> TX STBC
>>>>>>>>>> RX antenna pattern consistency
>>>>>>>>>> TX antenna pattern consistency
>>>>>>>>>> VHT RX MCS set:
>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>> 3 streams: not supported
>>>>>>>>>> 4 streams: not supported
>>>>>>>>>> 5 streams: not supported
>>>>>>>>>> 6 streams: not supported
>>>>>>>>>> 7 streams: not supported
>>>>>>>>>> 8 streams: not supported
>>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>>> VHT TX MCS set:
>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>> 3 streams: not supported
>>>>>>>>>> 4 streams: not supported
>>>>>>>>>> 5 streams: not supported
>>>>>>>>>> 6 streams: not supported
>>>>>>>>>> 7 streams: not supported
>>>>>>>>>> 8 streams: not supported
>>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>>> Bitrates (non-HT):
>>>>>>>>>> * 6.0 Mbps
>>>>>>>>>> * 9.0 Mbps
>>>>>>>>>> * 12.0 Mbps
>>>>>>>>>> * 18.0 Mbps
>>>>>>>>>> * 24.0 Mbps
>>>>>>>>>> * 36.0 Mbps
>>>>>>>>>> * 48.0 Mbps
>>>>>>>>>> * 54.0 Mbps
>>>>>>>>>> Frequencies:
>>>>>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar
>>>>>>>>>> detection)
>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>>>>>>>>> detection)
>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>>>>>>>>> detection)
>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>>>>>>>>> detection)
>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>>>>>> Supported commands:
>>>>>>>>>> * new_interface
>>>>>>>>>> * set_interface
>>>>>>>>>> * new_key
>>>>>>>>>> * start_ap
>>>>>>>>>> * new_station
>>>>>>>>>> * set_bss
>>>>>>>>>> * authenticate
>>>>>>>>>> * associate
>>>>>>>>>> * deauthenticate
>>>>>>>>>> * disassociate
>>>>>>>>>> * join_ibss
>>>>>>>>>> * remain_on_channel
>>>>>>>>>> * set_tx_bitrate_mask
>>>>>>>>>> * frame
>>>>>>>>>> * frame_wait_cancel
>>>>>>>>>> * set_wiphy_netns
>>>>>>>>>> * set_channel
>>>>>>>>>> * set_wds_peer
>>>>>>>>>> * probe_client
>>>>>>>>>> * set_noack_map
>>>>>>>>>> * register_beacons
>>>>>>>>>> * start_p2p_device
>>>>>>>>>> * set_mcast_rate
>>>>>>>>>> * testmode
>>>>>>>>>> * channel_switch
>>>>>>>>>> * Unknown command (104)
>>>>>>>>>> * connect
>>>>>>>>>> * disconnect
>>>>>>>>>> Supported TX frame types:
>>>>>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>> 0x80 0x90
>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>> 0x80 0x90
>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>>> 0x90 0xa0
>>>>>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>> 0x80 0x90
>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>>>> 0x70 0x80
>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>>>> 0x70 0x80
>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>> 0x80 0x90
>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60
>>>>>>>>>> 0x70 0x80
>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>> Supported RX frame types:
>>>>>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>>>>>> * managed: 0x40 0xd0
>>>>>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>>>>>> * P2P-client: 0x40 0xd0
>>>>>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>> * P2P-device: 0x40 0xd0
>>>>>>>>>> software interface modes (can always be added):
>>>>>>>>>> * AP/VLAN
>>>>>>>>>> * monitor
>>>>>>>>>> valid interface combinations:
>>>>>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>>>>>> HT Capability overrides:
>>>>>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>>>>>> * maximum A-MSDU length
>>>>>>>>>> * supported channel width
>>>>>>>>>> * short GI for 40 MHz
>>>>>>>>>> * max A-MPDU length exponent
>>>>>>>>>> * min MPDU start spacing
>>>>>>>>>> Device supports TX status socket option.
>>>>>>>>>> Device supports HT-IBSS.
>>>>>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>>>>>> Device supports scan flush.
>>>>>>>>>> Device supports per-vif TX power setting
>>>>>>>>>> Driver supports a userspace MPM
>>>>>>>>>> Driver/device bandwidth changes during BSS lifetime
>>>>>>>>>> (AP/GO mode)
>>>>>>>>>> Device supports static SMPS
>>>>>>>>>> =====================================================
>>>>>>>>>>
>>>>>>>>>> I am grateful for any help here and do have some time to help
>>>>>>>>>> debugging the issue.
>>>>>>>>>>
>>>>>>>>>> Marcel
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------
>>>>>>>>>> This message is not intended to have
>>>>>>>>>> contractual effect
>>>>>>>>>> ------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> 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
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jorge Baranda
>>>>>>>> Research Engineer, MSc
>>>>>>>> jorge.baranda@cttc.es
>>>>>>>>
>>>>>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>>>>>> Av. Carl Friedrich Gauss, 7
>>>>>>>> 08860 Castelldefels, Barcelona (Spain)
>>>>>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>>>>>> Fax. +34 93 645 29 01
>>>>>>>> www.cttc.es
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> 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
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> ------------------------------------------------------
>>>>>> This message is not intended to have
>>>>>> contractual effect
>>>>>> ------------------------------------------------------
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
--
Jorge Baranda
Research Engineer, MSc
jorge.baranda@cttc.es
Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
Av. Carl Friedrich Gauss, 7
08860 Castelldefels, Barcelona (Spain)
Tel: +34 93 645 29 00 Ext: 2171
Fax. +34 93 645 29 01
www.cttc.es
[-- Attachment #2: wpa_supplicant.log --]
[-- Type: text/x-log, Size: 26073 bytes --]
wpa_supplicant v2.5-devel
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan2' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='DIR=/run/wpa_supplicant'
ctrl_interface_group='wheel'
ap_scan=2
Priority group 0
id=0 ssid='SC224SC225'
rfkill: initial event: idx=0 type=2 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=2 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=3 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=4 type=1 op=0 soft=0 hard=0
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Supported cipher 00-0f-ac:6
nl80211: Using driver-based off-channel TX
nl80211: Use separate P2P group interface (driver advertised support)
nl80211: use P2P_DEVICE support
nl80211: interface wlan2 in phy phy2
nl80211: Set mode ifindex 6 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0x1662330
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0505
netlink: Operstate: ifindex=6 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
nl80211: driver param='(null)'
Add interface wlan2 to a new radio phy2
nl80211: Regulatory information - country=98 (DFS-FCC)
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 5170-5250 @ 80 MHz 17 mBm (no outdoor)
nl80211: 5250-5330 @ 80 MHz 20 mBm (no outdoor) (DFS)
nl80211: 5490-5725 @ 160 MHz 23 mBm (DFS)
nl80211: 57240-63720 @ 2160 MHz 40 mBm
nl80211: Added 802.11b mode based on 802.11g information
wlan2: Own MAC address: 04:f0:21:18:24:71
Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures
wpa_driver_nl80211_set_key: ifindex=6 (wlan2) alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan2) alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan2) alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan2) alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan2) alg=0 addr=(nil) key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan2) alg=0 addr=(nil) key_idx=5 set_tx=0 seq_len=0 key_len=0
wlan2: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlan2: Setting scan request: 0.100000 sec
ENGINE: Loading dynamic engine
ENGINE: Loading dynamic engine
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
Using existing control interface directory.
wlan2: Added interface wlan2
wlan2: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
random: Got 18/20 bytes from /dev/random
RTM_NEWLINK: ifi_index=6 ifname=wlan2 operstate=2 linkmode=0 ifi_family=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK: ifi_index=6 ifname=wlan2 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1003 ([UP])
random: Got 2/2 bytes from /dev/random
wlan2: State: DISCONNECTED -> SCANNING
wlan2: Add radio work 'connect'@0x1680290
wlan2: First radio work item in the queue - schedule start immediately
wlan2: Starting radio work 'connect'@0x1680290 after 0.000013 second wait
wlan2: Trying to associate with SSID 'SC224SC225'
wlan2: Cancelling scan request
wlan2: WPA: clearing own WPA/RSN IE
wlan2: Automatic auth_alg selection: 0x1
wlan2: WPA: clearing AP WPA IE
wlan2: WPA: clearing AP RSN IE
wlan2: WPA: clearing own WPA/RSN IE
wlan2: State: SCANNING -> ASSOCIATING
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
nl80211: Received scan results (0 BSSes)
wlan2: BSS: Start scan result update 1
IBSS/mesh: setup freq channel 36, sec_channel_offset 1
IBSS: VHT setup freq cf1 5210, cf2 0, bw 80
wlan2: set_disable_max_amsdu: 1
wlan2: set_ampdu_factor: -1
wlan2: set_ampdu_density: -1
wlan2: set_disable_ht40: 0
wlan2: set_disable_sgi: 0
wlan2: set_disable_ldpc: 0
nl80211: Join IBSS (ifindex=6)
nl80211: Set mode ifindex 6 iftype 1 (ADHOC)
nl80211: Failed to set interface 6 to mode 1: -16 (Device or resource busy)
nl80211: Try mode change after setting interface down
nl80211: Set freq 5180 (ht_enabled=1, vht_enabled=1, bandwidth=80 MHz, cf1=5210 MHz, cf2=0 MHz)
* freq=5180
* vht_enabled=1
* ht_enabled=1
* bandwidth=80
* channel_width=3
* center_freq1=5210
* center_freq2=0
nl80211: Failed to set channel (freq=5180): -16 (Device or resource busy)
nl80211: Failed to set frequency on interface
nl80211: Set mode ifindex 6 iftype 1 (ADHOC)
nl80211: Mode change succeeded while interface is down
nl80211: Unsubscribe mgmt frames handle 0x8888888889eeabb9 (mode change)
nl80211: Subscribe to mgmt frames with non-AP handle 0x1662330
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x1662330 match=
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0505
* SSID - hexdump_ascii(len=10):
53 43 32 32 34 53 43 32 32 35 SC224SC225
* freq=5180
* vht_enabled=1
* ht_enabled=1
* bandwidth=80
* channel_width=3
* center_freq1=5210
* center_freq2=0
* Extra IEs for Beacon/Probe Response frames - hexdump(len=10): 7f 08 00 00 00 00 00 00 00 40
* htcaps - hexdump(len=26): 63 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* htcaps_mask - hexdump(len=26): 63 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps_mask - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
nl80211: Join IBSS failed: ret=-22 (Invalid argument)
wlan2: Association request to the driver failed
wlan2: Radio work 'connect'@0x1680290 done in 1.033801 seconds
Added BSSID 00:00:00:00:00:00 into blacklist
wlan2: Blacklist count 1 --> request scan in 100 ms
wlan2: Setting scan request: 0.100000 sec
wlan2: State: ASSOCIATING -> DISCONNECTED
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
EAPOL: disable timer tick
RTM_NEWLINK: ifi_index=6 ifname=wlan2 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface wlan2 is up
RTM_NEWLINK: ifi_index=6 ifname=wlan2 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1003 ([UP])
l2_packet_receive - recvfrom: Network is down
wlan2: State: DISCONNECTED -> SCANNING
wlan2: Re-association to the same ESS
wlan2: Add radio work 'connect'@0x1680290
wlan2: First radio work item in the queue - schedule start immediately
wlan2: Starting radio work 'connect'@0x1680290 after 0.000021 second wait
wlan2: Trying to associate with SSID 'SC224SC225'
wlan2: Cancelling scan request
wlan2: WPA: clearing own WPA/RSN IE
wlan2: Automatic auth_alg selection: 0x1
wlan2: WPA: clearing AP WPA IE
wlan2: WPA: clearing AP RSN IE
wlan2: WPA: clearing own WPA/RSN IE
wlan2: State: SCANNING -> ASSOCIATING
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
nl80211: Received scan results (0 BSSes)
wlan2: BSS: Start scan result update 2
IBSS/mesh: setup freq channel 36, sec_channel_offset 1
IBSS: VHT setup freq cf1 5210, cf2 0, bw 80
wlan2: set_disable_max_amsdu: 1
wlan2: set_ampdu_factor: -1
wlan2: set_ampdu_density: -1
wlan2: set_disable_ht40: 0
wlan2: set_disable_sgi: 0
wlan2: set_disable_ldpc: 0
nl80211: Join IBSS (ifindex=6)
nl80211: Set mode ifindex 6 iftype 1 (ADHOC)
nl80211: Unsubscribe mgmt frames handle 0x8888888889eeabb9 (mode change)
nl80211: Subscribe to mgmt frames with non-AP handle 0x1662330
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x1662330 match=
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0505
* SSID - hexdump_ascii(len=10):
53 43 32 32 34 53 43 32 32 35 SC224SC225
* freq=5180
* vht_enabled=1
* ht_enabled=1
* bandwidth=80
* channel_width=3
* center_freq1=5210
* center_freq2=0
* Extra IEs for Beacon/Probe Response frames - hexdump(len=10): 7f 08 00 00 00 00 00 00 00 40
* htcaps - hexdump(len=26): 63 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* htcaps_mask - hexdump(len=26): 63 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps_mask - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
nl80211: Join IBSS failed: ret=-22 (Invalid argument)
wlan2: Association request to the driver failed
wlan2: Radio work 'connect'@0x1680290 done in 0.000444 seconds
BSSID 00:00:00:00:00:00 blacklist count incremented to 2
wlan2: Blacklist count 2 --> request scan in 500 ms
wlan2: Setting scan request: 0.500000 sec
wlan2: State: ASSOCIATING -> DISCONNECTED
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
wlan2: State: DISCONNECTED -> SCANNING
wlan2: Re-association to the same ESS
wlan2: Add radio work 'connect'@0x1680290
wlan2: First radio work item in the queue - schedule start immediately
wlan2: Starting radio work 'connect'@0x1680290 after 0.000012 second wait
wlan2: Trying to associate with SSID 'SC224SC225'
wlan2: Cancelling scan request
wlan2: WPA: clearing own WPA/RSN IE
wlan2: Automatic auth_alg selection: 0x1
wlan2: WPA: clearing AP WPA IE
wlan2: WPA: clearing AP RSN IE
wlan2: WPA: clearing own WPA/RSN IE
wlan2: State: SCANNING -> ASSOCIATING
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
nl80211: Received scan results (0 BSSes)
wlan2: BSS: Start scan result update 3
IBSS/mesh: setup freq channel 36, sec_channel_offset 1
IBSS: VHT setup freq cf1 5210, cf2 0, bw 80
wlan2: set_disable_max_amsdu: 1
wlan2: set_ampdu_factor: -1
wlan2: set_ampdu_density: -1
wlan2: set_disable_ht40: 0
wlan2: set_disable_sgi: 0
wlan2: set_disable_ldpc: 0
nl80211: Join IBSS (ifindex=6)
nl80211: Set mode ifindex 6 iftype 1 (ADHOC)
nl80211: Unsubscribe mgmt frames handle 0x8888888889eeabb9 (mode change)
nl80211: Subscribe to mgmt frames with non-AP handle 0x1662330
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x1662330 match=
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0505
* SSID - hexdump_ascii(len=10):
53 43 32 32 34 53 43 32 32 35 SC224SC225
* freq=5180
* vht_enabled=1
* ht_enabled=1
* bandwidth=80
* channel_width=3
* center_freq1=5210
* center_freq2=0
* Extra IEs for Beacon/Probe Response frames - hexdump(len=10): 7f 08 00 00 00 00 00 00 00 40
* htcaps - hexdump(len=26): 63 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* htcaps_mask - hexdump(len=26): 63 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps_mask - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
nl80211: Join IBSS failed: ret=-22 (Invalid argument)
wlan2: Association request to the driver failed
wlan2: Radio work 'connect'@0x1680290 done in 0.000493 seconds
BSSID 00:00:00:00:00:00 blacklist count incremented to 3
wlan2: Blacklist count 3 --> request scan in 1000 ms
wlan2: Setting scan request: 1.000000 sec
wlan2: State: ASSOCIATING -> DISCONNECTED
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
wlan2: State: DISCONNECTED -> SCANNING
wlan2: Re-association to the same ESS
wlan2: Add radio work 'connect'@0x1680290
wlan2: First radio work item in the queue - schedule start immediately
wlan2: Starting radio work 'connect'@0x1680290 after 0.000012 second wait
wlan2: Trying to associate with SSID 'SC224SC225'
wlan2: Cancelling scan request
wlan2: WPA: clearing own WPA/RSN IE
wlan2: Automatic auth_alg selection: 0x1
wlan2: WPA: clearing AP WPA IE
wlan2: WPA: clearing AP RSN IE
wlan2: WPA: clearing own WPA/RSN IE
wlan2: State: SCANNING -> ASSOCIATING
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
nl80211: Received scan results (0 BSSes)
wlan2: BSS: Start scan result update 4
IBSS/mesh: setup freq channel 36, sec_channel_offset 1
IBSS: VHT setup freq cf1 5210, cf2 0, bw 80
wlan2: set_disable_max_amsdu: 1
wlan2: set_ampdu_factor: -1
wlan2: set_ampdu_density: -1
wlan2: set_disable_ht40: 0
wlan2: set_disable_sgi: 0
wlan2: set_disable_ldpc: 0
nl80211: Join IBSS (ifindex=6)
nl80211: Set mode ifindex 6 iftype 1 (ADHOC)
nl80211: Unsubscribe mgmt frames handle 0x8888888889eeabb9 (mode change)
nl80211: Subscribe to mgmt frames with non-AP handle 0x1662330
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x1662330 match=
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0505
* SSID - hexdump_ascii(len=10):
53 43 32 32 34 53 43 32 32 35 SC224SC225
* freq=5180
* vht_enabled=1
* ht_enabled=1
* bandwidth=80
* channel_width=3
* center_freq1=5210
* center_freq2=0
* Extra IEs for Beacon/Probe Response frames - hexdump(len=10): 7f 08 00 00 00 00 00 00 00 40
* htcaps - hexdump(len=26): 63 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* htcaps_mask - hexdump(len=26): 63 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps_mask - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
nl80211: Join IBSS failed: ret=-22 (Invalid argument)
wlan2: Association request to the driver failed
wlan2: Radio work 'connect'@0x1680290 done in 0.000465 seconds
BSSID 00:00:00:00:00:00 blacklist count incremented to 4
wlan2: Blacklist count 4 --> request scan in 5000 ms
wlan2: Setting scan request: 5.000000 sec
wlan2: State: ASSOCIATING -> DISCONNECTED
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
wlan2: State: DISCONNECTED -> SCANNING
wlan2: Re-association to the same ESS
wlan2: Add radio work 'connect'@0x1680290
wlan2: First radio work item in the queue - schedule start immediately
wlan2: Starting radio work 'connect'@0x1680290 after 0.000012 second wait
wlan2: Trying to associate with SSID 'SC224SC225'
wlan2: Cancelling scan request
wlan2: WPA: clearing own WPA/RSN IE
wlan2: Automatic auth_alg selection: 0x1
wlan2: WPA: clearing AP WPA IE
wlan2: WPA: clearing AP RSN IE
wlan2: WPA: clearing own WPA/RSN IE
wlan2: State: SCANNING -> ASSOCIATING
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
nl80211: Received scan results (0 BSSes)
wlan2: BSS: Start scan result update 5
IBSS/mesh: setup freq channel 36, sec_channel_offset 1
IBSS: VHT setup freq cf1 5210, cf2 0, bw 80
wlan2: set_disable_max_amsdu: 1
wlan2: set_ampdu_factor: -1
wlan2: set_ampdu_density: -1
wlan2: set_disable_ht40: 0
wlan2: set_disable_sgi: 0
wlan2: set_disable_ldpc: 0
nl80211: Join IBSS (ifindex=6)
nl80211: Set mode ifindex 6 iftype 1 (ADHOC)
nl80211: Unsubscribe mgmt frames handle 0x8888888889eeabb9 (mode change)
nl80211: Subscribe to mgmt frames with non-AP handle 0x1662330
nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x1662330 match=
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0505
* SSID - hexdump_ascii(len=10):
53 43 32 32 34 53 43 32 32 35 SC224SC225
* freq=5180
* vht_enabled=1
* ht_enabled=1
* bandwidth=80
* channel_width=3
* center_freq1=5210
* center_freq2=0
* Extra IEs for Beacon/Probe Response frames - hexdump(len=10): 7f 08 00 00 00 00 00 00 00 40
* htcaps - hexdump(len=26): 63 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* htcaps_mask - hexdump(len=26): 63 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
* vhtcaps_mask - hexdump(len=12): 00 00 00 00 00 00 00 00 00 00 00 00
nl80211: Join IBSS failed: ret=-22 (Invalid argument)
wlan2: Association request to the driver failed
wlan2: Radio work 'connect'@0x1680290 done in 0.000453 seconds
BSSID 00:00:00:00:00:00 blacklist count incremented to 5
wlan2: Blacklist count 5 --> request scan in 10000 ms
wlan2: Setting scan request: 10.000000 sec
wlan2: State: ASSOCIATING -> DISCONNECTED
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
nl80211: Drv Event 43 (NL80211_CMD_JOIN_IBSS) received for wlan2
nl80211: IBSS 86:8b:e8:f5:fa:d3 joined
nl80211: IBSS-joined on 5180 MHz
nl80211: Operating frequency for the associated BSS from scan results: 5180 MHz
nl80211: IBSS on frequency 5180 MHz
wlan2: Event ASSOC (0) received
wlan2: State: DISCONNECTED -> ASSOCIATED
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
wlan2: Associated to a new BSS: BSSID=86:8b:e8:f5:fa:d3
wlan2: Select network based on association information
wlan2: Network configuration found for the current AP
wlan2: WPA: clearing AP WPA IE
wlan2: WPA: clearing AP RSN IE
wlan2: WPA: clearing own WPA/RSN IE
nl80211: IBSS-joined on 5180 MHz
nl80211: Received scan results (1 BSSes)
wlan2: BSS: Start scan result update 6
wlan2: BSS: Add new id 0 BSSID 86:8b:e8:f5:fa:d3 SSID 'SC224SC225' freq 5180
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=ForceAuthorized
wlan2: Associated with 86:8b:e8:f5:fa:d3
wlan2: WPA: Association event - clear replay counter
wlan2: WPA: Clear old PTK
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state S_FORCE_AUTH
EAPOL: Supplicant port status: Authorized
nl80211: Set supplicant port authorized for 86:8b:e8:f5:fa:d3
nl80211: Failed to set STA flag: -2 (No such file or directory)
EAPOL: SUPP_BE entering state IDLE
wlan2: Cancelling authentication timeout
wlan2: State: ASSOCIATED -> COMPLETED
wlan2: CTRL-EVENT-CONNECTED - Connection to 86:8b:e8:f5:fa:d3 completed [id=0 id_str=]
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
nl80211: Set wlan2 operstate 0->1 (UP)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
wlan2: Cancelling scan request
RTM_NEWLINK: ifi_index=6 ifname=wlan2 operstate=5 linkmode=1 ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
nl80211: Set IF_OPER_UP again based on ifi_flags and expected operstate
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
RTM_NEWLINK: ifi_index=6 ifname=wlan2 wext ifi_family=0 ifi_flags=0x11003 ([UP][LOWER_UP])
nl80211: Set IF_OPER_UP again based on ifi_flags and expected operstate
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=6 (IF_OPER_UP)
RTM_NEWLINK: ifi_index=6 ifname=wlan2 operstate=6 linkmode=1 ifi_family=0 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
wlan2: Removing interface wlan2
wlan2: Request to deauthenticate - bssid=86:8b:e8:f5:fa:d3 pending_bssid=00:00:00:00:00:00 reason=3 state=COMPLETED
nl80211: Leave IBSS request sent successfully
nl80211: Set mode ifindex 6 iftype 2 (STATION)
nl80211: Failed to set interface 6 to mode 2: -16 (Device or resource busy)
nl80211: Try mode change after setting interface down
nl80211: Set mode ifindex 6 iftype 2 (STATION)
nl80211: Mode change succeeded while interface is down
nl80211: Unsubscribe mgmt frames handle 0x8888888889eeabb9 (mode change)
nl80211: Subscribe to mgmt frames with non-AP handle 0x1662330
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0801
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION) nl_handle=0x1662330 match=0505
wlan2: Event DEAUTH (12) received
wlan2: Deauthentication notification
wlan2: * reason 3 (locally generated)
Deauthentication frame IE(s) - hexdump(len=0): [NULL]
wlan2: CTRL-EVENT-DISCONNECTED bssid=86:8b:e8:f5:fa:d3 reason=3 locally_generated=1
wlan2: Auto connect disabled: do not try to re-connect
wlan2: Ignore connection failure indication since interface has been put into disconnected state
wlan2: WPA: Clear old PMK and PTK
wlan2: State: COMPLETED -> DISCONNECTED
nl80211: Set wlan2 operstate 1->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
nl80211: Skip set_supp_port(unauthorized) while not associated
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
wlan2: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlan2 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wlan2: WPA: Clear old PMK and PTK
wlan2: BSS: Remove id 0 BSSID 86:8b:e8:f5:fa:d3 SSID 'SC224SC225' due to wpa_bss_flush
wlan2: Cancelling scan request
wlan2: Cancelling authentication timeout
Remove interface wlan2 from radio phy2
Remove radio phy2
nl80211: deinit ifname=wlan2 disabled_11b_rates=0
nl80211: Remove monitor interface: refcount=0
netlink: Operstate: ifindex=6 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
nl80211: Set mode ifindex 6 iftype 2 (STATION)
nl80211: Unsubscribe mgmt frames handle 0x8888888889eeabb9 (mode change)
wlan2: CTRL-EVENT-TERMINATING
Control interface directory not empty - leaving it behind
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-17 15:39 ` Jorge Baranda
@ 2015-09-17 16:02 ` Marcel H.
2015-09-17 16:11 ` Ben Greear
1 sibling, 0 replies; 22+ messages in thread
From: Marcel H. @ 2015-09-17 16:02 UTC (permalink / raw)
To: Jorge Baranda; +Cc: ath10k
Jorge,
I have never used Candela kernel (I actually have (4.2), but without
success) - Im using kvalos ath git kernel repo with the official
firmware for ath10k (STA / IBSS one)
Marcel
On Thu, Sep 17, 2015 at 5:39 PM, Jorge Baranda <jbaranda@cttc.es> wrote:
> Dear Marcel and all,
>
> I have also followed your setup for trying to configure the wpa_supplicant
> program to setup a 80MHz link but it has not been possible.
> After downloading the last version of wpa_supplicant with git (version 2.5),
> and using your wpa_supplicant.conf file, the link was not possible to be
> setup (the log file is attached) .
> It results that nl80211 driver is not compatible with ap_scan=2 option. If
> using ap_scan=1, the result is the same.
> I have to use the wext driver to establish the link but it is a 20Mhz link .
> The output of iw dev wlan2 info is:
>
> Interface wlan2
> ifindex 6
> wdev 0x200000001
> addr 04:f0:21:18:24:71
> ssid SC224SC225
> type IBSS
> wiphy 2
> channel 36 (5180 MHz), width: 20 MHz (no HT), center1: 5180 MHz
>
> Anyone faced the same problem?
> Maybe is not possible to setup the 80MHz link with the Candela Kernel 4.0.
>
> Thank you very much in advance for your time and attention,
>
> Regards,
>
> Jordi
>
>
> El 17/09/15 12:27, Jorge Baranda escribió:
>
>> Dear Hannes and all,
>>
>> I have tried to replicate Hannes' setup to make work wpa_supplicant with
>> Candela Kernel 4.0 (and Candela firmware 10.1.467-ct-14), but I have not
>> been successful.
>> I downloaded the last version of wpa_supplicant from
>> http://w1.fi/wpa_supplicant/ website, applied your changes in the
>> wpa_supplicant.c file and your .config file.
>> Then I used your wpa_supplicant.conf file but it failed to start (attached
>> the full log). The error says that "the ctrl_interface exists and seems to
>> be in use"
>>
>> I have checked with ps aux to see if there is a wpa_supplicant process but
>> after kill it, it restarts again.
>> This is the result of ps aux | grep wpa_supplicant:
>>
>> root 2368 0.0 0.0 30868 6140 ? Ss 11:40 0:00
>> /sbin/wpa_supplicant -u -s -O /var/run/wpa_supplicant
>> monet 2690 0.0 0.0 13688 2372 pts/9 S+ 12:10 0:00 grep
>> --color=auto wpa_supplicant
>>
>> Browsing in the internet I have not found any answer to solve this problem
>> :(. Have you faced it?
>>
>> Then I have tried removing the "ctrl_interface line" from the
>> wpa_supplicant.conf file (resulting in a file similar to the one sent by
>> Marcel H.) and the program started in a loop (see attached
>> wpa_supplicant2.log). It seems like it tries to connect to the ssid "test"
>> but it is not able to find it (normal, because we want to create it).
>>
>> Apart from this, in this setup, do I have to make any change also in the
>> /etc/network/interfaces file?
>>
>> Thank you very much for your time and attention,
>>
>> Regards,
>>
>> Jordi
>>
>>
>>
>> El 09/09/15 13:15, Harms, Hannes escribió:
>>>
>>> My wpa_supplicant config:
>>>
>>>
>>> ctrl_interface=DIR=/run/wpa_supplicant
>>> ap_scan=2
>>>
>>> network={
>>> ssid="test"
>>> bssid=02:12:34:56:78:9A
>>> key_mgmt=NONE
>>> mode=1
>>> frequency=5180
>>> disable_ht=0
>>> disable_vht=0
>>> disable_max_amsdu=1 # not sure, works also without this flag
>>> }
>>>
>>>
>>> Regards
>>> Hannes
>>>
>>> Am 09.09.2015 um 13:08 schrieb Jorge Baranda:
>>>>
>>>> Hi,
>>>>
>>>> Good news!! Harms, could you share full wpa_supplicant configuration
>>>> files?
>>>> (for both computers).
>>>> I will download the latest version of wpa_supplicant, apply your changes
>>>> and try
>>>> to make work IBSS mode and 80MHz with Candela Kernel 4.0.
>>>>
>>>> Thanks,
>>>>
>>>> El 09/09/15 12:59, Harms, Hannes escribió:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have WLE900VX working in IBSS mode and 80 Mhz with Candela Kernel
>>>>> 4.2.
>>>>> For me also the latest wpa_supplicant was not able to activate 80MHz by
>>>>> default , I don't no why.
>>>>>
>>>>> The only way I found to get it working was to modify
>>>>> wpa_supplicant/wpa_supplicant.c
>>>>> Commit following two lines in wpa_supplicant.c like this :
>>>>>
>>>>> //if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_VHT_IBSS))
>>>>> // return;
>>>>>
>>>>> That was all for me to get it working.
>>>>>
>>>>> wpa_supplicant config file:
>>>>> # Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is
>>>>> ignored)
>>>>> CONFIG_LIBNL32=y
>>>>>
>>>>> # Support VHT overrides (disable VHT, mask MCS rates, etc.)
>>>>> CONFIG_VHT_OVERRIDES=y
>>>>>
>>>>> # Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
>>>>> CONFIG_HT_OVERRIDES=y
>>>>>
>>>>> # IEEE 802.11n (High Throughput) support (mainly for AP mode)
>>>>> CONFIG_IEEE80211N=y
>>>>>
>>>>> # IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
>>>>> # (depends on CONFIG_IEEE80211N)
>>>>> CONFIG_IEEE80211AC=y
>>>>>
>>>>> # IEEE 802.11w (management frame protection), also known as PMF
>>>>> # Driver support is also needed for IEEE 802.11w.
>>>>> CONFIG_IEEE80211W=y
>>>>>
>>>>> Am 09.09.2015 um 11:46 schrieb Marcel H.:
>>>>>>
>>>>>> May I ask someone for support on this one?
>>>>>> We would really like to make this work and I'm running out of ideas -
>>>>>> is there any way do turn detailed debugging on to get a better
>>>>>> understanding why do I get the following message back? ->
>>>>>>
>>>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>>>> command failed: Device or resource busy (-16)
>>>>>>
>>>>>> Thanks,
>>>>>> Marcel
>>>>>>
>>>>>> On Wed, Sep 9, 2015 at 9:49 AM, Marcel H. <maco@blava.net> wrote:
>>>>>>>
>>>>>>> Thanks for the response, unfortunately this is the result of defining
>>>>>>> the center frequency:
>>>>>>>
>>>>>>> root@voyage1:/opt/ca_node/etc# iw wlan0 set freq 5745 80 5775
>>>>>>> command failed: Device or resource busy (-16)
>>>>>>>
>>>>>>> Also, using wpa_supplicant does not work using the following config:
>>>>>>>
>>>>>>> root@voyage1:/opt/ca_node/etc# cat wpa_supplicant-mesh.conf
>>>>>>> ap_scan=2
>>>>>>> ctrl_interface=/run/wpa_supplicant
>>>>>>> update_config=1
>>>>>>> device_type=0-00000000-0
>>>>>>>
>>>>>>> network={
>>>>>>> scan_ssid=1
>>>>>>> key_mgmt=NONE
>>>>>>> priority=1
>>>>>>> ssid="ibss"
>>>>>>> mode=1
>>>>>>> frequency=5180
>>>>>>> }
>>>>>>>
>>>>>>> running as:
>>>>>>> wpa_supplicant -i wlan0 -c ./wpa_supplicant-mesh.conf -dd -D
>>>>>>> nl80211,wext
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> root@voyage1:/opt/ca_node/etc# iw dev wlan0 info
>>>>>>> Interface wlan0
>>>>>>> ifindex 5
>>>>>>> wdev 0x100000001
>>>>>>> addr 04:f0:21:1b:5f:3d
>>>>>>> ssid ibss-rsn
>>>>>>> type IBSS
>>>>>>> wiphy 1
>>>>>>> channel 36 (5180 MHz), width: 20 MHz, center1: 5180 MHz
>>>>>>>
>>>>>>> root@voyage1:/opt/ca_node/etc# iw phy phy1 info
>>>>>>> Wiphy phy1
>>>>>>> DFS state: usable (for 46424 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar
>>>>>>> detection)
>>>>>>> DFS state: usable (for 46424 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar
>>>>>>> detection)
>>>>>>> DFS state: usable (for 46424 sec)
>>>>>>> DFS CAC time: 60000 ms
>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar
>>>>>>> detection)
>>>>>>> DFS state: usable (for 46424 sec)
>>>>>>> Its fallbacking to 20MHz channels, which is even less than 40MHz
>>>>>>> channels set manually by iw
>>>>>>>
>>>>>>>
>>>>>>> How recent wpa_supplicat shall I try? I believe this it quite recent:
>>>>>>>
>>>>>>> root@voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>>>>>> wpa_supplicant v2.3
>>>>>>> Copyright (c) 2003-2014, Jouni Malinen <j@w1.fi> and contributors
>>>>>>>
>>>>>>>
>>>>>>> Re. the regulatory settings:
>>>>>>>
>>>>>>> root@voyage1:/opt/ca_node/etc# iw reg get
>>>>>>> country US: DFS-FCC
>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>
>>>>>>>
>>>>>>> Any other thoughts?
>>>>>>>
>>>>>>> Marcel
>>>>>>>
>>>>>>> On Wed, Sep 9, 2015 at 9:43 AM, Janusz Dziedzic
>>>>>>> <janusz.dziedzic@tieto.com> wrote:
>>>>>>>>
>>>>>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda@cttc.es>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi everyone,
>>>>>>>>>
>>>>>>>>> Reading this thread, I would like to share with people some doubts
>>>>>>>>> about it.
>>>>>>>>> @Marco, I imagine you want to run your WLE600VX device using the
>>>>>>>>> 802.11ac
>>>>>>>>> protocol, isn't it?
>>>>>>>>> @Janusz, with running wpa_supplicant on both computers, will the
>>>>>>>>> ad-hoc
>>>>>>>>> connection be established? I am starting with these tools and now,
>>>>>>>>> I am
>>>>>>>>> getting used to know how they work. I was creating the ad-hoc
>>>>>>>>> connection
>>>>>>>>> with the iw tool.
>>>>>>>>>
>>>>>>>> Yes you should use wpa_supplicant on both PC.
>>>>>>>> In the future probably someone will add IBSS-VHT support also for
>>>>>>>> iw.
>>>>>>>>
>>>>>>>> BR
>>>>>>>> Janusz
>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> El 09/09/15 07:50, Janusz Dziedzic escribió:
>>>>>>>>>
>>>>>>>>>> On 8 September 2015 at 23:31, Marcel H. <maco@blava.net> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi everyone,
>>>>>>>>>>> I have an interesting issue - I'm trying to run the QCA9882 based
>>>>>>>>>>> card
>>>>>>>>>>> in IBSS mode (to be used for BATMAN), however all I can do is to
>>>>>>>>>>> run
>>>>>>>>>>> in in 40Mhz channel width in 5GHz spectrum. Any attempt to run it
>>>>>>>>>>> in
>>>>>>>>>>> 80MHz width resolves in the following:
>>>>>>>>>>>
>>>>>>>>>> You should run IBSS using fresh wpa_supplicant (best latest code).
>>>>>>>>>> By
>>>>>>>>>> default should run in 80MHz.
>>>>>>>>>> Other case is your regulatory - are you allow to use 80MHz on
>>>>>>>>>> channel
>>>>>>>>>> 157? First try 5180.
>>>>>>>>>>
>>>>>>>>>> eg. of wpa_supplicant config:
>>>>>>>>>>
>>>>>>>>>> network = {
>>>>>>>>>> ssid="test_ibss"
>>>>>>>>>> key_mgmt=NONE
>>>>>>>>>> mode=1
>>>>>>>>>> frequency=5180
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> BR
>>>>>>>>>> Janusz
>>>>>>>>>>
>>>>>>>>>>> Interface wlan0
>>>>>>>>>>> ifindex 5
>>>>>>>>>>> wdev 0x1
>>>>>>>>>>> addr 04:f0:21:1b:5f:3b
>>>>>>>>>>> ssid my-mesh-network
>>>>>>>>>>> type IBSS
>>>>>>>>>>> wiphy 0
>>>>>>>>>>> channel 157 (5785 MHz), width: 40 MHz, center1: 5795 MHz
>>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>>>> root@voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> More info:
>>>>>>>>>>> =====================================================
>>>>>>>>>>> 06:00.0 Network controller: Qualcomm Atheros QCA988x 802.11ac
>>>>>>>>>>> Wireless
>>>>>>>>>>> Network Adapter
>>>>>>>>>>> Flags: bus master, fast devsel, latency 0, IRQ 27
>>>>>>>>>>> Memory at f7400000 (64-bit, non-prefetchable) [size=2M]
>>>>>>>>>>> Expansion ROM at f7600000 [disabled] [size=64K]
>>>>>>>>>>> Capabilities: [40] Power Management version 2
>>>>>>>>>>> Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
>>>>>>>>>>> Capabilities: [70] Express Endpoint, MSI 00
>>>>>>>>>>> Capabilities: [100] Advanced Error Reporting
>>>>>>>>>>> Capabilities: [140] Virtual Channel
>>>>>>>>>>> Capabilities: [160] Device Serial Number
>>>>>>>>>>> 00-00-00-00-00-00-00-00
>>>>>>>>>>> Kernel driver in use: ath10k_pci
>>>>>>>>>>>
>>>>>>>>>>> root@voyage2:/opt/ca_node/bin# iw reg get
>>>>>>>>>>> country US: DFS-FCC
>>>>>>>>>>> (2402 - 2472 @ 40), (N/A, 30), (N/A)
>>>>>>>>>>> (5170 - 5250 @ 80), (N/A, 17), (N/A)
>>>>>>>>>>> (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
>>>>>>>>>>> (5735 - 5835 @ 80), (N/A, 30), (N/A)
>>>>>>>>>>> (57240 - 63720 @ 2160), (N/A, 40), (N/A)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> root@voyage2:/opt/ca_node/bin# uname -a
>>>>>>>>>>> Linux voyage2 4.2.0-wl-ath-261216-gd89281c #1 SMP Tue Sep 8
>>>>>>>>>>> 14:03:33
>>>>>>>>>>> GMT 2015 i686 GNU/Linux
>>>>>>>>>>> (todays checkout from https://github.com/kvalo/ath + Voyage Linux
>>>>>>>>>>> 0.10
>>>>>>>>>>> .config)
>>>>>>>>>>>
>>>>>>>>>>> root@voyage2:/lib/firmware/ath10k/QCA988X/hw2.0# md5sum
>>>>>>>>>>> ./firmware-2.bin
>>>>>>>>>>> e2db04b651c2b5ced4732f3f009a1cce ./firmware-2.bin
>>>>>>>>>>> (this is from the 'main' directory in the
>>>>>>>>>>> https://github.com/kvalo/ath10k-firmware)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Wiphy phy0
>>>>>>>>>>> max # scan SSIDs: 16
>>>>>>>>>>> max scan IEs length: 195 bytes
>>>>>>>>>>> Retry short limit: 7
>>>>>>>>>>> Retry long limit: 4
>>>>>>>>>>> Coverage class: 0 (up to 0m)
>>>>>>>>>>> Device supports RSN-IBSS.
>>>>>>>>>>> Device supports AP-side u-APSD.
>>>>>>>>>>> Supported Ciphers:
>>>>>>>>>>> * WEP40 (00-0f-ac:1)
>>>>>>>>>>> * WEP104 (00-0f-ac:5)
>>>>>>>>>>> * TKIP (00-0f-ac:2)
>>>>>>>>>>> * CCMP (00-0f-ac:4)
>>>>>>>>>>> * CMAC (00-0f-ac:6)
>>>>>>>>>>> Available Antennas: TX 0x3 RX 0x3
>>>>>>>>>>> Configured Antennas: TX 0x3 RX 0x3
>>>>>>>>>>> Supported interface modes:
>>>>>>>>>>> * IBSS
>>>>>>>>>>> * managed
>>>>>>>>>>> * AP
>>>>>>>>>>> * AP/VLAN
>>>>>>>>>>> * monitor
>>>>>>>>>>> * P2P-client
>>>>>>>>>>> * P2P-GO
>>>>>>>>>>> * P2P-device
>>>>>>>>>>> Band 1:
>>>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>>>> RX LDPC
>>>>>>>>>>> HT20/HT40
>>>>>>>>>>> Static SM Power Save
>>>>>>>>>>> RX HT20 SGI
>>>>>>>>>>> RX HT40 SGI
>>>>>>>>>>> TX STBC
>>>>>>>>>>> RX STBC 1-stream
>>>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>>>> DSSS/CCK HT40
>>>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>>>> Max MPDU length: 11454
>>>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>>>> RX LDPC
>>>>>>>>>>> short GI (80 MHz)
>>>>>>>>>>> TX STBC
>>>>>>>>>>> RX antenna pattern consistency
>>>>>>>>>>> TX antenna pattern consistency
>>>>>>>>>>> VHT RX MCS set:
>>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>>> 3 streams: not supported
>>>>>>>>>>> 4 streams: not supported
>>>>>>>>>>> 5 streams: not supported
>>>>>>>>>>> 6 streams: not supported
>>>>>>>>>>> 7 streams: not supported
>>>>>>>>>>> 8 streams: not supported
>>>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>>>> VHT TX MCS set:
>>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>>> 3 streams: not supported
>>>>>>>>>>> 4 streams: not supported
>>>>>>>>>>> 5 streams: not supported
>>>>>>>>>>> 6 streams: not supported
>>>>>>>>>>> 7 streams: not supported
>>>>>>>>>>> 8 streams: not supported
>>>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>>>> Bitrates (non-HT):
>>>>>>>>>>> * 1.0 Mbps
>>>>>>>>>>> * 2.0 Mbps (short preamble supported)
>>>>>>>>>>> * 5.5 Mbps (short preamble supported)
>>>>>>>>>>> * 11.0 Mbps (short preamble supported)
>>>>>>>>>>> * 6.0 Mbps
>>>>>>>>>>> * 9.0 Mbps
>>>>>>>>>>> * 12.0 Mbps
>>>>>>>>>>> * 18.0 Mbps
>>>>>>>>>>> * 24.0 Mbps
>>>>>>>>>>> * 36.0 Mbps
>>>>>>>>>>> * 48.0 Mbps
>>>>>>>>>>> * 54.0 Mbps
>>>>>>>>>>> Frequencies:
>>>>>>>>>>> * 2412 MHz [1] (30.0 dBm)
>>>>>>>>>>> * 2417 MHz [2] (30.0 dBm)
>>>>>>>>>>> * 2422 MHz [3] (30.0 dBm)
>>>>>>>>>>> * 2427 MHz [4] (30.0 dBm)
>>>>>>>>>>> * 2432 MHz [5] (30.0 dBm)
>>>>>>>>>>> * 2437 MHz [6] (30.0 dBm)
>>>>>>>>>>> * 2442 MHz [7] (30.0 dBm)
>>>>>>>>>>> * 2447 MHz [8] (30.0 dBm)
>>>>>>>>>>> * 2452 MHz [9] (30.0 dBm)
>>>>>>>>>>> * 2457 MHz [10] (30.0 dBm)
>>>>>>>>>>> * 2462 MHz [11] (30.0 dBm)
>>>>>>>>>>> * 2467 MHz [12] (disabled)
>>>>>>>>>>> * 2472 MHz [13] (disabled)
>>>>>>>>>>> * 2484 MHz [14] (disabled)
>>>>>>>>>>> Band 2:
>>>>>>>>>>> Capabilities: 0x19e3
>>>>>>>>>>> RX LDPC
>>>>>>>>>>> HT20/HT40
>>>>>>>>>>> Static SM Power Save
>>>>>>>>>>> RX HT20 SGI
>>>>>>>>>>> RX HT40 SGI
>>>>>>>>>>> TX STBC
>>>>>>>>>>> RX STBC 1-stream
>>>>>>>>>>> Max AMSDU length: 7935 bytes
>>>>>>>>>>> DSSS/CCK HT40
>>>>>>>>>>> Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
>>>>>>>>>>> Minimum RX AMPDU time spacing: 8 usec (0x06)
>>>>>>>>>>> HT TX/RX MCS rate indexes supported: 0-15
>>>>>>>>>>> VHT Capabilities (0x338001b2):
>>>>>>>>>>> Max MPDU length: 11454
>>>>>>>>>>> Supported Channel Width: neither 160 nor 80+80
>>>>>>>>>>> RX LDPC
>>>>>>>>>>> short GI (80 MHz)
>>>>>>>>>>> TX STBC
>>>>>>>>>>> RX antenna pattern consistency
>>>>>>>>>>> TX antenna pattern consistency
>>>>>>>>>>> VHT RX MCS set:
>>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>>> 3 streams: not supported
>>>>>>>>>>> 4 streams: not supported
>>>>>>>>>>> 5 streams: not supported
>>>>>>>>>>> 6 streams: not supported
>>>>>>>>>>> 7 streams: not supported
>>>>>>>>>>> 8 streams: not supported
>>>>>>>>>>> VHT RX highest supported: 0 Mbps
>>>>>>>>>>> VHT TX MCS set:
>>>>>>>>>>> 1 streams: MCS 0-9
>>>>>>>>>>> 2 streams: MCS 0-9
>>>>>>>>>>> 3 streams: not supported
>>>>>>>>>>> 4 streams: not supported
>>>>>>>>>>> 5 streams: not supported
>>>>>>>>>>> 6 streams: not supported
>>>>>>>>>>> 7 streams: not supported
>>>>>>>>>>> 8 streams: not supported
>>>>>>>>>>> VHT TX highest supported: 0 Mbps
>>>>>>>>>>> Bitrates (non-HT):
>>>>>>>>>>> * 6.0 Mbps
>>>>>>>>>>> * 9.0 Mbps
>>>>>>>>>>> * 12.0 Mbps
>>>>>>>>>>> * 18.0 Mbps
>>>>>>>>>>> * 24.0 Mbps
>>>>>>>>>>> * 36.0 Mbps
>>>>>>>>>>> * 48.0 Mbps
>>>>>>>>>>> * 54.0 Mbps
>>>>>>>>>>> Frequencies:
>>>>>>>>>>> * 5180 MHz [36] (17.0 dBm)
>>>>>>>>>>> * 5200 MHz [40] (17.0 dBm)
>>>>>>>>>>> * 5220 MHz [44] (17.0 dBm)
>>>>>>>>>>> * 5240 MHz [48] (17.0 dBm)
>>>>>>>>>>> * 5260 MHz [52] (23.0 dBm) (no IR, radar detection)
>>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>>> * 5280 MHz [56] (23.0 dBm) (no IR, radar detection)
>>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>>> * 5300 MHz [60] (23.0 dBm) (no IR, radar detection)
>>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>>> DFS CAC time: 60000 ms
>>>>>>>>>>> * 5320 MHz [64] (23.0 dBm) (no IR, radar detection)
>>>>>>>>>>> DFS state: usable (for 1076 sec)
>>>>>>>>>>> DFS CAC time: 60000 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] (disabled)
>>>>>>>>>>> * 5745 MHz [149] (30.0 dBm)
>>>>>>>>>>> * 5765 MHz [153] (30.0 dBm)
>>>>>>>>>>> * 5785 MHz [157] (30.0 dBm)
>>>>>>>>>>> * 5805 MHz [161] (30.0 dBm)
>>>>>>>>>>> * 5825 MHz [165] (30.0 dBm)
>>>>>>>>>>> Supported commands:
>>>>>>>>>>> * new_interface
>>>>>>>>>>> * set_interface
>>>>>>>>>>> * new_key
>>>>>>>>>>> * start_ap
>>>>>>>>>>> * new_station
>>>>>>>>>>> * set_bss
>>>>>>>>>>> * authenticate
>>>>>>>>>>> * associate
>>>>>>>>>>> * deauthenticate
>>>>>>>>>>> * disassociate
>>>>>>>>>>> * join_ibss
>>>>>>>>>>> * remain_on_channel
>>>>>>>>>>> * set_tx_bitrate_mask
>>>>>>>>>>> * frame
>>>>>>>>>>> * frame_wait_cancel
>>>>>>>>>>> * set_wiphy_netns
>>>>>>>>>>> * set_channel
>>>>>>>>>>> * set_wds_peer
>>>>>>>>>>> * probe_client
>>>>>>>>>>> * set_noack_map
>>>>>>>>>>> * register_beacons
>>>>>>>>>>> * start_p2p_device
>>>>>>>>>>> * set_mcast_rate
>>>>>>>>>>> * testmode
>>>>>>>>>>> * channel_switch
>>>>>>>>>>> * Unknown command (104)
>>>>>>>>>>> * connect
>>>>>>>>>>> * disconnect
>>>>>>>>>>> Supported TX frame types:
>>>>>>>>>>> * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>>>> 0x90
>>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>>> * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>>> 0x80 0x90
>>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>>> * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>>>> 0x90 0xa0
>>>>>>>>>>> 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>>> * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>>> 0x80 0x90
>>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>>> * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>>> 0x80
>>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>>> * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>>> 0x80
>>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>>> * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80
>>>>>>>>>>> 0x90
>>>>>>>>>>> 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>>> * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70
>>>>>>>>>>> 0x80
>>>>>>>>>>> 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
>>>>>>>>>>> Supported RX frame types:
>>>>>>>>>>> * IBSS: 0x40 0xb0 0xc0 0xd0
>>>>>>>>>>> * managed: 0x40 0xd0
>>>>>>>>>>> * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>>> * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>>> * mesh point: 0xb0 0xc0 0xd0
>>>>>>>>>>> * P2P-client: 0x40 0xd0
>>>>>>>>>>> * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
>>>>>>>>>>> * P2P-device: 0x40 0xd0
>>>>>>>>>>> software interface modes (can always be added):
>>>>>>>>>>> * AP/VLAN
>>>>>>>>>>> * monitor
>>>>>>>>>>> valid interface combinations:
>>>>>>>>>>> * #{ managed, P2P-client } <= 8, #{ P2P-GO } <= 3, #{
>>>>>>>>>>> P2P-device } <= 1, #{ AP } <= 7,
>>>>>>>>>>> total <= 8, #channels <= 1, STA/AP BI must match
>>>>>>>>>>> HT Capability overrides:
>>>>>>>>>>> * MCS: ff ff ff ff ff ff ff ff ff ff
>>>>>>>>>>> * maximum A-MSDU length
>>>>>>>>>>> * supported channel width
>>>>>>>>>>> * short GI for 40 MHz
>>>>>>>>>>> * max A-MPDU length exponent
>>>>>>>>>>> * min MPDU start spacing
>>>>>>>>>>> Device supports TX status socket option.
>>>>>>>>>>> Device supports HT-IBSS.
>>>>>>>>>>> Device supports SAE with AUTHENTICATE command
>>>>>>>>>>> Device supports scan flush.
>>>>>>>>>>> Device supports per-vif TX power setting
>>>>>>>>>>> Driver supports a userspace MPM
>>>>>>>>>>> Driver/device bandwidth changes during BSS lifetime (AP/GO
>>>>>>>>>>> mode)
>>>>>>>>>>> Device supports static SMPS
>>>>>>>>>>> =====================================================
>>>>>>>>>>>
>>>>>>>>>>> I am grateful for any help here and do have some time to help
>>>>>>>>>>> debugging the issue.
>>>>>>>>>>>
>>>>>>>>>>> Marcel
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> ------------------------------------------------------
>>>>>>>>>>> This message is not intended to have
>>>>>>>>>>> contractual effect
>>>>>>>>>>> ------------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Jorge Baranda
>>>>>>>>> Research Engineer, MSc
>>>>>>>>> jorge.baranda@cttc.es
>>>>>>>>>
>>>>>>>>> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
>>>>>>>>> Av. Carl Friedrich Gauss, 7
>>>>>>>>> 08860 Castelldefels, Barcelona (Spain)
>>>>>>>>> Tel: +34 93 645 29 00 Ext: 2171
>>>>>>>>> Fax. +34 93 645 29 01
>>>>>>>>> www.cttc.es
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> ------------------------------------------------------
>>>>>>> This message is not intended to have
>>>>>>> contractual effect
>>>>>>> ------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
>
> --
> Jorge Baranda
> Research Engineer, MSc
> jorge.baranda@cttc.es
>
> Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
> Av. Carl Friedrich Gauss, 7
> 08860 Castelldefels, Barcelona (Spain)
> Tel: +34 93 645 29 00 Ext: 2171
> Fax. +34 93 645 29 01
> www.cttc.es
>
--
------------------------------------------------------
This message is not intended to have
contractual effect
------------------------------------------------------
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-17 15:39 ` Jorge Baranda
2015-09-17 16:02 ` Marcel H.
@ 2015-09-17 16:11 ` Ben Greear
2015-09-18 6:29 ` Jorge Baranda
1 sibling, 1 reply; 22+ messages in thread
From: Ben Greear @ 2015-09-17 16:11 UTC (permalink / raw)
To: Jorge Baranda, ath10k, Marcel H.
On 09/17/2015 08:39 AM, Jorge Baranda wrote:
> Dear Marcel and all,
>
> I have also followed your setup for trying to configure the wpa_supplicant program to setup a 80MHz link but it has not been possible.
> After downloading the last version of wpa_supplicant with git (version 2.5), and using your wpa_supplicant.conf file, the link was not possible to be setup (the
> log file is attached) .
Please post your supplicant .conf file as well.
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] 22+ messages in thread
* Re: WLE600VX from PCEngines
2015-09-17 16:11 ` Ben Greear
@ 2015-09-18 6:29 ` Jorge Baranda
0 siblings, 0 replies; 22+ messages in thread
From: Jorge Baranda @ 2015-09-18 6:29 UTC (permalink / raw)
To: Ben Greear, ath10k
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
Dear Ben, all,
Here you have my wpa_supplicant configuration files.
In the meantime, I will try to replicate the setup with the Candela
Kernel 4.2.
Thank you very much for your time and attention,
Jordi Baranda
El 17/09/15 18:11, Ben Greear escribió:
> On 09/17/2015 08:39 AM, Jorge Baranda wrote:
>> Dear Marcel and all,
>>
>> I have also followed your setup for trying to configure the
>> wpa_supplicant program to setup a 80MHz link but it has not been
>> possible.
>> After downloading the last version of wpa_supplicant with git
>> (version 2.5), and using your wpa_supplicant.conf file, the link was
>> not possible to be setup (the
>> log file is attached) .
>
> Please post your supplicant .conf file as well.
>
> Thanks,
> Ben
>
--
Jorge Baranda
Research Engineer, MSc
jorge.baranda@cttc.es
Centre Tecnològic de Telecomunicacions de Catalunya (CTTC)
Av. Carl Friedrich Gauss, 7
08860 Castelldefels, Barcelona (Spain)
Tel: +34 93 645 29 00 Ext: 2171
Fax. +34 93 645 29 01
www.cttc.es
[-- Attachment #2: wpa_supplicant.conf --]
[-- Type: text/plain, Size: 262 bytes --]
ctrl_interface=DIR=/run/wpa_supplicant
ap_scan=2
network={
ssid="SC224SC225"
#bssid=02:12:34:56:78:9A
key_mgmt=NONE
mode=1
frequency=5180
disable_ht=0
disable_vht=0
disable_max_amsdu=1 # not sure, works also without this flag
}
[-- Attachment #3: config_wpa_supplicant.txt --]
[-- Type: text/plain, Size: 18290 bytes --]
# Example wpa_supplicant build time configuration
#
# This file lists the configuration options that are used when building the
# hostapd binary. All lines starting with # are ignored. Configuration option
# lines must be commented out complete, if they are not to be included, i.e.,
# just setting VARIABLE=n is not disabling that variable.
#
# This file is included in Makefile, so variables like CFLAGS and LIBS can also
# be modified from here. In most cases, these lines should use += in order not
# to override previous values of the variables.
# Uncomment following two lines and fix the paths if you have installed OpenSSL
# or GnuTLS in non-default location
#CFLAGS += -I/usr/local/openssl/include
#LIBS += -L/usr/local/openssl/lib
# Some Red Hat versions seem to include kerberos header files from OpenSSL, but
# the kerberos files are not in the default include path. Following line can be
# used to fix build issues on such systems (krb5.h not found).
#CFLAGS += -I/usr/include/kerberos
# Driver interface for generic Linux wireless extensions
# Note: WEXT is deprecated in the current Linux kernel version and no new
# functionality is added to it. nl80211-based interface is the new
# replacement for WEXT and its use allows wpa_supplicant to properly control
# the driver to improve existing functionality like roaming and to support new
# functionality.
CONFIG_DRIVER_WEXT=y
# Driver interface for Linux drivers using the nl80211 kernel interface
CONFIG_DRIVER_NL80211=y
# driver_nl80211.c requires libnl. If you are compiling it yourself
# you may need to point hostapd to your version of libnl.
#
#CFLAGS += -I$<path to libnl include files>
#LIBS += -L$<path to libnl library files>
# Use libnl v2.0 (or 3.0) libraries.
#CONFIG_LIBNL20=y
# Use libnl 3.2 libraries (if this is selected, CONFIG_LIBNL20 is ignored)
CONFIG_LIBNL32=y
# Driver interface for FreeBSD net80211 layer (e.g., Atheros driver)
#CONFIG_DRIVER_BSD=y
#CFLAGS += -I/usr/local/include
#LIBS += -L/usr/local/lib
#LIBS_p += -L/usr/local/lib
#LIBS_c += -L/usr/local/lib
# Driver interface for Windows NDIS
#CONFIG_DRIVER_NDIS=y
#CFLAGS += -I/usr/include/w32api/ddk
#LIBS += -L/usr/local/lib
# For native build using mingw
#CONFIG_NATIVE_WINDOWS=y
# Additional directories for cross-compilation on Linux host for mingw target
#CFLAGS += -I/opt/mingw/mingw32/include/ddk
#LIBS += -L/opt/mingw/mingw32/lib
#CC=mingw32-gcc
# By default, driver_ndis uses WinPcap for low-level operations. This can be
# replaced with the following option which replaces WinPcap calls with NDISUIO.
# However, this requires that WZC is disabled (net stop wzcsvc) before starting
# wpa_supplicant.
# CONFIG_USE_NDISUIO=y
# Driver interface for wired Ethernet drivers
CONFIG_DRIVER_WIRED=y
# Driver interface for the Broadcom RoboSwitch family
#CONFIG_DRIVER_ROBOSWITCH=y
# Driver interface for no driver (e.g., WPS ER only)
#CONFIG_DRIVER_NONE=y
# Solaris libraries
#LIBS += -lsocket -ldlpi -lnsl
#LIBS_c += -lsocket
# Enable IEEE 802.1X Supplicant (automatically included if any EAP method is
# included)
CONFIG_IEEE8021X_EAPOL=y
# EAP-MD5
CONFIG_EAP_MD5=y
# EAP-MSCHAPv2
CONFIG_EAP_MSCHAPV2=y
# EAP-TLS
CONFIG_EAP_TLS=y
# EAL-PEAP
CONFIG_EAP_PEAP=y
# EAP-TTLS
CONFIG_EAP_TTLS=y
# EAP-FAST
# Note: If OpenSSL is used as the TLS library, OpenSSL 1.0 or newer is needed
# for EAP-FAST support. Older OpenSSL releases would need to be patched, e.g.,
# with openssl-0.9.8x-tls-extensions.patch, to add the needed functions.
#CONFIG_EAP_FAST=y
# EAP-GTC
CONFIG_EAP_GTC=y
# EAP-OTP
CONFIG_EAP_OTP=y
# EAP-SIM (enable CONFIG_PCSC, if EAP-SIM is used)
#CONFIG_EAP_SIM=y
# EAP-PSK (experimental; this is _not_ needed for WPA-PSK)
#CONFIG_EAP_PSK=y
# EAP-pwd (secure authentication using only a password)
#CONFIG_EAP_PWD=y
# EAP-PAX
#CONFIG_EAP_PAX=y
# LEAP
CONFIG_EAP_LEAP=y
# EAP-AKA (enable CONFIG_PCSC, if EAP-AKA is used)
#CONFIG_EAP_AKA=y
# EAP-AKA' (enable CONFIG_PCSC, if EAP-AKA' is used).
# This requires CONFIG_EAP_AKA to be enabled, too.
#CONFIG_EAP_AKA_PRIME=y
# Enable USIM simulator (Milenage) for EAP-AKA
#CONFIG_USIM_SIMULATOR=y
# EAP-SAKE
#CONFIG_EAP_SAKE=y
# EAP-GPSK
#CONFIG_EAP_GPSK=y
# Include support for optional SHA256 cipher suite in EAP-GPSK
#CONFIG_EAP_GPSK_SHA256=y
# EAP-TNC and related Trusted Network Connect support (experimental)
#CONFIG_EAP_TNC=y
# Wi-Fi Protected Setup (WPS)
#CONFIG_WPS=y
# Enable WPS external registrar functionality
#CONFIG_WPS_ER=y
# Disable credentials for an open network by default when acting as a WPS
# registrar.
#CONFIG_WPS_REG_DISABLE_OPEN=y
# Enable WPS support with NFC config method
#CONFIG_WPS_NFC=y
# EAP-IKEv2
#CONFIG_EAP_IKEV2=y
# EAP-EKE
#CONFIG_EAP_EKE=y
# PKCS#12 (PFX) support (used to read private key and certificate file from
# a file that usually has extension .p12 or .pfx)
CONFIG_PKCS12=y
# Smartcard support (i.e., private key on a smartcard), e.g., with openssl
# engine.
CONFIG_SMARTCARD=y
# PC/SC interface for smartcards (USIM, GSM SIM)
# Enable this if EAP-SIM or EAP-AKA is included
#CONFIG_PCSC=y
# Support HT overrides (disable HT/HT40, mask MCS rates, etc.)
CONFIG_HT_OVERRIDES=y
# Support VHT overrides (disable VHT, mask MCS rates, etc.)
CONFIG_VHT_OVERRIDES=y
# Development testing
#CONFIG_EAPOL_TEST=y
# Select control interface backend for external programs, e.g, wpa_cli:
# unix = UNIX domain sockets (default for Linux/*BSD)
# udp = UDP sockets using localhost (127.0.0.1)
# udp6 = UDP IPv6 sockets using localhost (::1)
# named_pipe = Windows Named Pipe (default for Windows)
# udp-remote = UDP sockets with remote access (only for tests systems/purpose)
# udp6-remote = UDP IPv6 sockets with remote access (only for tests purpose)
# y = use default (backwards compatibility)
# If this option is commented out, control interface is not included in the
# build.
CONFIG_CTRL_IFACE=y
# Include support for GNU Readline and History Libraries in wpa_cli.
# When building a wpa_cli binary for distribution, please note that these
# libraries are licensed under GPL and as such, BSD license may not apply for
# the resulting binary.
#CONFIG_READLINE=y
# Include internal line edit mode in wpa_cli. This can be used as a replacement
# for GNU Readline to provide limited command line editing and history support.
#CONFIG_WPA_CLI_EDIT=y
# Remove debugging code that is printing out debug message to stdout.
# This can be used to reduce the size of the wpa_supplicant considerably
# if debugging code is not needed. The size reduction can be around 35%
# (e.g., 90 kB).
#CONFIG_NO_STDOUT_DEBUG=y
# Remove WPA support, e.g., for wired-only IEEE 802.1X supplicant, to save
# 35-50 kB in code size.
#CONFIG_NO_WPA=y
# Remove IEEE 802.11i/WPA-Personal ASCII passphrase support
# This option can be used to reduce code size by removing support for
# converting ASCII passphrases into PSK. If this functionality is removed, the
# PSK can only be configured as the 64-octet hexstring (e.g., from
# wpa_passphrase). This saves about 0.5 kB in code size.
#CONFIG_NO_WPA_PASSPHRASE=y
# Disable scan result processing (ap_mode=1) to save code size by about 1 kB.
# This can be used if ap_scan=1 mode is never enabled.
#CONFIG_NO_SCAN_PROCESSING=y
# Select configuration backend:
# file = text file (e.g., wpa_supplicant.conf; note: the configuration file
# path is given on command line, not here; this option is just used to
# select the backend that allows configuration files to be used)
# winreg = Windows registry (see win_example.reg for an example)
CONFIG_BACKEND=file
# Remove configuration write functionality (i.e., to allow the configuration
# file to be updated based on runtime configuration changes). The runtime
# configuration can still be changed, the changes are just not going to be
# persistent over restarts. This option can be used to reduce code size by
# about 3.5 kB.
#CONFIG_NO_CONFIG_WRITE=y
# Remove support for configuration blobs to reduce code size by about 1.5 kB.
#CONFIG_NO_CONFIG_BLOBS=y
# Select program entry point implementation:
# main = UNIX/POSIX like main() function (default)
# main_winsvc = Windows service (read parameters from registry)
# main_none = Very basic example (development use only)
#CONFIG_MAIN=main
# Select wrapper for operating system and C library specific functions
# unix = UNIX/POSIX like systems (default)
# win32 = Windows systems
# none = Empty template
#CONFIG_OS=unix
# Select event loop implementation
# eloop = select() loop (default)
# eloop_win = Windows events and WaitForMultipleObject() loop
#CONFIG_ELOOP=eloop
# Should we use poll instead of select? Select is used by default.
#CONFIG_ELOOP_POLL=y
# Should we use epoll instead of select? Select is used by default.
#CONFIG_ELOOP_EPOLL=y
# Select layer 2 packet implementation
# linux = Linux packet socket (default)
# pcap = libpcap/libdnet/WinPcap
# freebsd = FreeBSD libpcap
# winpcap = WinPcap with receive thread
# ndis = Windows NDISUIO (note: requires CONFIG_USE_NDISUIO=y)
# none = Empty template
#CONFIG_L2_PACKET=linux
# PeerKey handshake for Station to Station Link (IEEE 802.11e DLS)
CONFIG_PEERKEY=y
# IEEE 802.11w (management frame protection), also known as PMF
# Driver support is also needed for IEEE 802.11w.
CONFIG_IEEE80211W=y
# Select TLS implementation
# openssl = OpenSSL (default)
# gnutls = GnuTLS
# internal = Internal TLSv1 implementation (experimental)
# none = Empty template
#CONFIG_TLS=openssl
# TLS-based EAP methods require at least TLS v1.0. Newer version of TLS (v1.1)
# can be enabled to get a stronger construction of messages when block ciphers
# are used. It should be noted that some existing TLS v1.0 -based
# implementation may not be compatible with TLS v1.1 message (ClientHello is
# sent prior to negotiating which version will be used)
#CONFIG_TLSV11=y
# TLS-based EAP methods require at least TLS v1.0. Newer version of TLS (v1.2)
# can be enabled to enable use of stronger crypto algorithms. It should be
# noted that some existing TLS v1.0 -based implementation may not be compatible
# with TLS v1.2 message (ClientHello is sent prior to negotiating which version
# will be used)
#CONFIG_TLSV12=y
# If CONFIG_TLS=internal is used, additional library and include paths are
# needed for LibTomMath. Alternatively, an integrated, minimal version of
# LibTomMath can be used. See beginning of libtommath.c for details on benefits
# and drawbacks of this option.
#CONFIG_INTERNAL_LIBTOMMATH=y
#ifndef CONFIG_INTERNAL_LIBTOMMATH
#LTM_PATH=/usr/src/libtommath-0.39
#CFLAGS += -I$(LTM_PATH)
#LIBS += -L$(LTM_PATH)
#LIBS_p += -L$(LTM_PATH)
#endif
# At the cost of about 4 kB of additional binary size, the internal LibTomMath
# can be configured to include faster routines for exptmod, sqr, and div to
# speed up DH and RSA calculation considerably
#CONFIG_INTERNAL_LIBTOMMATH_FAST=y
# Include NDIS event processing through WMI into wpa_supplicant/wpasvc.
# This is only for Windows builds and requires WMI-related header files and
# WbemUuid.Lib from Platform SDK even when building with MinGW.
#CONFIG_NDIS_EVENTS_INTEGRATED=y
#PLATFORMSDKLIB="/opt/Program Files/Microsoft Platform SDK/Lib"
# Add support for old DBus control interface
# (fi.epitest.hostap.WPASupplicant)
#CONFIG_CTRL_IFACE_DBUS=y
# Add support for new DBus control interface
# (fi.w1.hostap.wpa_supplicant1)
#CONFIG_CTRL_IFACE_DBUS_NEW=y
# Add introspection support for new DBus control interface
#CONFIG_CTRL_IFACE_DBUS_INTRO=y
# Add support for loading EAP methods dynamically as shared libraries.
# When this option is enabled, each EAP method can be either included
# statically (CONFIG_EAP_<method>=y) or dynamically (CONFIG_EAP_<method>=dyn).
# Dynamic EAP methods are build as shared objects (eap_*.so) and they need to
# be loaded in the beginning of the wpa_supplicant configuration file
# (see load_dynamic_eap parameter in the example file) before being used in
# the network blocks.
#
# Note that some shared parts of EAP methods are included in the main program
# and in order to be able to use dynamic EAP methods using these parts, the
# main program must have been build with the EAP method enabled (=y or =dyn).
# This means that EAP-TLS/PEAP/TTLS/FAST cannot be added as dynamic libraries
# unless at least one of them was included in the main build to force inclusion
# of the shared code. Similarly, at least one of EAP-SIM/AKA must be included
# in the main build to be able to load these methods dynamically.
#
# Please also note that using dynamic libraries will increase the total binary
# size. Thus, it may not be the best option for targets that have limited
# amount of memory/flash.
#CONFIG_DYNAMIC_EAP_METHODS=y
# IEEE Std 802.11r-2008 (Fast BSS Transition)
#CONFIG_IEEE80211R=y
# Add support for writing debug log to a file (/tmp/wpa_supplicant-log-#.txt)
#CONFIG_DEBUG_FILE=y
# Send debug messages to syslog instead of stdout
#CONFIG_DEBUG_SYSLOG=y
# Set syslog facility for debug messages
#CONFIG_DEBUG_SYSLOG_FACILITY=LOG_DAEMON
# Add support for sending all debug messages (regardless of debug verbosity)
# to the Linux kernel tracing facility. This helps debug the entire stack by
# making it easy to record everything happening from the driver up into the
# same file, e.g., using trace-cmd.
#CONFIG_DEBUG_LINUX_TRACING=y
# Add support for writing debug log to Android logcat instead of standard
# output
#CONFIG_ANDROID_LOG=y
# Enable privilege separation (see README 'Privilege separation' for details)
#CONFIG_PRIVSEP=y
# Enable mitigation against certain attacks against TKIP by delaying Michael
# MIC error reports by a random amount of time between 0 and 60 seconds
#CONFIG_DELAYED_MIC_ERROR_REPORT=y
# Enable tracing code for developer debugging
# This tracks use of memory allocations and other registrations and reports
# incorrect use with a backtrace of call (or allocation) location.
#CONFIG_WPA_TRACE=y
# For BSD, uncomment these.
#LIBS += -lexecinfo
#LIBS_p += -lexecinfo
#LIBS_c += -lexecinfo
# Use libbfd to get more details for developer debugging
# This enables use of libbfd to get more detailed symbols for the backtraces
# generated by CONFIG_WPA_TRACE=y.
#CONFIG_WPA_TRACE_BFD=y
# For BSD, uncomment these.
#LIBS += -lbfd -liberty -lz
#LIBS_p += -lbfd -liberty -lz
#LIBS_c += -lbfd -liberty -lz
# wpa_supplicant depends on strong random number generation being available
# from the operating system. os_get_random() function is used to fetch random
# data when needed, e.g., for key generation. On Linux and BSD systems, this
# works by reading /dev/urandom. It should be noted that the OS entropy pool
# needs to be properly initialized before wpa_supplicant is started. This is
# important especially on embedded devices that do not have a hardware random
# number generator and may by default start up with minimal entropy available
# for random number generation.
#
# As a safety net, wpa_supplicant is by default trying to internally collect
# additional entropy for generating random data to mix in with the data fetched
# from the OS. This by itself is not considered to be very strong, but it may
# help in cases where the system pool is not initialized properly. However, it
# is very strongly recommended that the system pool is initialized with enough
# entropy either by using hardware assisted random number generator or by
# storing state over device reboots.
#
# wpa_supplicant can be configured to maintain its own entropy store over
# restarts to enhance random number generation. This is not perfect, but it is
# much more secure than using the same sequence of random numbers after every
# reboot. This can be enabled with -e<entropy file> command line option. The
# specified file needs to be readable and writable by wpa_supplicant.
#
# If the os_get_random() is known to provide strong random data (e.g., on
# Linux/BSD, the board in question is known to have reliable source of random
# data from /dev/urandom), the internal wpa_supplicant random pool can be
# disabled. This will save some in binary size and CPU use. However, this
# should only be considered for builds that are known to be used on devices
# that meet the requirements described above.
#CONFIG_NO_RANDOM_POOL=y
# IEEE 802.11n (High Throughput) support (mainly for AP mode)
CONFIG_IEEE80211N=y
# IEEE 802.11ac (Very High Throughput) support (mainly for AP mode)
# (depends on CONFIG_IEEE80211N)
CONFIG_IEEE80211AC=y
# Wireless Network Management (IEEE Std 802.11v-2011)
# Note: This is experimental and not complete implementation.
#CONFIG_WNM=y
# Interworking (IEEE 802.11u)
# This can be used to enable functionality to improve interworking with
# external networks (GAS/ANQP to learn more about the networks and network
# selection based on available credentials).
#CONFIG_INTERWORKING=y
# Hotspot 2.0
#CONFIG_HS20=y
# Disable roaming in wpa_supplicant
#CONFIG_NO_ROAMING=y
# AP mode operations with wpa_supplicant
# This can be used for controlling AP mode operations with wpa_supplicant. It
# should be noted that this is mainly aimed at simple cases like
# WPA2-Personal while more complex configurations like WPA2-Enterprise with an
# external RADIUS server can be supported with hostapd.
#CONFIG_AP=y
# P2P (Wi-Fi Direct)
# This can be used to enable P2P support in wpa_supplicant. See README-P2P for
# more information on P2P operations.
#CONFIG_P2P=y
# Enable TDLS support
#CONFIG_TDLS=y
# Wi-Fi Direct
# This can be used to enable Wi-Fi Direct extensions for P2P using an external
# program to control the additional information exchanges in the messages.
#CONFIG_WIFI_DISPLAY=y
# Autoscan
# This can be used to enable automatic scan support in wpa_supplicant.
# See wpa_supplicant.conf for more information on autoscan usage.
#
# Enabling directly a module will enable autoscan support.
# For exponential module:
#CONFIG_AUTOSCAN_EXPONENTIAL=y
# For periodic module:
#CONFIG_AUTOSCAN_PERIODIC=y
# Password (and passphrase, etc.) backend for external storage
# These optional mechanisms can be used to add support for storing passwords
# and other secrets in external (to wpa_supplicant) location. This allows, for
# example, operating system specific key storage to be used
#
# External password backend for testing purposes (developer use)
#CONFIG_EXT_PASSWORD_TEST=y
[-- Attachment #4: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2015-09-18 6:29 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-09-08 21:31 WLE600VX from PCEngines Marcel H.
[not found] ` <CABkMH_pegBjg987d5Bs_xkGqk1fsYAZqjSVWorNzPnL_L7PhDw@mail.gmail.com>
2015-09-09 4:10 ` Tomasz Skapski
2015-09-09 5:50 ` Janusz Dziedzic
2015-09-09 6:20 ` Jorge Baranda
2015-09-09 7:43 ` Janusz Dziedzic
2015-09-09 7:49 ` Marcel H.
2015-09-09 9:46 ` Marcel H.
2015-09-09 10:59 ` Harms, Hannes
2015-09-09 11:08 ` Janusz Dziedzic
2015-09-09 11:08 ` [SPAM] " Jorge Baranda
2015-09-09 11:14 ` Ben Greear
2015-09-09 11:15 ` Harms, Hannes
2015-09-09 11:34 ` Marcel H.
2015-09-09 11:40 ` Marcel H.
2015-09-09 18:22 ` Ben Greear
2015-09-17 10:27 ` [SPAM] " Jorge Baranda
2015-09-17 15:39 ` Jorge Baranda
2015-09-17 16:02 ` Marcel H.
2015-09-17 16:11 ` Ben Greear
2015-09-18 6:29 ` Jorge Baranda
2015-09-09 11:09 ` Janusz Dziedzic
2015-09-09 11:06 ` Janusz Dziedzic
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.