From: David Gnedt <david.gnedt@davizone.at>
To: Kalle Valo <kvalo@adurom.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
Grazvydas Ignotas <notasas@gmail.com>,
Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Subject: Re: [PATCH 11/18] wl1251: configure hardware en-/decryption for monitor mode
Date: Sun, 06 Feb 2011 15:05:11 +0100 [thread overview]
Message-ID: <4D4EAA97.90709@davizone.at> (raw)
In-Reply-To: <87oc6vbcyz.fsf@purkki.adurom.net>
Am 2011-02-01 23:35, schrieb Kalle Valo:
> But doesn't this break the case when you are connected to a network
> with encryption and you have a separate monitor interface at the same
> time? Or even worse, as Johannes pointed out, will the frames sent
> unencrypted?
If you add a monitor interface, it will break associated (encryption enabled)
managed interfaces (until mac80211 tries to reassociate). Nevertheless it
shouldn't send out unencrypted frames because of the added check in tx.c.
I couldn't find any mac80211 API function to renegotiate hw encryption, so I
originally did an awful hack to force reassociation on the managed interface. I
haven't included that patch in this patchset.
By the way I forgot that DF_SNIFF_MODE_ENABLE is also necessary for receiving
encrypted frames, which can't be decrypted in firmware (else they would be
corrupted).
prev parent reply other threads:[~2011-02-06 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 17:54 [PATCH 11/18] wl1251: configure hardware en-/decryption for monitor mode David Gnedt
2011-01-30 19:11 ` David Gnedt
2011-01-31 15:43 ` Kalle Valo
2011-01-31 22:58 ` David Gnedt
2011-02-01 22:35 ` Kalle Valo
2011-02-06 14:05 ` David Gnedt [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=4D4EAA97.90709@davizone.at \
--to=david.gnedt@davizone.at \
--cc=GNUtoo@no-log.org \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=notasas@gmail.com \
/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).