From: Johannes Berg <johannes@sipsolutions.net>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: radiotap@netbsd.org, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Query] Decryption and Monitor Mode
Date: Wed, 06 Nov 2013 08:59:54 +0100 [thread overview]
Message-ID: <1383724794.14307.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CABPxzY++gCivs1u8nDtAeB5=p+ZkGHXmOnqud1hkh=TWB5Xprg@mail.gmail.com>
On Wed, 2013-11-06 at 01:22 +0530, Krishna Chaitanya wrote:
> With this wireshark is not able to decode the packets, even thought
> they are decrypted. I propose 2 solutions
Well, you can say "ignore protected bit (with IV)" in the settings of
wireshark. But I agree that this is cumbersome, and previously floated
the idea of addings bits to radiotap to make this auto-detected.
> Radiotap and Wireshark:
>
> 1) Add 2 flags to the radiotap RX Flags (HW Decrypted the packet,
> Packet has security Header (for some chipsets which consume the
> security header as well..??).)
>
> Based on these the wireshark dissector decodes the packet accordingly.
>
> mac80211:
>
> 2) Remove the security header information in the monitor path as well
> based on the existing RX_FLAGS.
>
>
> Solutions 2 looks more elegant and simple, any comments?
Solution 2 drops information and makes the kernel code more expensive,
so I don't think we want that.
I think the radiotap bits would be better.
johannes
next prev parent reply other threads:[~2013-11-06 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 19:52 [Query] Decryption and Monitor Mode Krishna Chaitanya
2013-11-06 7:59 ` Johannes Berg [this message]
2013-11-06 10:15 ` Krishna Chaitanya
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=1383724794.14307.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chaitanya.mgit@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=radiotap@netbsd.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).