From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Flaky AP has bad AIFSN, so no HT/VHT....
Date: Thu, 26 Feb 2015 10:07:49 -0800 [thread overview]
Message-ID: <54EF60F5.1030506@candelatech.com> (raw)
One of our customers reported that our ath10k stations were only able
to connect at 54Mbps speeds. This is using somewhat hacked 3.17.8 kernel,
but it looks like 3.19 has the same code checks for AIFSN.
It looks like their beacon has bogus AIFSN info, and sniff of the beacon does
show AIFSN set to 0.
Kernel dmesg logs:
wlan0: authenticated at: 1424969385.456415
wlan0: AP has invalid WMM params (AIFSN=0 for ACI 0), disabling WMM
wlan0: associate with 00:18:25:06:4a:b4 (try 1/3), at: 1424969385.457148
wlan0: RX AssocResp from 00:18:25:06:4a:b4 (capab=0x401 status=0 aid=2) at: 1424969385.476681
wlan0: associated at: 1424969385.477265
But a commercial phone connects just fine to this AP, and reports ~780Mbps link speed,
so it at least thinks it is doing VHT.
My question is, should we just warn and ignore this bad AIFSN, or is this really
a fatal issue as far as enabling WMM?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2015-02-26 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 18:07 Ben Greear [this message]
2015-02-26 20:13 ` Flaky AP has bad AIFSN, so no HT/VHT Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54EF60F5.1030506@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).