From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <linville@tuxdriver.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V9 2/2] cfg80211/nl80211: Enable drivers to implement MAC address based ACL
Date: Sat, 19 Jan 2013 10:39:27 +0530 [thread overview]
Message-ID: <50FA2A87.6000106@qca.qualcomm.com> (raw)
In-Reply-To: <1358544641.7922.28.camel@jlt4.sipsolutions.net>
On Saturday 19 January 2013 03:00 AM, Johannes Berg wrote:
> On Fri, 2013-01-18 at 11:18 +0530, Vasanthakumar Thiagarajan wrote:
>
>> + * @NL80211_ATTR_ACL_POLICY: ACL policy, see&enum nl80211_acl_policy_attr.
>> + *
>> + * @NL80211_ATTR_MAC_ADDRS: Array of nested MAC addresses, used for
>> + * MAC ACL.
>
> Ok so one last (not a promise ;-) ) thing ...
>
> You basically completely back-pedalled from wanting to support white&
> blacklist at the same time to no longer even allowing that in the API.
> Should I really merge this? Who says you're not going to return in a
> couple of weeks and want that then, making the API very strange?
The decision to have ACL only with a single list has been taken only
after a detailed (private) discussion with Jouni. I'm pretty much
convinced that this API is enough for ACL, everything else can be
handled in user space(wpa_s) like different types of notification to
application for stats purpose or user feedback.
>
>
> Anyway, if you think that the dual list approach is dead indefinitely, I
> guess I can apply it. I'm just not sure I believe that ;-)
As said above, I think this API + wpa_s changes are enough to do the
job of black & white list.
Vasanth
next prev parent reply other threads:[~2013-01-19 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 5:48 [PATCH V9 1/2] cfg80211: Move the definition of struct mac_address up Vasanthakumar Thiagarajan
2013-01-18 5:48 ` [PATCH V9 2/2] cfg80211/nl80211: Enable drivers to implement MAC address based ACL Vasanthakumar Thiagarajan
2013-01-18 21:30 ` Johannes Berg
2013-01-19 5:09 ` Vasanthakumar Thiagarajan [this message]
2013-01-25 17:39 ` Johannes Berg
2013-01-28 4:48 ` Vasanthakumar Thiagarajan
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=50FA2A87.6000106@qca.qualcomm.com \
--to=vthiagar@qca.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.