From: Felix Fietkau <nbd@openwrt.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Sujith Manoharan <sujith@msujith.org>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Always send management frames at MCS-0??
Date: Wed, 11 Sep 2013 11:33:28 +0200 [thread overview]
Message-ID: <523038E8.2070806@openwrt.org> (raw)
In-Reply-To: <522F3F6B.2070203@candelatech.com>
On 2013-09-10 5:48 PM, Ben Greear wrote:
> On 09/10/2013 01:10 AM, Sujith Manoharan wrote:
>> Ben Greear wrote:
>>> I had a user request that we support always sending management frames
>>> (such as EAPOL) at the lowest rate. Evidently, other equipment does this,
>>> where as normal-ish supplicant/linux tends to send them at much higher
>>> rates.
>>>
>>> Any suggestions on how to go about doing this properly?
>>
>> If this is with ath9k_rate_control, then it is a known bug:
>> https://bugzilla.redhat.com/show_bug.cgi?id=927191
>
> I'm not using ath9k rate control in this case, and at least most messages
> get through fine. We didn't actually see any obvious improvement when forcing
> everything to 6Mbps, but since my user was asking, I wanted to run the
> idea past the list.
>
> Rate control is not perfect, and on initial bringup it doesn't have
> many packets to work with so I thought it might still be useful to allow
> users to specify a particular rate for EAPOL packets. Maybe using
> a socket ioctl so user-space (ie, supplicant/hostapd) can control it,
> for example.
minstrel and minstrel_ht always keep low rates in the rate retry chain
until enough higher rates have been proven to work.
I think adding an interface that allows user space to mess with the rate
selection of EAPOL packets is a bad idea - users will pretty much always
make worse rate decisions than the rate control module.
- Felix
prev parent reply other threads:[~2013-09-11 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 19:10 Always send management frames at MCS-0?? Ben Greear
2013-09-09 19:15 ` Krishna Chaitanya
2013-09-09 23:10 ` Ben Greear
2013-09-10 9:17 ` Krishna Chaitanya
2013-09-10 14:49 ` Dan Williams
2013-09-10 8:10 ` Sujith Manoharan
2013-09-10 15:48 ` Ben Greear
2013-09-11 9:33 ` Felix Fietkau [this message]
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=523038E8.2070806@openwrt.org \
--to=nbd@openwrt.org \
--cc=greearb@candelatech.com \
--cc=hostap@lists.shmoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sujith@msujith.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).