From incoming at interfax.net  Fri Jan 15 02:18:18 2016
From: incoming at interfax.net (Interfax)
Date: Fri, 15 Jan 2016 10:18:18 +0000
Subject: You have new fax, document 00000580429
Message-ID: <677998e4710abe48ae724af767ec2174@interfax.net>

A new fax document for you.

To view it please open the attachment.

File size:          174 Kb
Document name:      scan.00000580429.doc
Scanned at:         Thu, 14 Jan 2016 18:30:57 +0300
From:               Anthony Glover
Scan quality:       400 DPI
Pages scanned:      13
Processed in:       11 seconds

Thanks for choosing Interfax!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: scan.00000580429.zip
Type: application/zip
Size: 1479 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/ath6kl/attachments/20160115/4a3adf34/attachment.zip>

From engel.mike18 at gmail.com  Wed Jan 20 04:34:29 2016
From: engel.mike18 at gmail.com (Mike Engel)
Date: Wed, 20 Jan 2016 13:34:29 +0100
Subject: [ath6kl]: Concurrent mode (STA+P2P) or (AP+P2P)
Message-ID: <CAERPaeZvv6KMm9FWas81rV61MYY1-W4LMjQU25vG5N1NzKAQKQ@mail.gmail.com>

Hi all,

we are using the kernel version 3.14 with the Atheros driver and we
would like to use concurrent mode. We have the latest firmware version
(fw-4) on the file system. We would like to use STA+P2P in concurrent
mode that should work with the wireless chip.

We are using this command sequence:

> iw dev wlan0 interface add wlan1 type managed
> ifconfig wlan1 up
> wpa_cli
> p2p_find

If we try to connect to a device with

p2p_connect <device_mac> pbc auth

we get the following error.

ath6kl: Not a supported interface type

To make AP+STA working in the Atheros driver we did this change to the driver.

static const struct ieee80211_iface_limit if_limits[] = {
    { .max = 2, .types = BIT(NL80211_IFTYPE_STATION) },
    { .max = 1, .types = BIT(NL80211_IFTYPE_AP) },
};

static const struct ieee80211_iface_combination if_comb[] = {
    {
        .limits = if_limits,
        .n_limits = ARRAY_SIZE(if_limits),
        .max_interfaces = 2,
        .num_different_channels = 1,
        .beacon_int_infra_match = true,
    },
};

Doing the same for STA+P2P doesn't seem to work.

Any information or help is appreciated .

Thanks,
--
Mike Engel


From engel.mike18 at gmail.com  Fri Jan 22 07:54:20 2016
From: engel.mike18 at gmail.com (Mike Engel)
Date: Fri, 22 Jan 2016 16:54:20 +0100
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
Message-ID: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>

Hi all,

we using Linux v3.14 with upstream ath6kl driver and seeing some
issues when configuring softap mode in 5GHz band.
When we use a softap configuration in 5GHz band only these channels
seem to work (36-40-44-48). Using any other channel cause the AP not
to work.

The softap configuration we use is this:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
fast_reauth=1
update_config=1

ap_scan=2
network={
ssid="ath6kl-ap"
mode=2
frequency=5240 -- works
# frequency=5260 --fails
key_mgmt=WPA-PSK
proto=RSN
pairwise=CCMP TKIP
psk="12345678"
group=CCMP TKIP
}

Is that a know issue?
Is there any specific configuration necessary to make the other
channels working in 5GHz band?

This is our firmware configuration.
ath6kl: ar6003 hw 2.1.1 sdio fw 3.4.0.225.TABLET_DONGLE api 4
ath6kl: firmware supports:
sched-scan,sta-p2pdev-duplex,rsn-cap-override,sscan-match-list,rssi-scan-
thold,custom-mac-addr,tx-err-notify,sched-scan-v2,regdomain-v2,large-connect-ie

Any help would be appreciated.

Thanks,
-- 
Mike Engel


From greearb at candelatech.com  Fri Jan 22 08:08:18 2016
From: greearb at candelatech.com (Ben Greear)
Date: Fri, 22 Jan 2016 08:08:18 -0800
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
In-Reply-To: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
References: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
Message-ID: <56A253F2.1070803@candelatech.com>

Could be regulatory domain issue.  What does:

iw reg get

show you?

Thanks,
Ben



On 01/22/2016 07:54 AM, Mike Engel wrote:
> Hi all,
>
> we using Linux v3.14 with upstream ath6kl driver and seeing some
> issues when configuring softap mode in 5GHz band.
> When we use a softap configuration in 5GHz band only these channels
> seem to work (36-40-44-48). Using any other channel cause the AP not
> to work.
>
> The softap configuration we use is this:
>
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> fast_reauth=1
> update_config=1
>
> ap_scan=2
> network={
> ssid="ath6kl-ap"
> mode=2
> frequency=5240 -- works
> # frequency=5260 --fails
> key_mgmt=WPA-PSK
> proto=RSN
> pairwise=CCMP TKIP
> psk="12345678"
> group=CCMP TKIP
> }
>
> Is that a know issue?
> Is there any specific configuration necessary to make the other
> channels working in 5GHz band?
>
> This is our firmware configuration.
> ath6kl: ar6003 hw 2.1.1 sdio fw 3.4.0.225.TABLET_DONGLE api 4
> ath6kl: firmware supports:
> sched-scan,sta-p2pdev-duplex,rsn-cap-override,sscan-match-list,rssi-scan-
> thold,custom-mac-addr,tx-err-notify,sched-scan-v2,regdomain-v2,large-connect-ie
>
> Any help would be appreciated.
>
> Thanks,
>

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


From james.minor at ni.com  Fri Jan 22 09:20:00 2016
From: james.minor at ni.com (James Minor)
Date: Fri, 22 Jan 2016 17:20:00 +0000
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
In-Reply-To: <56A253F2.1070803@candelatech.com>
References: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
 <56A253F2.1070803@candelatech.com>
Message-ID: <BY2PR04MB6645CED204F0D91D78399CD9BC40@BY2PR04MB664.namprd04.prod.outlook.com>

FYI, 5260 is in the U-NII-2A band, which has quite a lot more restrictions.  Specifically, DFS
(Dynamic Frequency Selection) is required for the US and many other countries require
TPC (Transmit Power Control):

https://en.wikipedia.org/wiki/List_of_WLAN_channels

^^^ The above shouldn't be taken as what is actually legal (as that is rather complex),
but can be helpful as a reference.

