From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Specifying priority for management frames?
Date: Fri, 06 Sep 2013 14:22:28 -0700 [thread overview]
Message-ID: <522A4794.7080106@candelatech.com> (raw)
In-Reply-To: <5228CD6B.5010209@candelatech.com>
On 09/05/2013 11:28 AM, Ben Greear wrote:
> On 09/05/2013 11:17 AM, Ben Greear wrote:
>> While debugging a problem with group-rekeys, we noticed that the sniffer (on external machine)
>> reported management packets are sent in the best-effort QoS queue.
>>
>> It seems to me that these should be in the VO queue instead, or at least
>> we should be able to specify the queue in supplicant when sending the frames?
>
>
> Hrmm, actually it appears the mac80211 layer tries to send on VO. Maybe
> some of my hackings are messing this up...I'll go dig deeper.
I've dug a bit deeper, but not all the way I guess.
When I sniff on a separate machine, the EAP packets still
show QoS being 'Best Effort' in wireshark.
UDP data packets sent with proper IP TOS show up in
VI or VO as specified.
So, I think this means that either the EAP packets are not actually
going out the VO queue, or they are somehow missing some wifi QoS config
in their header.
I just tested this with the latest wireless-testing tree, totally un-modified.
The sniffer is running my standard set of patches, but I doubt that matters
since it does properly show QoS on UDP packets.
I'll go look to see if I can figure out where the wifi frame TOS bits
are configured..but if someone has suggestions, let me know!
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-09-06 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 18:17 Specifying priority for management frames? Ben Greear
2013-09-05 18:28 ` Ben Greear
2013-09-06 21:22 ` Ben Greear [this message]
2013-09-09 18:52 ` Ben Greear
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=522A4794.7080106@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.