From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Fun with QoS in AP mode.
Date: Tue, 07 May 2013 21:58:26 -0700 [thread overview]
Message-ID: <5189DB72.3020809@candelatech.com> (raw)
We were doing some testing with ToS/QoS in some VOIP streams today.
The mappings on the station machine work fine, but on the AP, the packets
always go to the BE queue. Both systems are 3.9.0+ ath9k, recent hostapd,
supplicant, etc.
The VOIP call traffic is going station to station, so the AP is just turning
the packets around..
Any ideas where to go poking?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2013-05-08 4:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 4:58 Ben Greear [this message]
2013-05-08 5:06 ` Fun with QoS in AP mode Sujith Manoharan
2013-05-08 15:15 ` Ben Greear
2013-05-09 5:13 ` Sujith Manoharan
2013-05-09 14:43 ` Ben Greear
[not found] ` <CAJu560hVBcdJ67uNprj0TOY6rWNd-iT8f7QNaE64=ENz91yj6w@mail.gmail.com>
2013-05-09 16:26 ` Ben Greear
2013-05-09 16:32 ` Sujith Manoharan
2013-05-09 16:39 ` Ben Greear
2013-05-09 17:00 ` Krishna Chaitanya
2013-05-09 18:50 ` 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=5189DB72.3020809@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).