[ATH6KL]: driver only supports limited channels in 5GHz band
Mike Engel
engel.mike18 at gmail.com
Mon Jan 25 02:40:33 PST 2016
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
>>
More information about the ath6kl
mailing list