From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 1/3] cfg80211: support an active monitor interface flag
Date: Tue, 28 May 2013 14:38:32 +0200 [thread overview]
Message-ID: <1369744712.8548.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51A4A044.3030109@openwrt.org>
On Tue, 2013-05-28 at 14:17 +0200, Felix Fietkau wrote:
> On 2013-05-28 1:50 PM, Johannes Berg wrote:
> > On Tue, 2013-05-28 at 13:01 +0200, Felix Fietkau wrote:
> >> An active monitor interface is one that is used for communication (via
> >> injection). It is expected to ACK incoming unicast packets. This is
> >> useful for running various 802.11 testing utilities that associate to an
> >> AP via injection and manage the state in user space.
> >
> > Applied 1 and 2.
> >
> > Allowing MAC address duplication seems a bit strange, but I guess it
> > simplifies things for users?
> It is allowed only for non-active monitor interfaces, which previously
> did not use ieee80211_verify_mac and ignores the configured MAC address
> anyway.
Oh, that makes sense, I misread the code then.
johannes
prev parent reply other threads:[~2013-05-28 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 11:01 [PATCH v2 1/3] cfg80211: support an active monitor interface flag Felix Fietkau
2013-05-28 11:01 ` [PATCH v2 2/3] mac80211: support active monitor interfaces Felix Fietkau
2013-05-28 11:01 ` [PATCH v2 3/3] ath9k: advertise support for " Felix Fietkau
2013-05-28 11:50 ` [PATCH v2 1/3] cfg80211: support an active monitor interface flag Johannes Berg
2013-05-28 12:17 ` Felix Fietkau
2013-05-28 12:38 ` Johannes Berg [this message]
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=1369744712.8548.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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).