From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"hostap@lists.shmoo.com" <hostap@lists.shmoo.com>
Subject: Always send management frames at MCS-0??
Date: Mon, 09 Sep 2013 12:10:41 -0700 [thread overview]
Message-ID: <522E1D31.2090403@candelatech.com> (raw)
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?
Any opinions on whether it's a good idea or not?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2013-09-09 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 19:10 Ben Greear [this message]
2013-09-09 19:15 ` Always send management frames at MCS-0?? 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
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=522E1D31.2090403@candelatech.com \
--to=greearb@candelatech.com \
--cc=hostap@lists.shmoo.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).