From: Michal Kazior <michal.kazior@tieto.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC 0/2] ath10k: fix qos workaround
Date: Wed, 24 Apr 2013 14:49:17 +0200 [thread overview]
Message-ID: <5177D4CD.6020804@tieto.com> (raw)
In-Reply-To: <20855.47516.43566.209338@gargle.gargle.HOWL>
On 24/04/13 12:53, Sujith Manoharan wrote:
> Michal Kazior wrote:
>> >From what I've observed so far is frames in
>> monitor mode (non promiscuous) are corrupted. They
>> have the QoS Control stripped, with LLC header
>> finding itself in the QoS Control. Wireshark shows
>> such packets as A-MSDU corrupted frames. I tried
>> restoring the QoS Control but it didn't fix that.
>
> I don't understand. Why should pure monitor mode care about
> the TX path ?
This is not concerned with the pure (I hope we don't have a
misunderstanding here) monitor mode.
You can create monitor vif when associated and you might want to listen
to the traffic *without* going into the promiscuous mode (no monitor
vdev is created). It simply passes raw 802.11 frames that pass through
mac80211 (both tx and rx) on other interfaces (i.e. associated station
interface).
-- Pozdrawiam / Best regards, Michal Kazior.
next prev parent reply other threads:[~2013-04-24 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k3ntawjy.fsf@kamboji.qca.qualcomm.com>
2013-04-24 10:10 ` [ath9k-devel] [RFC 0/2] ath10k: fix qos workaround Michal Kazior
2013-04-24 10:10 ` [ath9k-devel] [RFC 1/2] ath10k: make more space in ath10k_skb_cb Michal Kazior
2013-04-24 10:10 ` [ath9k-devel] [RFC 2/2] ath10k: copy skb during tx Michal Kazior
2013-04-24 10:53 ` [ath9k-devel] [RFC 0/2] ath10k: fix qos workaround Sujith Manoharan
2013-04-24 12:49 ` Michal Kazior [this message]
2013-04-25 6:43 ` Kalle Valo
2013-04-25 6:59 ` Michal Kazior
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=5177D4CD.6020804@tieto.com \
--to=michal.kazior@tieto.com \
--cc=ath9k-devel@lists.ath9k.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.