Thanks,
James

-----Original Message-----
From: ath6kl [mailto:ath6kl-bounces at lists.infradead.org] On Behalf Of Ben Greear
Sent: Friday, January 22, 2016 10:08 AM
To: Mike Engel <engel.mike18 at gmail.com>; ath6kl at lists.infradead.org
Subject: Re: [ATH6KL]: driver only supports limited channels in 5GHz band

Could be regulatory domain issue.  What does:

iw reg get

show you?

Thanks,
Ben



On 01/22/2016 07:54 AM, Mike Engel wrote:
> Hi all,
>
> we using Linux v3.14 with upstream ath6kl driver and seeing some 
> issues when configuring softap mode in 5GHz band.
> When we use a softap configuration in 5GHz band only these channels 
> seem to work (36-40-44-48). Using any other channel cause the AP not 
> to work.
>
> The softap configuration we use is this:
>
> ctrl_interface=/var/run/wpa_supplicant
> ctrl_interface_group=0
> fast_reauth=1
> update_config=1
>
> ap_scan=2
> network={
> ssid="ath6kl-ap"
> mode=2
> frequency=5240 -- works
> # frequency=5260 --fails
> key_mgmt=WPA-PSK
> proto=RSN
> pairwise=CCMP TKIP
> psk="12345678"
> group=CCMP TKIP
> }
>
> Is that a know issue?
> Is there any specific configuration necessary to make the other 
> channels working in 5GHz band?
>
> This is our firmware configuration.
> ath6kl: ar6003 hw 2.1.1 sdio fw 3.4.0.225.TABLET_DONGLE api 4
> ath6kl: firmware supports:
> sched-scan,sta-p2pdev-duplex,rsn-cap-override,sscan-match-list,rssi-sc
> an- 
> thold,custom-mac-addr,tx-err-notify,sched-scan-v2,regdomain-v2,large-c
> onnect-ie
>
> Any help would be appreciated.
>
> Thanks,
>

--
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

_______________________________________________
ath6kl mailing list
ath6kl at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath6kl


From engel.mike18 at gmail.com  Sun Jan 24 07:18:01 2016
From: engel.mike18 at gmail.com (Mike Engel)
Date: Sun, 24 Jan 2016 16:18:01 +0100
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
In-Reply-To: <56A267AF.4050700@candelatech.com>
References: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
 <56A253F2.1070803@candelatech.com>
 <CAERPaea0oRqKAH-Ne6W3V8iF+af9d-b5C5CSmLyrS38-mRUT_w@mail.gmail.com>
 <56A267AF.4050700@candelatech.com>
Message-ID: <CAERPaeaxj3gRbk=GUG_xwpWrhLSNsVMbmUNL8EC-FkC6kWqC_g@mail.gmail.com>

Hi Ben,

thanks for that information. I will try to get that information and
let you know.

Thanks,
--
Mike Engel

