From: Johannes Berg <johannes@sipsolutions.net>
To: Allan Matthew <allanm84@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: set channel from radiotap headers during injection
Date: Wed, 19 Aug 2015 20:09:05 +0200 [thread overview]
Message-ID: <1440007745.2089.11.camel@sipsolutions.net> (raw)
In-Reply-To: <CAEnVuW18e15hOjoMYRstjgu2cr5BFAtVHThAyZGqpMAdFUQrpQ@mail.gmail.com> (sfid-20150819_183736_502054_67CA1931)
On Wed, 2015-08-19 at 09:37 -0700, Allan Matthew wrote:
> It seems like the functionality for this (maybe not the monitor mode)
> must be available in order to support the multiple 802.11p channels
> in the 5.8ghz band.
Not sure - I haven't looked at WAVE/11p in a long time, but the code we
have certainly assumes that the channel configuration is fixed, i.e.
only done once when "joining" the network.
> It sounds like what you are proposing is to create a non-monitor vif,
> select its channel, bitrate, bandwidth and then use the MAC address
> to
> select it as the transmitting interface. Is that correct? I'm
> guessing I could do this with raw sockets and prepend the ieee80211
> header (but not the radiotap header)?
>
No - radiotap injection has code to select the interfaces. So if you
have hardware that's capable of, say, having two AP interfaces on
different channels, then injection would select the channel by
selecting the interface. However, this isn't really a good way of
handling this either.
If you can be more specific what this would be used for, perhaps kernel
modifications would be appropriate to support it more correctly (rather
than relying on injection.)
johannes
next prev parent reply other threads:[~2015-08-19 18:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 18:22 set channel from radiotap headers during injection Allan Matthew
2015-08-14 21:39 ` Allan Matthew
2015-08-19 11:24 ` Johannes Berg
2015-08-19 16:37 ` Allan Matthew
2015-08-19 18:09 ` Johannes Berg [this message]
2015-08-19 19:00 ` Allan Matthew
2015-08-19 19:41 ` Johannes Berg
2015-08-19 19:50 ` Allan Matthew
2015-08-19 19:53 ` Johannes Berg
2015-08-19 20:43 ` Allan Matthew
2015-08-25 0:46 ` Allan Matthew
2015-08-25 9:36 ` Johannes Berg
2015-08-25 17:47 ` Allan Matthew
2015-08-25 17:48 ` Johannes Berg
2015-08-19 17:44 ` Ben Greear
2015-08-19 18:02 ` Johannes Berg
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=1440007745.2089.11.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=allanm84@gmail.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).