From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] hostapd: remove vlan stuff
Date: Fri, 17 Aug 2007 12:12:18 +0200 [thread overview]
Message-ID: <1187345538.23489.140.camel@johannes.berg> (raw)
In-Reply-To: <20070817030649.GB1415@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
On Thu, 2007-08-16 at 20:06 -0700, Jouni Malinen wrote:
> That would break the broadcast domain and if someone really want that,
> they could create a VLAN per STA..
Yeah, I was a bit confused here.
> The purpose of using different group
> keys per VLAN is to allow each VLAN to have a separate broadcast domain,
> i.e., all broadcast packets to STAs bound to this VLAN are available to
> all STAs in this VLAN (and only to them).
Right.
> Since in 802.11 BSS networks, broadcast frames are only sent by the AP,
> hw acceleration can be made to work fine with this kind of
> configuration.
True.
> As far as the clients are concerned, they don't even know
> about the existance of different VLANs and group keys and as such, this
> looks a standard AP to them. As far as the AP is concerned, it will need
> to have support for using multiple keys with hwaccel and way of indexing
> them with each transmitted frame. Taken into account how support for
> hwaccel to unicast frames is implemented, this is quite a simple
> extension to that.
True as well, however, have you considered IBSS networks? As far as I
can tell, there you are actually able to put STAs into VLANs as well,
but you need to use per-VLAN group keys for receiving too.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-08-17 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 22:41 [PATCH] hostapd: remove vlan stuff Johannes Berg
2007-08-15 12:24 ` [PATCH v2] " Johannes Berg
2007-08-16 1:22 ` Jouni Malinen
2007-08-16 13:20 ` Johannes Berg
2007-08-17 3:06 ` Jouni Malinen
2007-08-17 10:12 ` Johannes Berg [this message]
2007-08-16 22:39 ` 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=1187345538.23489.140.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.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