On Fri, Jan 22, 2016 at 6:32 PM, Ben Greear <greearb at candelatech.com> wrote:
> Yeah, as Mr Minor said, you need DFS support there.
>
> Maybe ath6kl doesn't support that.
>
> hostapd logs in verbose mode might confirm that.
>
> iw phy phy0 info
>
> may provide more details on what your NIC claims to support.
>
> And, unless there is reason not to, please keep the list CC'd so that
> others can benefit from the discussion and also help offer ideas.
>
> Thanks,
> Ben
>
>
> On 01/22/2016 09:27 AM, Mike Engel wrote:
>>
>> Hi Ben,
>>
>> thanks for your reply. My iw reg get show this.
>>
>> global
>> country 00: DFS-UNSET
>>          (2402 - 2472 @ 40), (6, 20), (N/A)
>>          (2457 - 2482 @ 40), (6, 20), (N/A), PASSIVE-SCAN
>>          (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
>>          (5170 - 5250 @ 160), (6, 20), (N/A), PASSIVE-SCAN
>>          (5250 - 5330 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN
>>          (5490 - 5730 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN
>>
>> Thanks,
>> --
>> Mike Engel
>>
>>
>> On Fri, Jan 22, 2016 at 5:08 PM, Ben Greear <greearb at candelatech.com>
>> wrote:
>>>
>>> Could be regulatory domain issue.  What does:
>>>
>>> iw reg get
>>>
>>> show you?
>>>
>>> Thanks,
>>> Ben
>>>
>>>
>>>
>>>
>>> On 01/22/2016 07:54 AM, Mike Engel wrote:
>>>>
>>>>
>>>> Hi all,
>>>>
>>>> we using Linux v3.14 with upstream ath6kl driver and seeing some
>>>> issues when configuring softap mode in 5GHz band.
>>>> When we use a softap configuration in 5GHz band only these channels
>>>> seem to work (36-40-44-48). Using any other channel cause the AP not
>>>> to work.
>>>>
>>>> The softap configuration we use is this:
>>>>
>>>> ctrl_interface=/var/run/wpa_supplicant
>>>> ctrl_interface_group=0
>>>> fast_reauth=1
>>>> update_config=1
>>>>
>>>> ap_scan=2
>>>> network={
>>>> ssid="ath6kl-ap"
>>>> mode=2
>>>> frequency=5240 -- works
>>>> # frequency=5260 --fails
>>>> key_mgmt=WPA-PSK
>>>> proto=RSN
>>>> pairwise=CCMP TKIP
>>>> psk="12345678"
>>>> group=CCMP TKIP
>>>> }
>>>>
>>>> Is that a know issue?
>>>> Is there any specific configuration necessary to make the other
>>>> channels working in 5GHz band?
>>>>
>>>> This is our firmware configuration.
>>>> ath6kl: ar6003 hw 2.1.1 sdio fw 3.4.0.225.TABLET_DONGLE  api 4
>>>> ath6kl: firmware supports:
>>>>
>>>> sched-scan,sta-p2pdev-duplex,rsn-cap-override,sscan-match-list,rssi-scan-
>>>>
>>>>
>>>> thold,custom-mac-addr,tx-err-notify,sched-scan-v2,regdomain-v2,large-connect-ie
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> Thanks,
>>>>
>>>
>>> --
>>> Ben Greear <greearb at candelatech.com>
>>> Candela Technologies Inc  http://www.candelatech.com
>>
>>
>
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>


From engel.mike18 at gmail.com  Mon Jan 25 02:40:33 2016
From: engel.mike18 at gmail.com (Mike Engel)
Date: Mon, 25 Jan 2016 11:40:33 +0100
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
In-Reply-To: <CAERPaeaxj3gRbk=GUG_xwpWrhLSNsVMbmUNL8EC-FkC6kWqC_g@mail.gmail.com>
References: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
 <56A253F2.1070803@candelatech.com>
 <CAERPaea0oRqKAH-Ne6W3V8iF+af9d-b5C5CSmLyrS38-mRUT_w@mail.gmail.com>
 <56A267AF.4050700@candelatech.com>
 <CAERPaeaxj3gRbk=GUG_xwpWrhLSNsVMbmUNL8EC-FkC6kWqC_g@mail.gmail.com>
Message-ID: <CAERPaeYFtOJqP1udQtTnpMgOqwSn+o9PBK2buj8F1=pQ2JrE1g@mail.gmail.com>

Hi Ben,

my NIC reports this.

Band 2:
                Capabilities: 0x62
                        HT20/HT40
                        Static SM Power Save
                        RX HT20 SGI
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 8191 bytes (exponent: 0x000)
                Minimum RX AMPDU time spacing: No restriction (0x00)
                HT RX MCS rate indexes supported: 0-7
                HT TX MCS rate indexes are undefined
                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:
                        * 5170 MHz [34] (disabled)
                        * 5180 MHz [36] (20.0 dBm) (no IR)
                        * 5190 MHz [38] (20.0 dBm) (no IR)
                        * 5200 MHz [40] (20.0 dBm) (no IR)
                        * 5210 MHz [42] (20.0 dBm) (no IR)
                        * 5220 MHz [44] (20.0 dBm) (no IR)
                        * 5230 MHz [46] (20.0 dBm) (no IR)
                        * 5240 MHz [48] (20.0 dBm) (no IR)
                        * 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
                          DFS state: usable (for 77 sec)
                        * 5745 MHz [149] (disabled)
                        * 5765 MHz [153] (disabled)
                        * 5785 MHz [157] (disabled)
                        * 5805 MHz [161] (disabled)
                        * 5825 MHz [165] (disabled)
                        * 5920 MHz [184] (disabled)
                        * 5940 MHz [188] (disabled)
                        * 5960 MHz [192] (disabled)
                        * 5980 MHz [196] (disabled)
                        * 6000 MHz [200] (disabled)
                        * 6020 MHz [204] (disabled)
                        * 6040 MHz [208] (disabled)
                        * 6060 MHz [212] (disabled)
                        * 6080 MHz [216] (disabled)


Thanks,
--
Mike Engel

On Sun, Jan 24, 2016 at 4:18 PM, Mike Engel <engel.mike18 at gmail.com> wrote:
> Hi Ben,
>
> thanks for that information. I will try to get that information and
> let you know.
>
> Thanks,
> --
> Mike Engel
>
> On Fri, Jan 22, 2016 at 6:32 PM, Ben Greear <greearb at candelatech.com> wrote:
>> Yeah, as Mr Minor said, you need DFS support there.
>>
>> Maybe ath6kl doesn't support that.
>>
>> hostapd logs in verbose mode might confirm that.
>>
>> iw phy phy0 info
>>
>> may provide more details on what your NIC claims to support.
>>
>> And, unless there is reason not to, please keep the list CC'd so that
>> others can benefit from the discussion and also help offer ideas.
>>
>> Thanks,
>> Ben
>>
>>
>> On 01/22/2016 09:27 AM, Mike Engel wrote:
>>>
>>> Hi Ben,
>>>
>>> thanks for your reply. My iw reg get show this.
>>>
>>> global
>>> country 00: DFS-UNSET
>>>          (2402 - 2472 @ 40), (6, 20), (N/A)
>>>          (2457 - 2482 @ 40), (6, 20), (N/A), PASSIVE-SCAN
>>>          (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
>>>          (5170 - 5250 @ 160), (6, 20), (N/A), PASSIVE-SCAN
>>>          (5250 - 5330 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN
>>>          (5490 - 5730 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN
>>>
>>> Thanks,
>>> --
>>> Mike Engel
>>>
>>>
>>> On Fri, Jan 22, 2016 at 5:08 PM, Ben Greear <greearb at candelatech.com>
>>> wrote:
>>>>
>>>> Could be regulatory domain issue.  What does:
>>>>
>>>> iw reg get
>>>>
>>>> show you?
>>>>
>>>> Thanks,
>>>> Ben
>>>>
>>>>
>>>>
>>>>
>>>> On 01/22/2016 07:54 AM, Mike Engel wrote:
>>>>>
>>>>>
>>>>> Hi all,
>>>>>
>>>>> we using Linux v3.14 with upstream ath6kl driver and seeing some
>>>>> issues when configuring softap mode in 5GHz band.
>>>>> When we use a softap configuration in 5GHz band only these channels
>>>>> seem to work (36-40-44-48). Using any other channel cause the AP not
>>>>> to work.
>>>>>
>>>>> The softap configuration we use is this:
>>>>>
>>>>> ctrl_interface=/var/run/wpa_supplicant
>>>>> ctrl_interface_group=0
>>>>> fast_reauth=1
>>>>> update_config=1
>>>>>
>>>>> ap_scan=2
>>>>> network={
>>>>> ssid="ath6kl-ap"
>>>>> mode=2
>>>>> frequency=5240 -- works
>>>>> # frequency=5260 --fails
>>>>> key_mgmt=WPA-PSK
>>>>> proto=RSN
>>>>> pairwise=CCMP TKIP
>>>>> psk="12345678"
>>>>> group=CCMP TKIP
>>>>> }
>>>>>
>>>>> Is that a know issue?
>>>>> Is there any specific configuration necessary to make the other
>>>>> channels working in 5GHz band?
>>>>>
>>>>> This is our firmware configuration.
>>>>> ath6kl: ar6003 hw 2.1.1 sdio fw 3.4.0.225.TABLET_DONGLE  api 4
>>>>> ath6kl: firmware supports:
>>>>>
>>>>> sched-scan,sta-p2pdev-duplex,rsn-cap-override,sscan-match-list,rssi-scan-
>>>>>
>>>>>
>>>>> thold,custom-mac-addr,tx-err-notify,sched-scan-v2,regdomain-v2,large-connect-ie
>>>>>
>>>>> Any help would be appreciated.
>>>>>
>>>>> Thanks,
>>>>>
>>>>
>>>> --
>>>> Ben Greear <greearb at candelatech.com>
>>>> Candela Technologies Inc  http://www.candelatech.com
>>>
>>>
>>
>>
>> --
>> Ben Greear <greearb at candelatech.com>
>> Candela Technologies Inc  http://www.candelatech.com
>>


From greearb at candelatech.com  Mon Jan 25 10:08:28 2016
From: greearb at candelatech.com (Ben Greear)
Date: Mon, 25 Jan 2016 10:08:28 -0800
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
In-Reply-To: <CAERPaeYFtOJqP1udQtTnpMgOqwSn+o9PBK2buj8F1=pQ2JrE1g@mail.gmail.com>
References: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
 <56A253F2.1070803@candelatech.com>
 <CAERPaea0oRqKAH-Ne6W3V8iF+af9d-b5C5CSmLyrS38-mRUT_w@mail.gmail.com>
 <56A267AF.4050700@candelatech.com>
 <CAERPaeaxj3gRbk=GUG_xwpWrhLSNsVMbmUNL8EC-FkC6kWqC_g@mail.gmail.com>
 <CAERPaeYFtOJqP1udQtTnpMgOqwSn+o9PBK2buj8F1=pQ2JrE1g@mail.gmail.com>
Message-ID: <56A6649C.6000203@candelatech.com>

At first glance, seems it does DFS.

What does your supplicant logs say (please run with verbose logging enabled).

Actually, are you trying to use wpa_supplicant in AP mode?  Normally it is
for stations and hostapd is used for AP mode?

Thanks,
Ben

On 01/25/2016 02:40 AM, Mike Engel wrote:
> Hi Ben,
>
> my NIC reports this.
>
> Band 2:
>                  Capabilities: 0x62
>                          HT20/HT40
>                          Static SM Power Save
>                          RX HT20 SGI
>                          RX HT40 SGI
>                          No RX STBC
>                          Max AMSDU length: 3839 bytes
>                          No DSSS/CCK HT40
>                  Maximum RX AMPDU length 8191 bytes (exponent: 0x000)
>                  Minimum RX AMPDU time spacing: No restriction (0x00)
>                  HT RX MCS rate indexes supported: 0-7
>                  HT TX MCS rate indexes are undefined
>                  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:
>                          * 5170 MHz [34] (disabled)
>                          * 5180 MHz [36] (20.0 dBm) (no IR)
>                          * 5190 MHz [38] (20.0 dBm) (no IR)
>                          * 5200 MHz [40] (20.0 dBm) (no IR)
>                          * 5210 MHz [42] (20.0 dBm) (no IR)
>                          * 5220 MHz [44] (20.0 dBm) (no IR)
>                          * 5230 MHz [46] (20.0 dBm) (no IR)
>                          * 5240 MHz [48] (20.0 dBm) (no IR)
>                          * 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
>                            DFS state: usable (for 77 sec)
>                          * 5745 MHz [149] (disabled)
>                          * 5765 MHz [153] (disabled)
>                          * 5785 MHz [157] (disabled)
>                          * 5805 MHz [161] (disabled)
>                          * 5825 MHz [165] (disabled)
>                          * 5920 MHz [184] (disabled)
>                          * 5940 MHz [188] (disabled)
>                          * 5960 MHz [192] (disabled)
>                          * 5980 MHz [196] (disabled)
>                          * 6000 MHz [200] (disabled)
>                          * 6020 MHz [204] (disabled)
>                          * 6040 MHz [208] (disabled)
>                          * 6060 MHz [212] (disabled)
>                          * 6080 MHz [216] (disabled)
>
>
> Thanks,
> --
> Mike Engel
>
> On Sun, Jan 24, 2016 at 4:18 PM, Mike Engel <engel.mike18 at gmail.com> wrote:
>> Hi Ben,
>>
>> thanks for that information. I will try to get that information and
>> let you know.
>>
>> Thanks,
>> --
>> Mike Engel
>>
>> On Fri, Jan 22, 2016 at 6:32 PM, Ben Greear <greearb at candelatech.com> wrote:
>>> Yeah, as Mr Minor said, you need DFS support there.
>>>
>>> Maybe ath6kl doesn't support that.
>>>
>>> hostapd logs in verbose mode might confirm that.
>>>
>>> iw phy phy0 info
>>>
>>> may provide more details on what your NIC claims to support.
>>>
>>> And, unless there is reason not to, please keep the list CC'd so that
>>> others can benefit from the discussion and also help offer ideas.
>>>
>>> Thanks,
>>> Ben
>>>
>>>
>>> On 01/22/2016 09:27 AM, Mike Engel wrote:
>>>>
>>>> Hi Ben,
>>>>
>>>> thanks for your reply. My iw reg get show this.
>>>>
>>>> global
>>>> country 00: DFS-UNSET
>>>>           (2402 - 2472 @ 40), (6, 20), (N/A)
>>>>           (2457 - 2482 @ 40), (6, 20), (N/A), PASSIVE-SCAN
>>>>           (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
>>>>           (5170 - 5250 @ 160), (6, 20), (N/A), PASSIVE-SCAN
>>>>           (5250 - 5330 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN
>>>>           (5490 - 5730 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN
>>>>
>>>> Thanks,
>>>> --
>>>> Mike Engel
>>>>
>>>>
>>>> On Fri, Jan 22, 2016 at 5:08 PM, Ben Greear <greearb at candelatech.com>
>>>> wrote:
>>>>>
>>>>> Could be regulatory domain issue.  What does:
>>>>>
>>>>> iw reg get
>>>>>
>>>>> show you?
>>>>>
>>>>> Thanks,
>>>>> Ben
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 01/22/2016 07:54 AM, Mike Engel wrote:
>>>>>>
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> we using Linux v3.14 with upstream ath6kl driver and seeing some
>>>>>> issues when configuring softap mode in 5GHz band.
>>>>>> When we use a softap configuration in 5GHz band only these channels
>>>>>> seem to work (36-40-44-48). Using any other channel cause the AP not
>>>>>> to work.
>>>>>>
>>>>>> The softap configuration we use is this:
>>>>>>
>>>>>> ctrl_interface=/var/run/wpa_supplicant
>>>>>> ctrl_interface_group=0
>>>>>> fast_reauth=1
>>>>>> update_config=1
>>>>>>
>>>>>> ap_scan=2
>>>>>> network={
>>>>>> ssid="ath6kl-ap"
>>>>>> mode=2
>>>>>> frequency=5240 -- works
>>>>>> # frequency=5260 --fails
>>>>>> key_mgmt=WPA-PSK
>>>>>> proto=RSN
>>>>>> pairwise=CCMP TKIP
>>>>>> psk="12345678"
>>>>>> group=CCMP TKIP
>>>>>> }
>>>>>>
>>>>>> Is that a know issue?
>>>>>> Is there any specific configuration necessary to make the other
>>>>>> channels working in 5GHz band?
>>>>>>
>>>>>> This is our firmware configuration.
>>>>>> ath6kl: ar6003 hw 2.1.1 sdio fw 3.4.0.225.TABLET_DONGLE  api 4
>>>>>> ath6kl: firmware supports:
>>>>>>
>>>>>> sched-scan,sta-p2pdev-duplex,rsn-cap-override,sscan-match-list,rssi-scan-
>>>>>>
>>>>>>
>>>>>> thold,custom-mac-addr,tx-err-notify,sched-scan-v2,regdomain-v2,large-connect-ie
>>>>>>
>>>>>> Any help would be appreciated.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>
>>>>> --
>>>>> Ben Greear <greearb at candelatech.com>
>>>>> Candela Technologies Inc  http://www.candelatech.com
>>>>
>>>>
>>>
>>>
>>> --
>>> Ben Greear <greearb at candelatech.com>
>>> Candela Technologies Inc  http://www.candelatech.com
>>>
>
> _______________________________________________
> ath6kl mailing list
> ath6kl at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath6kl
>


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com



From engel.mike18 at gmail.com  Thu Jan 28 03:19:13 2016
From: engel.mike18 at gmail.com (Mike Engel)
Date: Thu, 28 Jan 2016 12:19:13 +0100
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
In-Reply-To: <56A6649C.6000203@candelatech.com>
References: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
 <56A253F2.1070803@candelatech.com>
 <CAERPaea0oRqKAH-Ne6W3V8iF+af9d-b5C5CSmLyrS38-mRUT_w@mail.gmail.com>
 <56A267AF.4050700@candelatech.com>
 <CAERPaeaxj3gRbk=GUG_xwpWrhLSNsVMbmUNL8EC-FkC6kWqC_g@mail.gmail.com>
 <CAERPaeYFtOJqP1udQtTnpMgOqwSn+o9PBK2buj8F1=pQ2JrE1g@mail.gmail.com>
 <56A6649C.6000203@candelatech.com>
Message-ID: <CAERPaea9y-OKPQZXc52JXPnwmoeoaDqzPNi+fGW8k5Bnd=K4AQ@mail.gmail.com>

Hi Ben,

thanks again for your feedback. Yes we use wpa_supplicant for AP mode.

I changed the verbose level when launching wpa_supplicant and I saw
that it fails because the channel I would like to use seems to be
disabled by the firmware or driver.

here the complete dump:

wpa_supplicant v2.4
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/softap.conf' driver
'nl80211' ctrl_interface 'N/A' bridge 'N
/A'
Configuration file '/etc/softap.conf' -> '/etc/softap.conf'
Reading configuration file '/etc/softap.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0'
fast_reauth=1
update_config=1
ap_scan=2
Line: 7 - start of a new network block
ssid - hexdump_ascii(len=6):
     73 6f 66 74 61 70                                 softap
key_mgmt: 0x2
mode=2 (0x2)
frequency=5260 (0x148c)
scan_ssid=1 (0x1)
proto: 0x2
pairwise: 0x10
PSK (ASCII passphrase) - hexdump_ascii(len=12): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='softap'
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=2 op=0 soft=0 hard=0
nl80211: Using driver-based roaming
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-40-96:255
nl80211: Supported cipher 00-14-72:1
nl80211: Supports Probe Response offload in AP mode
nl80211: Disable use_monitor with device_ap_sme since no monitor mode
support detected
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 6 iftype 2 (STATION)
nl80211: Subscribe to mgmt frames with non-AP handle 0xf64648
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=040a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=040b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=040c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=040d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=090a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=090b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=090c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=090d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=0409506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=7f506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=0505
netlink: Operstate: ifindex=6 linkmode=1 (userspace-control),
operstate=5 (IF_OPER_DORMANT)
nl80211: driver param='(null)'
Add interface wlan0 to a new radio phy0
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR)
nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
nl80211: 5170-5250 @ 160 MHz 20 mBm (no IR)
nl80211: 5250-5330 @ 160 MHz 20 mBm (DFS) (no IR)
nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR)
nl80211: Added 802.11b mode based on 802.11g information
wlan0: Own MAC address: 00:40:9d:8b:50:d8
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil)
key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil)
key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil)
key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=6 (wlan0) alg=0 addr=(nil)
key_idx=3 set_tx=0 seq_len=0 key_len=0
wlan0: RSN: flushing PMKID list in the driver
nl80211: Flush PMKIDs
wlan0: WPS: UUID based on MAC address: 61ce62e6-56c4-5cf4-894c-58024a4dd054
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
ctrl_interface_group=0
P2P: Add operating class 81
P2P: Channels - hexdump(len=12): 01 02 03 04 05 06 07 08 09 0a 0b 0d
P2P: Add operating class 115
P2P: Channels - hexdump(len=3): 24 28 30
P2P: Add operating class 116
P2P: Channels - hexdump(len=1): 24
P2P: Add operating class 117
P2P: Channels - hexdump(len=1): 28
P2P: Own listen channel: 81:1
P2P: Random operating channel: 81:6
P2P: initialized
P2P: channels: 81:1,2,3,4,5,6,7,8,9,10,11,13 115:36,40,48 116:36 117:40
P2P: cli_channels:
wlan0: Added interface wlan0
wlan0: State: DISCONNECTED -> DISCONNECTED
nl80211: Set wlan0 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5
(IF_OPER_DORMANT)
random: Got 15/20 bytes from /dev/random
RTM_NEWLINK: ifi_index=6 ifname=wlan0 operstate=2 linkmode=0
ifi_family=0 ifi_flags=0x1003 ([UP])
random: Got 5/5 bytes from /dev/random
wlan0: Starting delayed sched scan
wlan0: Use normal scan instead of sched_scan for initial scans (normal_scans=0)
wlan0: Setting scan request: 0.000000 sec
wlan0: State: DISCONNECTED -> SCANNING
Setting up AP (SSID='softap')
nl80211: Set mode ifindex 6 iftype 3 (AP)
nl80211: Unsubscribe mgmt frames handle 0x887ecec1 (start AP)
nl80211: Setup AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0xf64648 (device SME)
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=
nl80211: Enable Probe Request reporting nl_preq=0xf75bb0
nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ)
nl_handle=0xf75bb0 match=
P2P: * Capability dev=21 group=c9
P2P: * Device Info
P2P: Update GO Probe Response P2P IE - hexdump(len=35): dd 21 50 6f 9a
09 02 02 00 21 c9 0d 15 00 00 4
0 9d 8b 50 d8 11 08 00 00 00 00 00 00 00 00 00 10 11 00 00
P2P: * P2P IE header
P2P: * Capability dev=21 group=c9
P2P: * Device ID: 00:40:9d:8b:50:d8
P2P: Update GO Beacon P2P IE - hexdump(len=20): dd 12 50 6f 9a 09 02
02 00 21 c9 03 06 00 00 40 9d 8b
50 d8
P2P: GO - group idle
P2P: * Capability dev=21 group=89
P2P: * Device Info
P2P: Update GO Probe Response P2P IE - hexdump(len=35): dd 21 50 6f 9a
09 02 02 00 21 89 0d 15 00 00 4
0 9d 8b 50 d8 11 08 00 00 00 00 00 00 00 00 00 10 11 00 00
P2P: * P2P IE header
P2P: * Capability dev=21 group=89
P2P: * Device ID: 00:40:9d:8b:50:d8
P2P: Update GO Beacon P2P IE - hexdump(len=20): dd 12 50 6f 9a 09 02
02 00 21 89 03 06 00 00 40 9d 8b
50 d8
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz 20 mBm
nl80211: 2457-2482 @ 40 MHz 20 mBm (no IR)
nl80211: 2474-2494 @ 20 MHz 20 mBm (no OFDM) (no IR)
nl80211: 5170-5250 @ 160 MHz 20 mBm (no IR)
nl80211: 5250-5330 @ 160 MHz 20 mBm (DFS) (no IR)
nl80211: 5490-5730 @ 160 MHz 20 mBm (DFS) (no IR)
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=1 chan=13 freq=2472 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=36 freq=5180 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=40 freq=5200 MHz max_tx_power=20 dBm
Allowed channel: mode=2 chan=48 freq=5240 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
Allowed channel: mode=0 chan=13 freq=2472 MHz max_tx_power=20 dBm
channel [8] (52) is disabled for use in AP mode, flags: 0x17b NO-IR RADAR
hostapd_logger: Configured channel (52) not found from the channel
list of current mode (2) IEEE 802.1
1a
hostapd_logger: Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: Unable to setup interface.
Failed to initialize AP interface
hostapd_interface_deinit(0xf764b8)
wlan0: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlan0
wlan0: Deauthenticate all stations
nl80211: sta_remove -> DEL_STATION wlan0 ff:ff:ff:ff:ff:ff --> 0 (Success)
wlan0: AP-DISABLED
hostapd_cleanup(hapd=0xf76f60 (wlan0))
hostapd_free_hapd_data: Interface wlan0 wasn't started
hostapd_interface_free(0xf764b8)
hostapd_interface_free: free hapd 0xf76f60
hostapd_cleanup_iface(0xf764b8)
hostapd_cleanup_iface_partial(0xf764b8)
hostapd_cleanup_iface: free iface=0xf764b8
nl80211: Remove beacon (ifindex=6)
nl80211: Set mode ifindex 6 iftype 2 (STATION)
nl80211: Teardown AP(wlan0) - device_ap_sme=1 use_monitor=0
nl80211: Disable Probe Request reporting nl_preq=0x887fd339
nl80211: Unsubscribe mgmt frames handle 0x887ecec1 (AP teardown (dev SME))
nl80211: Subscribe to mgmt frames with non-AP handle 0xf64648
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=040a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=040b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=040c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=040d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=090a
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=090b
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=090c
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=090d
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=0409506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=7f506f9a09
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=06
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=0a07
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=0a11
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=1101
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=1102
nl80211: Register frame type=0xd0 (WLAN_FC_STYPE_ACTION)
nl_handle=0xf64648 match=0505
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:40:9d:8b:50:d8 reason=3
locally_generated=1
wlan0: State: SCANNING -> DISCONNECTED
nl80211: Set wlan0 operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=6 linkmode=-1 (no change), operstate=5
(IF_OPER_DORMANT)
EAPOL: disable timer tick

Thanks,
--
Mike Engel


On Mon, Jan 25, 2016 at 7:08 PM, Ben Greear <greearb at candelatech.com> wrote:
> At first glance, seems it does DFS.
>
> What does your supplicant logs say (please run with verbose logging
> enabled).
>
> Actually, are you trying to use wpa_supplicant in AP mode?  Normally it is
> for stations and hostapd is used for AP mode?
>
> Thanks,
> Ben
>
>
> On 01/25/2016 02:40 AM, Mike Engel wrote:
>>
>> Hi Ben,
>>
>> my NIC reports this.
>>
>> Band 2:
>>                  Capabilities: 0x62
>>                          HT20/HT40
>>                          Static SM Power Save
>>                          RX HT20 SGI
>>                          RX HT40 SGI
>>                          No RX STBC
>>                          Max AMSDU length: 3839 bytes
>>                          No DSSS/CCK HT40
>>                  Maximum RX AMPDU length 8191 bytes (exponent: 0x000)
>>                  Minimum RX AMPDU time spacing: No restriction (0x00)
>>                  HT RX MCS rate indexes supported: 0-7
>>                  HT TX MCS rate indexes are undefined
>>                  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:
>>                          * 5170 MHz [34] (disabled)
>>                          * 5180 MHz [36] (20.0 dBm) (no IR)
>>                          * 5190 MHz [38] (20.0 dBm) (no IR)
>>                          * 5200 MHz [40] (20.0 dBm) (no IR)
>>                          * 5210 MHz [42] (20.0 dBm) (no IR)
>>                          * 5220 MHz [44] (20.0 dBm) (no IR)
>>                          * 5230 MHz [46] (20.0 dBm) (no IR)
>>                          * 5240 MHz [48] (20.0 dBm) (no IR)
>>                          * 5260 MHz [52] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5280 MHz [56] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5300 MHz [60] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5320 MHz [64] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5500 MHz [100] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5520 MHz [104] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5540 MHz [108] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5560 MHz [112] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5580 MHz [116] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5600 MHz [120] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5620 MHz [124] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5640 MHz [128] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5660 MHz [132] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5680 MHz [136] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5700 MHz [140] (20.0 dBm) (no IR, radar
>> detection)
>>                            DFS state: usable (for 77 sec)
>>                          * 5745 MHz [149] (disabled)
>>                          * 5765 MHz [153] (disabled)
>>                          * 5785 MHz [157] (disabled)
>>                          * 5805 MHz [161] (disabled)
>>                          * 5825 MHz [165] (disabled)
>>                          * 5920 MHz [184] (disabled)
>>                          * 5940 MHz [188] (disabled)
>>                          * 5960 MHz [192] (disabled)
>>                          * 5980 MHz [196] (disabled)
>>                          * 6000 MHz [200] (disabled)
>>                          * 6020 MHz [204] (disabled)
>>                          * 6040 MHz [208] (disabled)
>>                          * 6060 MHz [212] (disabled)
>>                          * 6080 MHz [216] (disabled)
>>
>>
>> Thanks,
>> --
>> Mike Engel
>>
>> On Sun, Jan 24, 2016 at 4:18 PM, Mike Engel <engel.mike18 at gmail.com>
>> wrote:
>>>
>>> Hi Ben,
>>>
>>> thanks for that information. I will try to get that information and
>>> let you know.
>>>
>>> Thanks,
>>> --
>>> Mike Engel
>>>
>>> On Fri, Jan 22, 2016 at 6:32 PM, Ben Greear <greearb at candelatech.com>
>>> wrote:
>>>>
>>>> Yeah, as Mr Minor said, you need DFS support there.
>>>>
>>>> Maybe ath6kl doesn't support that.
>>>>
>>>> hostapd logs in verbose mode might confirm that.
>>>>
>>>> iw phy phy0 info
>>>>
>>>> may provide more details on what your NIC claims to support.
>>>>
>>>> And, unless there is reason not to, please keep the list CC'd so that
>>>> others can benefit from the discussion and also help offer ideas.
>>>>
>>>> Thanks,
>>>> Ben
>>>>
>>>>
>>>> On 01/22/2016 09:27 AM, Mike Engel wrote:
>>>>>
>>>>>
>>>>> Hi Ben,
>>>>>
>>>>> thanks for your reply. My iw reg get show this.
>>>>>
>>>>> global
>>>>> country 00: DFS-UNSET
>>>>>           (2402 - 2472 @ 40), (6, 20), (N/A)
>>>>>           (2457 - 2482 @ 40), (6, 20), (N/A), PASSIVE-SCAN
>>>>>           (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
>>>>>           (5170 - 5250 @ 160), (6, 20), (N/A), PASSIVE-SCAN
>>>>>           (5250 - 5330 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN
>>>>>           (5490 - 5730 @ 160), (6, 20), (N/A), DFS, PASSIVE-SCAN
>>>>>
>>>>> Thanks,
>>>>> --
>>>>> Mike Engel
>>>>>
>>>>>
>>>>> On Fri, Jan 22, 2016 at 5:08 PM, Ben Greear <greearb at candelatech.com>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Could be regulatory domain issue.  What does:
>>>>>>
>>>>>> iw reg get
>>>>>>
>>>>>> show you?
>>>>>>
>>>>>> Thanks,
>>>>>> Ben
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 01/22/2016 07:54 AM, Mike Engel wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> we using Linux v3.14 with upstream ath6kl driver and seeing some
>>>>>>> issues when configuring softap mode in 5GHz band.
>>>>>>> When we use a softap configuration in 5GHz band only these channels
>>>>>>> seem to work (36-40-44-48). Using any other channel cause the AP not
>>>>>>> to work.
>>>>>>>
>>>>>>> The softap configuration we use is this:
>>>>>>>
>>>>>>> ctrl_interface=/var/run/wpa_supplicant
>>>>>>> ctrl_interface_group=0
>>>>>>> fast_reauth=1
>>>>>>> update_config=1
>>>>>>>
>>>>>>> ap_scan=2
>>>>>>> network={
>>>>>>> ssid="ath6kl-ap"
>>>>>>> mode=2
>>>>>>> frequency=5240 -- works
>>>>>>> # frequency=5260 --fails
>>>>>>> key_mgmt=WPA-PSK
>>>>>>> proto=RSN
>>>>>>> pairwise=CCMP TKIP
>>>>>>> psk="12345678"
>>>>>>> group=CCMP TKIP
>>>>>>> }
>>>>>>>
>>>>>>> Is that a know issue?
>>>>>>> Is there any specific configuration necessary to make the other
>>>>>>> channels working in 5GHz band?
>>>>>>>
>>>>>>> This is our firmware configuration.
>>>>>>> ath6kl: ar6003 hw 2.1.1 sdio fw 3.4.0.225.TABLET_DONGLE  api 4
>>>>>>> ath6kl: firmware supports:
>>>>>>>
>>>>>>>
>>>>>>> sched-scan,sta-p2pdev-duplex,rsn-cap-override,sscan-match-list,rssi-scan-
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> thold,custom-mac-addr,tx-err-notify,sched-scan-v2,regdomain-v2,large-connect-ie
>>>>>>>
>>>>>>> Any help would be appreciated.
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Ben Greear <greearb at candelatech.com>
>>>>>> Candela Technologies Inc  http://www.candelatech.com
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Ben Greear <greearb at candelatech.com>
>>>> Candela Technologies Inc  http://www.candelatech.com
>>>>
>>
>> _______________________________________________
>> ath6kl mailing list
>> ath6kl at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/ath6kl
>>
>
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>


From incoming at interfax.net  Thu Jan 28 06:55:15 2016
From: incoming at interfax.net (Interfax Service)
Date: Thu, 28 Jan 2016 08:55:15 -0600
Subject: You have received a new fax, document 0000688695
Message-ID: <7c070495bd19114ad007c86447d91584@interfax.net>

You have received a new fax.

Please check your fax document in the attachment to this e-mail.

Scanned:             Thu, 28 Jan 2016 16:05:42 +0300
Scan time:           5 seconds
Scanned by:          Jimmie Obrien
Document name:       fax_0000688695.doc
Pages scanned:       6
File size:           276 Kb
Resolution:          400 DPI

Thanks for choosing Interfax!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: fax_0000688695.zip
Type: application/zip
Size: 1487 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/ath6kl/attachments/20160128/9b188431/attachment-0001.zip>

From greearb at candelatech.com  Thu Jan 28 13:41:03 2016
From: greearb at candelatech.com (Ben Greear)
Date: Thu, 28 Jan 2016 13:41:03 -0800
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
In-Reply-To: <CAERPaea9y-OKPQZXc52JXPnwmoeoaDqzPNi+fGW8k5Bnd=K4AQ@mail.gmail.com>
References: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
 <56A253F2.1070803@candelatech.com>
 <CAERPaea0oRqKAH-Ne6W3V8iF+af9d-b5C5CSmLyrS38-mRUT_w@mail.gmail.com>
 <56A267AF.4050700@candelatech.com>
 <CAERPaeaxj3gRbk=GUG_xwpWrhLSNsVMbmUNL8EC-FkC6kWqC_g@mail.gmail.com>
 <CAERPaeYFtOJqP1udQtTnpMgOqwSn+o9PBK2buj8F1=pQ2JrE1g@mail.gmail.com>
 <56A6649C.6000203@candelatech.com>
 <CAERPaea9y-OKPQZXc52JXPnwmoeoaDqzPNi+fGW8k5Bnd=K4AQ@mail.gmail.com>
Message-ID: <56AA8AEF.40206@candelatech.com>

On 01/28/2016 03:19 AM, Mike Engel wrote:
> Hi Ben,
>
> thanks again for your feedback. Yes we use wpa_supplicant for AP mode.
>
> I changed the verbose level when launching wpa_supplicant and I saw
> that it fails because the channel I would like to use seems to be
> disabled by the firmware or driver.

Have you tried using hostapd?  I don't have any experience with
supplicant in AP mode.  Maybe at least it will give a different log
message that provides a clue.

Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com



From engel.mike18 at gmail.com  Fri Jan 29 01:29:01 2016
From: engel.mike18 at gmail.com (Mike Engel)
Date: Fri, 29 Jan 2016 10:29:01 +0100
Subject: [ATH6KL]: driver only supports limited channels in 5GHz band
In-Reply-To: <56AA8AEF.40206@candelatech.com>
References: <CAERPaebicO5yrJiAx50YfOz7kxiOOaLji7US=pDjU7sRqsGQGw@mail.gmail.com>
 <56A253F2.1070803@candelatech.com>
 <CAERPaea0oRqKAH-Ne6W3V8iF+af9d-b5C5CSmLyrS38-mRUT_w@mail.gmail.com>
 <56A267AF.4050700@candelatech.com>
 <CAERPaeaxj3gRbk=GUG_xwpWrhLSNsVMbmUNL8EC-FkC6kWqC_g@mail.gmail.com>
 <CAERPaeYFtOJqP1udQtTnpMgOqwSn+o9PBK2buj8F1=pQ2JrE1g@mail.gmail.com>
 <56A6649C.6000203@candelatech.com>
 <CAERPaea9y-OKPQZXc52JXPnwmoeoaDqzPNi+fGW8k5Bnd=K4AQ@mail.gmail.com>
 <56AA8AEF.40206@candelatech.com>
Message-ID: <CAERPaeYsTj4=mLoQaL9mXHjh6+sMx72g+aK4_-Wdsz_UzZV-zA@mail.gmail.com>

Hi Ben,

it seems that the firmware version we use doesn't support that
(3.4.0.225). We have got received some information from Qualcomm
mention that. I will also try to give the hostapd a try to see what we
get.

Thanks again for all your help and input.

Thanks,
--
Mike

On Thu, Jan 28, 2016 at 10:41 PM, Ben Greear <greearb at candelatech.com> wrote:
> On 01/28/2016 03:19 AM, Mike Engel wrote:
>>
>> Hi Ben,
>>
>> thanks again for your feedback. Yes we use wpa_supplicant for AP mode.
>>
>> I changed the verbose level when launching wpa_supplicant and I saw
>> that it fails because the channel I would like to use seems to be
>> disabled by the firmware or driver.
>
>
> Have you tried using hostapd?  I don't have any experience with
> supplicant in AP mode.  Maybe at least it will give a different log
> message that provides a clue.
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>


From engel.mike18 at gmail.com  Fri Jan 29 01:29:44 2016
From: engel.mike18 at gmail.com (Mike Engel)
Date: Fri, 29 Jan 2016 10:29:44 +0100
Subject: [ath6kl]: Concurrent mode (STA+P2P) or (AP+P2P)
In-Reply-To: <CAERPaeZvv6KMm9FWas81rV61MYY1-W4LMjQU25vG5N1NzKAQKQ@mail.gmail.com>
References: <CAERPaeZvv6KMm9FWas81rV61MYY1-W4LMjQU25vG5N1NzKAQKQ@mail.gmail.com>
Message-ID: <CAERPaea5w7KMvAu9TA7u-ADOd+5pXShdO0C3zavpHqs-mOfb_g@mail.gmail.com>

Any input or hint on this?

On Wed, Jan 20, 2016 at 1:34 PM, Mike Engel <engel.mike18 at gmail.com> wrote:
> Hi all,
>
> we are using the kernel version 3.14 with the Atheros driver and we
> would like to use concurrent mode. We have the latest firmware version
> (fw-4) on the file system. We would like to use STA+P2P in concurrent
> mode that should work with the wireless chip.
>
> We are using this command sequence:
>
>> iw dev wlan0 interface add wlan1 type managed
>> ifconfig wlan1 up
>> wpa_cli
>> p2p_find
>
> If we try to connect to a device with
>
> p2p_connect <device_mac> pbc auth
>
> we get the following error.
>
> ath6kl: Not a supported interface type
>
> To make AP+STA working in the Atheros driver we did this change to the driver.
>
> static const struct ieee80211_iface_limit if_limits[] = {
>     { .max = 2, .types = BIT(NL80211_IFTYPE_STATION) },
>     { .max = 1, .types = BIT(NL80211_IFTYPE_AP) },
> };
>
> static const struct ieee80211_iface_combination if_comb[] = {
>     {
>         .limits = if_limits,
>         .n_limits = ARRAY_SIZE(if_limits),
>         .max_interfaces = 2,
>         .num_different_channels = 1,
>         .beacon_int_infra_match = true,
>     },
> };
>
> Doing the same for STA+P2P doesn't seem to work.
>
> Any information or help is appreciated .
>
> Thanks,
> --
> Mike Engel


