From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
"John W. Linville" <linville@tuxdriver.com>,
Jouni Malinen <Jouni.Malinen@atheros.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] cfg80211: add ap isolation support
Date: Tue, 27 Apr 2010 08:22:41 +0200 [thread overview]
Message-ID: <1272349361.3549.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <x2i43e72e891004261853p751a5d5bt9cbb99846b2eb1fb@mail.gmail.com>
On Mon, 2010-04-26 at 18:53 -0700, Luis R. Rodriguez wrote:
> >>>>> Yes, if you have an AP with lots of users that aren't expected to
> >>>>> communicate with each other (e.g. only for internet access), it can save
> >>>>> a lot of airtime by not forwarding every broadcast message emitted from
> >>>>> any station.
> >>>>> I'm sure there are a more situations where this can be useful.
> So the other way for an AP to forward traffic from STAs on the BSS to
> others is to transmit broadcast frames and the purpose of this patch
> is to disable that? If so can the description of the command be a
> little more descriptive about this? Perhaps annotating that other
> communication would not be done unless DLS links are created ?
The broadcast thing is a red herring. This applies also to unicast
frames sent between stations.
Basically what this patch does is restrict the network segment to each
station. You can send and receive multicast frames to/from the wired
network, but you would typically attach an AP like this to its own
network segment. And you can send/receive unicast frames, but not to
other stations on the AP. Or think of it as restricting the broadcast
domain. Or, another more expensive way to implement this would be to put
each station into its own VLAN (which should actually be feasible in
practice too).
johannes
next prev parent reply other threads:[~2010-04-27 6:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 23:23 [PATCH 1/2] cfg80211: add ap isolation support Felix Fietkau
2010-04-26 23:23 ` John W. Linville
2010-04-26 23:30 ` Felix Fietkau
2010-04-27 0:12 ` John W. Linville
2010-04-27 0:25 ` Luis R. Rodriguez
2010-04-27 1:34 ` Luis R. Rodriguez
2010-04-27 1:42 ` Felix Fietkau
2010-04-27 1:53 ` Luis R. Rodriguez
2010-04-27 6:22 ` Johannes Berg [this message]
2010-04-27 0:09 ` Bruno Randolf
2010-04-26 23:23 ` [PATCH 2/2] mac80211: implement " Felix Fietkau
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=1272349361.3549.8.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Jouni.Malinen@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--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).