From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Jouni.Malinen@atheros.com, linville@tuxdriver.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: do not TX injected frames when not allowed
Date: Sun, 18 Jan 2009 09:45:39 +0100 [thread overview]
Message-ID: <1232268339.3877.5.camel@johannes> (raw)
In-Reply-To: <1232131932-25044-1-git-send-email-lrodriguez@atheros.com> (sfid-20090116_195246_662337_C460CDDB)
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
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.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-01-18 8:45 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 [this message]
2009-01-18 15:32 ` Luis R. Rodriguez
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=1232268339.3877.5.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=Jouni.Malinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.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).