/32 subnet

Outback Dingo outbackdingo at gmail.com
Wed Feb 4 10:15:59 UTC 2009


hrmm honestly, isnt this the same as AP separation on the AP itself?? using
say

 option isolate  1 in both openwrt and i believe dd-wrt it essentaily does
the same thing if im not mistaken

though on the other hand i guess i could see it for server based chilli
access controllers

On Wed, Feb 4, 2009 at 5:03 PM, Thomas Liske <liske at ibh.de> wrote:

> Hi,
>
> the basic idea behind the attached patch is the following:
>
> On a hotspot, normaly you don't want to allow client to client
> communication (everybody should have access to the internet and be somehow
> protected from other hotspot users) - especially for the windows dhows.
>
> This patch adds a new configuration option "noc2c" (no client 2 client
> communcation). With this option enabled, the DHCP offers supplies a /32
> netmask. Doing this would prevent any hotspot client to communcate with
> anybody, even the default gateway. Therefore it adds a static route for the
> default gw as an connected route. This prevents (windows) clients doing any
> broadcasts on the hotspot network and reach any other hotspot client
> (default gateway must not route any pakets coming from a hotspot client to
> any other hotspot client). It would be great if somebody could test it with
> additional clients, Win XP works as expected.
>
> Any comments on the patch are welcome ;)
>
>
> Regards,
> Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
> For additional commands, e-mail: chilli-help at coova.org
> Wiki: http://coova.org/wiki/index.php/CoovaChilli
> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20090204/e098230f/attachment.htm>


More information about the Chilli mailing list