[SPAM] Re: [SPAM] Re: WLE600VX from PCEngines
Jorge Baranda
jbaranda at cttc.es
Thu Sep 17 03:27:28 PDT 2015
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 at 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 at blava.net> wrote:
>>>>> Thanks for the response, unfortunately this is the result of defining
>>>>> the center frequency:
>>>>>
>>>>> root at 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 at 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 at 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 at 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 at voyage1:/opt/ca_node/etc# wpa_supplicant -v
>>>>> wpa_supplicant v2.3
>>>>> Copyright (c) 2003-2014, Jouni Malinen <j at w1.fi> and contributors
>>>>>
>>>>>
>>>>> Re. the regulatory settings:
>>>>>
>>>>> root at 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 at tieto.com> wrote:
>>>>>> On 9 September 2015 at 08:20, Jorge Baranda <jbaranda at 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 at 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 at voyage2:/opt/ca_node/bin# iw dev wlan0 set freq 5745 80
>>>>>>>>> command failed: Invalid argument (-22)
>>>>>>>>> root at voyage2:/opt/ca_node/bin# ip link set wlan0 down
>>>>>>>>> root at 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 at 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 at 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 at 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 at lists.infradead.org
>>>>>>>>> http://lists.infradead.org/mailman/listinfo/ath10k
>>>>>>>> _______________________________________________
>>>>>>>> ath10k mailing list
>>>>>>>> ath10k at lists.infradead.org
>>>>>>>> http://lists.infradead.org/mailman/listinfo/ath10k
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Jorge Baranda
>>>>>>> Research Engineer, MSc
>>>>>>> jorge.baranda at 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 at lists.infradead.org
>>>>>>> http://lists.infradead.org/mailman/listinfo/ath10k
>>>>>> _______________________________________________
>>>>>> ath10k mailing list
>>>>>> ath10k at 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 at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant.log
Type: text/x-log
Size: 5465 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/ath10k/attachments/20150917/1b4dc5fd/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wpa_supplicant2.log
Type: text/x-log
Size: 3795 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/ath10k/attachments/20150917/1b4dc5fd/attachment-0003.bin>
More information about the ath10k
mailing list