Ali Abedi | 22 Oct 17:38 2014

Block ACK without frame aggregation


I am interested to know if we can send multiple packets (non-aggregated, 
single packets) and then ask
for a block ACK? I like to know if this functionality has been 
implemented in ath9k or if
it is possible to achieve this with slight code modifications.

What I need:
Frame-SIFS-Frame-SIFS-Frame-SIFS-REQ Block ACK-SIFS-Block ACK

이재훈 | 22 Oct 09:09 2014

Questions about ath9k driver

Hi, my name is jaehoon Lee and a graduate student at Seoul National University.


Recently, I bought the alix 2d2 device and wireless card(wlm200nx) for experiment the IEEE 802.11aa.


How can I install the ath9k driver and open FirmWare for WiFi networks in linux such as Ubuntu?


Thanks for reading my questions.


Best regards



Jaehoon Lee

ath9k-devel mailing list
ath9k-devel <at>
Li, Hongchun | 18 Oct 09:46 2014

IBSS network crashes after one device leaves network

I’m building an IBSS network using TP-Link TL-WN722N USB WiFi dongle.

I find that it is drived by ath9k.


Here is a problem I encountered.

First, I build an IBSS network with more than 8 devices.

For example, a network consists of 9 devices, N1, N2, …, N9.

All devices have same WiFi module.


When N9 joined network, kernel throws a warning, “Unable to move IBSS STA MAC_ADDR to state 3 (-105)”.

However, the network works correctly. Any node can communicate with each other.


But if I turn off one device, for example N3, the network crashes after a few minutes.

Ping command fails between any two devices in network.

Get no warning/error message from kernel.

After N3 is turned off and network crashes, I turned on N3 and network works correctly again.


I find the number 8 is an macro in device driver code: drivers/net/wireless/ath/ath9k/htc.h

252 #define ATH9K_HTC_MAX_STA 8

It seems like that when there are more than 8 devices in network, driver returns an error ENOBUFS(-105).


But in linux kernel source: net/mac80211/sta_info.c, I found this,

436  if (sdata->vif.type == NL80211_IFTYPE_ADHOC) {

437        sdata_info(sdata,

438                 "failed to move IBSS STA %pM to state %d (%d) - keeping it anyway\n",

439                 sta->sta.addr, state + 1, err);

440       err = 0;

441  }

So when it is an ad hoc network, kernel just ignore errors from driver.

This answers why ibss network work correctly when there are more than 8 devices.


But I cannot figure out why the network crashes after one device is turned off.

Does anyone have any idea how to solve this problem?


Li Chun


ath9k-devel mailing list
ath9k-devel <at>
JAGADEESH Y C | 16 Oct 09:53 2014

how to disable 11d in Atheros -8462

Hi ,

I am doing P2P testing with Third party Atheros card ,
Atheros card comes as Auto go when passive scanning flag is cleared i,e when it sees any 5G beacon

