From: Kalle Valo <kvalo@adurom.com>
To: David Gnedt <david.gnedt@davizone.at>
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: Wed, 02 Feb 2011 00:35:00 +0200 [thread overview]
Message-ID: <87oc6vbcyz.fsf@purkki.adurom.net> (raw)
In-Reply-To: <4D473E9A.9050106@davizone.at> (David Gnedt's message of "Mon\, 31 Jan 2011 23\:58\:34 +0100")
David Gnedt <david.gnedt@davizone.at> writes:
> Am 2011-01-31 16:43, schrieb Kalle Valo:
>>> Disable hardware encryption (DF_ENCRYPTION_DISABLE) and decryption
>>> (DF_SNIFF_MODE_ENABLE) via wl1251_acx_feature_cfg while monitor interface is
>>> present.
>>
>> Why? To be able to receive encrypted frames when associated or
>> something else?
>
> DF_SNIFF_MODE_ENABLE is set for receiving encrypted frames when associated.
> DF_ENCRYPTION_DISABLE is set to allow packet injection at all, as my testing
> showed that disabling encryption per-packet doesn't work.
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?
--
Kalle Valo
next prev parent reply other threads:[~2011-02-01 22:35 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 [this message]
2011-02-06 14:05 ` David Gnedt
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=87oc6vbcyz.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=GNUtoo@no-log.org \
--cc=david.gnedt@davizone.at \
--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).