[156698] in North American Network Operators' Group
Re: Big Temporary Networks
daemon@ATHENA.MIT.EDU (=?ISO-8859-15?Q?J=C1K=D3_Andr=E1s?)
Sun Sep 23 15:51:09 2012
Date: Sun, 23 Sep 2012 21:50:19 +0200 (CEST)
From: =?ISO-8859-15?Q?J=C1K=D3_Andr=E1s?= <jako.andras@eik.bme.hu>
To: William Herrin <bill@herrin.us>
In-Reply-To: <CAP-guGXKKj9T5jsjZ1HDScp7HKLgf0EEipg4AdV1--DDLuA8aQ@mail.gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> Second, in the hotspot scenarios where this is likely to be a problem
> (in IPv4 -or- IPv6) it's addressed by the "AP isolation" feature
> that's getting close to omnipresent even in the low end APs. With this
> feature enabled, stations are not allowed to talk to each other over
> the wlan; they can only talk to hosts on the wired side of the lan.
Not related to the original subject, neither to IPv6 usability on WLANs,=20
just a small comment: As far as I understand "AP isolation" doesn't work=20
if you don't have a WLAN controller but do have more than one APs. E.g. in=
=20
the following setup
ap1--sw1--sw2--ap2
with "AP isolation" turned on, clients associated to ap1 cannot=20
communicate directly with other clients associated to ap1, however they=20
can communicate directly with those associated to ap2. Broadcast from=20
ap1's clients does also get to all clients at ap2.
Regards,
Andr=E1s