iw list output :

                        * 5180 MHz [36] (15.0 dBm) (passive scanning, no IBSS)
                        * 5200 MHz [40] (15.0 dBm) (passive scanning, no IBSS)
                        * 5220 MHz [44] (15.0 dBm) (passive scanning, no IBSS)
                        * 5240 MHz [48] (15.0 dBm) (passive scanning, no IBSS)
                        * 5260 MHz [52] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5280 MHz [56] (15.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5300 MHz [60] (15.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5320 MHz [64] (15.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5500 MHz [100] (16.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5520 MHz [104] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5540 MHz [108] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5560 MHz [112] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5580 MHz [116] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5600 MHz [120] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5620 MHz [124] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5640 MHz [128] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5660 MHz [132] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5680 MHz [136] (17.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5700 MHz [140] (16.0 dBm) (passive scanning, no IBSS, radar detection)
                        * 5745 MHz [149] (17.0 dBm)
                        * 5765 MHz [153] (17.0 dBm) (passive scanning, no IBSS)
                        * 5785 MHz [157] (17.0 dBm) (passive scanning, no IBSS)
                        * 5805 MHz [161] (17.0 dBm)
                        * 5825 MHz [165] (17.0 dBm) (passive scanning, no IBSS)

So how do i  disable 11d so that passive scanning for all frequencies gets cleared ..?


ath9k-devel mailing list
ath9k-devel <at>
Georgios Kyriakou | 15 Oct 23:00 2014

MAC Layer Retransmissions during the same TXOP

Hey all,

I don't know if this is the best place to ask, thus I apologize in advance.

Back in the day I was messing around with MadWifi and, if I remember properly, after a packet was transmitted if the sender did not receive an ACK in SIFS time after the completion of the transmission, the sender would attempt a retransmission using the same or lower rate (multi rate retransmissions) without going into the backoff/contention phase. 

I spent some time going through the 802.11-2012 protocol trying to find relevant information without any luck. Is anyone familiar with that concept? Is it implemented that way in ath9k? Is this what the protocol implies?

Any pointers/suggestions are greatly appreciated.

Thank you,
ath9k-devel mailing list
ath9k-devel <at>
Matt Foster | 12 Oct 18:02 2014

ath9k_htc - 2 VIFs: concurrent AP and STATION mode


I may be trying something unsupported here, but thought I would ask the question anyway.

With ath9k_htc it seems easy enough to create two virtual interfaces, one in AP mode, and one in Station mode.

Using hostapd 2.3 to get rid of the requirement for a monitor interface (it seems only two VIFs are
possible), then I can create a VIF to run hostapd on happily.
I can also create a 2nd VIF, and I can ifconfig it up with an address.
However I can't use wpa_supplicant with it:
EAPOL: External notification - EAP success=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - EAP fail=0
EAPOL: Supplicant port status: Unauthorized
EAPOL: External notification - portControl=Auto
EAPOL: Supplicant port status: Unauthorized
nl80211: Authenticate (ifindex=7)
  * bssid=00:33:bb:f8:e5:ba
  * freq=2437
  * SSID - hexdump_ascii(len=7):
     XX XX XX XX XX XX XX                              XXXXX
  * IEs - hexdump(len=0): [NULL]
  * Auth Type 0
nl80211: MLME command failed: ret=-16 (Device or resource busy)
adhoc0: SME: Authentication request to the driver failed
Added BSSID XXXXXXX into blacklist

Similarly if hostapd is not running, and wpa_supplicant is started (which will now work), hostapd will not
start on it's VIF.

I'm running on 3.12.29 (on arm) with the current version of the firmware from

Am I missing a trick here, or is this something that simply doesn't work with ath9k_htc?


Ali Abedi | 10 Oct 16:40 2014

The operation of Minstrel_ht


I have a few questions about the operation of Minstrel_ht. I couldn't 
find a good reference that
explains minstrel_ht. I tried to understand it by reading the code. The 
fact that frame aggregation
was added to the picture confuses me a bit. I understand the multirate 
retry chain in Minstrel (802.11g).

1- Since the hardware only reties the frame when no block ack is 
received (phy header damage)
(is this correct?), do we still use the multirate retry chain with frame 

2- Is it possible to disable hardware retries?

3- Is software retry defined for an individual MPDU? Is this the number 
of times an MPDU
is rescheduled for transmission?

Thank you in advance.

Rahul Panda | 10 Oct 07:21 2014

Vendor specific information elements


I have just started working on a user space application (using the AR9382) and have almost zero WiFi development experience and learning things on the go.

Currently I am trying to get in some vendor specific information elements for an AP created with hostapd. Have tried adding it to the config but that didnt seem to make any effect. I know I should not be adding it anywhere in the driver directly.

Any pointers as to where I should be looking next?

I guess this may not be the right question for the ath9k mailing list, but kind of out of search options.

Rahul Panda
Hidden Brains Infotech Pvt. Ltd.
Ahmedabad, India.
Mob: +91 955-8480-559
ath9k-devel mailing list
ath9k-devel <at>
Charounson Saintilus | 9 Oct 09:08 2014

Bluetooth Co-Existence Algorithm

Good morning,

Could you provide a high level explanation of the bluetooth co-existence algorithm that's
implemented in the ath9k driver. I am particularly interested in the file structure and the
algorithm itself. Is this solely for co-located bluetooh and wi-fi or does the co-existence apply
to non co-located devices. 

Essentially, what is the general mechanism used by Wi-Fi to co-exist with Bluetooth and how
is it implemented in this driver?


ath9k-devel mailing list
ath9k-devel <at>
Ben Greear | 3 Oct 23:17 2014

3.17 regression, ath9k: Summarize hw state per channel context

Took a while, but I found the regression that has been bugging me.

This is on stock kernel, with hand-patched fixup from Felix that fixes
crash related to minstrel (patch made it upstream later, so that isn't
a current problem).

The test case is easily reproducible on my systems.  I'm not sure
all the details matter, but this happens to be my test case
at the moment:

32-bit Fedora OS, latest supplicant, etc.  ath9k NIC.

create wlan0 and sta0-4 (6 total), not sure how much that matters.
associate all 6 (works fine)
disconnect 5 of them, leaving sta0 up
Start trying to bring up the other 5 one at a time.  It will
fail, with iw events looking like this (in these logs, several
sta are trying to come up, but symptom is the same with just one)

2014-10-03 14:05:43.751  1.3:  sta2 (phy #0): scan finished: 2462, ""
2014-10-03 14:05:43.755  1.3:  sta1: new station 00:0e:8e:6f:40:49
2014-10-03 14:05:43.803  1.1:  vap0 (phy #1): mgmt TX status (cookie f3d5ce40): no ack
2014-10-03 14:05:43.978  1.1:  vap0 (phy #1): mgmt TX status (cookie f3d5ca80): no ack
2014-10-03 14:05:44.179  1.1:  vap0 (phy #1): mgmt TX status (cookie f3d5c900): no ack
2014-10-03 14:05:44.364  1.3:  sta1: del station 00:0e:8e:6f:40:49
2014-10-03 14:05:44.364  1.3:  sta1 (phy #0): auth: timed out
2014-10-03 14:05:45.647  1.3:  sta3 (phy #0): scan started
2014-10-03 14:05:45.659  1.1:  vap0 (phy #1): mgmt TX status (cookie f3d15000): no ack
2014-10-03 14:05:45.668  1.3:  sta3 (phy #0): scan finished: 2462, "ben-138"
2014-10-03 14:05:48.811  1.1:  vap0 (phy #1): mgmt TX status (cookie eaec63c0): no ack
2014-10-03 14:05:49.015  1.1:  vap0 (phy #1): mgmt TX status (cookie ef8cc540): no ack
2014-10-03 14:05:49.213  1.1:  vap0 (phy #1): mgmt TX status (cookie ef8cc540): no ack
2014-10-03 14:05:51.901  1.1:  vap0: del station 00:ab:cd:ef:01:01
2014-10-03 14:07:20.368  1.3:  wlan0 (phy #0): scan started

If I restart all interfaces on the radio, the will come up with no problem,
until I try to restart one again.

Bisect points at this patch:

9a9c4fbc3fcabc0d510600743204f890ebdbb141 is the first bad commit
commit 9a9c4fbc3fcabc0d510600743204f890ebdbb141
Author: Rajkumar Manoharan <rmanohar <at>>
Date:   Wed Jun 11 16:18:03 2014 +0530

    ath9k: Summarize hw state per channel context

    Group and set hw state (opmode, primary_sta, beacon conf) per
    channel context instead of whole list of vifs. This would allow
    each channel context to run in different mode (STA/AP).

    Signed-off-by: Felix Fietkau <nbd <at>>
    Signed-off-by: Rajkumar Manoharan <rmanohar <at>>
    Signed-off-by: John W. Linville <linville <at>>

:040000 040000 aa6eab9d17a0b3468075ff7c1abfee2ccfcb521e
e15af8b46ce047c8b46177e2d4cf74a4590a2181 M	drivers

I will be happy to test patches if anyone has a suggested fix or needs
debug output...



Ben Greear <greearb <at>>
Candela Technologies Inc
Jeyavenkatesh R | 30 Sep 12:36 2014

Help me to test the power save mode in p2p using wpa_supplicant and ath9k driver

  I am using ubuntu machines and ath9k driver for testing the of P2P
using wpa_supplicant. I can see all the features in p2p except power
saving technique. please help me to how to  test the power save
technique in p2p using ath9k driver.

Jeyavenkatesh R