[Chilli] Multiple chilli instances on the same network
david at coova.com
Mon Jan 21 18:37:41 UTC 2013
"Roaming" can mean several things here. As correctly pointed out, it is
routine to allow for roaming authentication through standard RADIUS
practices - typically using 802.1x or mac authentication on UAM network.
You could also have roaming between APs where the same chilli session is
maintained where the APs bridge into the same network. However, that is
separate from the clustering feature, which is designed to provide fault
tolerance. The feature is not complete and has only been experimented
with (with encouraging results). The concept is to have multiple
instance of chilli synchronized and able to assume control over the
network segment should the primary instance fail.
On Mon, 2013-01-21 at 09:55 +0100, Emanuele Pucciarelli wrote:
> > Yes, I could imagine that also, but in this setup, you've single point of
> > failure, right? If the AP which is running the Chilli instance goes down, then
> > you've a problem. What I would like to have instead, is Chilli running on all
> > the APs and share the client states between them, so if the user roams from
> > one Chilli instance to another one, he doesn't need to authenticate again.
> Correct! I almost forgot that it's designed to be run on access
> points! :) What I'm doing in this case is, simply, running Chillispot
> in a VM and handling availability at that level. My access points are
> completely unaware of Chillispot, except for being configured to use
> Chillispot as a RADIUS server and having both the 802.1x SSID and the
> "captive portal" SSID bound to the VLAN where Chillispot's DHCP server
> is listening.
> Best regards,
More information about the Chilli