From: Johannes Berg <johannes@sipsolutions.net>
To: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH V4 2/2] cfg80211/nl80211: Enable drivers to implement mac address based ACL
Date: Thu, 03 Jan 2013 10:54:43 +0100 [thread overview]
Message-ID: <1357206883.9741.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50E51B7F.7000607@qca.qualcomm.com>
On Thu, 2013-01-03 at 11:17 +0530, Vasanthakumar Thiagarajan wrote:
> > Basically we would have two modes:
> > * whitelist
> > * blacklist
> >
> > (each might or might not be supported by the driver)
> >
> > When a station is on the blacklist it's ignored. When it's on the
> > whitelist it's allowed. When it's on neither, but a list is configured,
> > an event might be sent. When there's a black-& whitelist, the blacklist
> > is this an optimisation to suppress the event, so we don't need a third
> > mode "black- and whitelist supported".
>
> Thanks!, I was really confused with this optimization part.
> If I get it correctly, there needs to be a mechanism for
> driver to advertise its dual list capability to user space.
No, because that's subsumed by just the whitelist -- the blacklist in
addition to the whitelist is just an optimisation which we can always
pass to the driver but it may ignore.
johannes
next prev parent reply other threads:[~2013-01-03 9:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 10:21 [PATCH V4 1/2] cfg80211: Move the definition of struct mac_address up Vasanthakumar Thiagarajan
2012-12-28 10:21 ` [PATCH V4 2/2] cfg80211/nl80211: Enable drivers to implement mac address based ACL Vasanthakumar Thiagarajan
2012-12-28 11:31 ` Johannes Berg
2012-12-28 12:56 ` Johannes Berg
2012-12-31 5:14 ` Vasanthakumar Thiagarajan
2013-01-02 12:56 ` Johannes Berg
2013-01-03 5:47 ` Vasanthakumar Thiagarajan
2013-01-03 9:54 ` Johannes Berg [this message]
2012-12-28 13:09 ` Johannes Berg
2012-12-31 5:19 ` Vasanthakumar Thiagarajan
2013-01-02 12:57 ` 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=1357206883.9741.0.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=vthiagar@qca.qualcomm.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).