Académique Documents
Professionnel Documents
Culture Documents
org/node/3960
Ruckus Configuration
We begin to configure our Ruckus access point by connecting a PC to one of the LAN Ethernet ports. (Note: The
default IP for the Ruckus is 192.168.0.1, which we changed to 10.1.0.2. For detailed instructions, please refer to the
Ruckus User Guide).
1 of 7 30/08/2012 15:06
Ruckus with Chilli | Coova :: Open Source Captive... http://www.coova.org/node/3960
Under the Configuration / Internet menu, we have our access point configured with the static IP address of 10.1.0.2
with a default gateway of 10.1.0.1.
We then connect our Ruckus access point's WAN port to our Ubuntu PC's eth1 interface with an Ethernet cable.
2 of 7 30/08/2012 15:06
Ruckus with Chilli | Coova :: Open Source Captive... http://www.coova.org/node/3960
For our purposes we want two wireless networks - one for an open captive portal and another for a 802.1x secure
network. Under the Configuration / Wireless menu, we enable both the Wireless 1 and Wireless 2 signals. You can, of
course, add more networks with or without wireless security.
3 of 7 30/08/2012 15:06
Ruckus with Chilli | Coova :: Open Source Captive... http://www.coova.org/node/3960
For the open signal we only had to configure the SSID, while for the 802.1x network we also set the required RADIUS
settings. The RADIUS settings will point to CoovaChilli, which will proxy the 802.1x authentication and provide RADIUS
accounting for the secure wireless sessions.
4 of 7 30/08/2012 15:06
Ruckus with Chilli | Coova :: Open Source Captive... http://www.coova.org/node/3960
On the Configuration / VLAN screen, we break up our networks by putting the different wireless signals onto different
VLANs. In our case, we decided to put the captive portal network on VLAN 100 and our 802.1x network on VLAN 200.
# Install CoovaChilli
wget http://coova-chilli.s3.amazonaws.com/coova-chilli_1.2.3-rc1_i386.deb
dpkg -i coova-chilli_1.2.3-rc1_i386.deb
Using the new multiple instance configuration syntax for CoovaChilli, we have the following configuration files:
/etc/chilli/config:
5 of 7 30/08/2012 15:06
Ruckus with Chilli | Coova :: Open Source Captive... http://www.coova.org/node/3960
HS_UAMSECRET=my-uam-secret
HS_UAMSERVER=my-company.com
HS_UAMFORMAT=http://\$HS_UAMSERVER/hotspot
# ... and so on ...
/etc/chilli/eth1.100/config:
/etc/chilli/eth1.100/chilli.conf:
include /etc/chilli/eth1.100/main.conf
include /etc/chilli/eth1.100/hs.conf
include /etc/chilli/eth1.100/local.conf
ipup /etc/chilli/up.sh
ipdown /etc/chilli/down.sh
/etc/chilli/eth1.200/config:
/etc/chilli/eth1.200/chilli.conf:
include /etc/chilli/eth1.200/main.conf
include /etc/chilli/eth1.200/hs.conf
include /etc/chilli/eth1.200/local.conf
ipup /etc/chilli/up.sh
ipdown /etc/chilli/down.sh
Starting chilli:
/etc/init.d/chilli start
While this example isn't exactly a comprehensive tutorial on setting up Ubuntu, Ruckus APs, and CoovaChilli, it does
show one of many possible configurations for using Ruckus access points with the CoovaChilli access controller.
6 of 7 30/08/2012 15:06
Ruckus with Chilli | Coova :: Open Source Captive... http://www.coova.org/node/3960
7 of 7 30/08/2012 15:06