Hi all,

I have recently setup a series of WRT's and WRAP boards with OLSR and documented the procedure here: http://www.bewifi.org.au/index.php/OLSRHowto

I installed Chillispot and configured it but I've just realised. If Chillispot is installed on each gateway and you are roaming, a problem lies when switching from one gateway to another you are going to be prompted to enter your details again and that will throw out any connections you had established. Is there anyway the daemon's can work together to keep active sessions?

Or can anyone suggest a different method of authentication that might work OK in this scenario?

Chillispot is a jealous god just like DHCP.  It wants to be the single controlling entity per subnet.

I can't see a good way to avoid this problem each time you move to a new subnet.

If you have one big happy bridged network it's easy you just have one Chilli daemon.

Perhaps WPA-Enterprise or 802.1x or some other method would work better.

still working on a dependency issue, so I do not have the personal experience yet, but with x-wrt there is a webif-mesh-hotspot-setup package....  I do not understand what it is about chillispot that would make it the jealous god? maybe with more info we can come up with a solution.
-tom

If you want it centralised it is quite easy. Have 1 chillispot installation and add accesspoint on the wired ports.

belrpr:
Thanks for your comments. im a bit gray on what chillispot does compared to wpa ent w/radius and other 802.1x solutions - hoping this thread can clarify a bit in the realm of chillispot/olsr. I think one chillispot with wired APs misses at least one maskedau's goals (and mine) - to elim the need for every AP to be a wired gateway. 

For my implementation, there would be many wired gateway nodes, but even more unwired router nodes. The "mesh" is not stable and I would like each node to be part of the AAA rather than rely on a particular node - this is where I though chillispot would have an advantage, but allowing each node to AAA regardless of the other nodes.

A second goal of mine and perhaps of maskedau's as well is for a unique captive portal page for each node - this is what I actually thought chillispot does, to have the page hosted locally on the node and pass the AAA to radius. Or is chillispot just a 802.1x client? If that were the case than oslr would prose no inherent challenge???

thanks again, tom