From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Jouni Malinen <Jouni.Malinen@Atheros.com>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: do not TX injected frames when not allowed
Date: Sun, 18 Jan 2009 07:32:43 -0800 [thread overview]
Message-ID: <20090118153243.GU29609@tesla> (raw)
In-Reply-To: <1232268339.3877.5.camel@johannes>
On Sun, Jan 18, 2009 at 12:45:39AM -0800, Johannes Berg wrote:
> On Fri, 2009-01-16 at 10:52 -0800, Luis R. Rodriguez wrote:
> > Monitor mode is able to TX by using injected frames. We should
> > not allow injected frames to be sent unless allowed by regulatory rules.
> > Since AP mode uses a monitor interfaces to transmit management frames
> > we have to take care to not break AP mode as well. Since hostapd
> > respects 'no-ibss|radar' flags we can make use of the same policy
> > statically for checking when to disable injected frames. Once AP
> > mode supports radar detection we should somehow distinguish a
> > regular monitor mode from an AP's monitor interface.
>
> Any proposal for "somehow"? I'm not all that worried about packet
> injection here.
I'll send a patch instead. Keep in mind by not applying this you are
allowing devices to not respect regulatory rules.
Luis
next prev parent reply other threads:[~2009-01-18 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 18:52 [PATCH] mac80211: do not TX injected frames when not allowed Luis R. Rodriguez
2009-01-18 8:45 ` Johannes Berg
2009-01-18 15:32 ` Luis R. Rodriguez [this message]
2009-01-18 16:04 ` Luis R. Rodriguez
-- strict thread matches above, loose matches on Subject: below --
2009-01-27 0:22 Luis R. Rodriguez
2009-01-27 8:49 ` 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=20090118153243.GU29609@tesla \
--to=lrodriguez@atheros.com \
--cc=Jouni.Malinen@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).