[Chilli] CoovaChilli & (non CoovaAP) AP
david at coova.com
Tue Mar 23 20:46:17 UTC 2010
You can bridge the networks so that chilli controls them both, or run
two instances of chilli. The instance handling the 802.1x network should
have these options defined:
$ chilli --help|grep proxy
--proxylisten=STRING Proxy IP address to listen on
--proxyport=INT Proxy UDP port to listen on (0 is off)
--proxyclient=STRING IP address of proxy client(s)
--proxysecret=STRING Radius proxy shared secret
And the 802.1x AP should use these settings for it's RADIUS.. chilli
will proxy the authentication, provide accounting, and still control the
network to enforce any limitations, etc.
On Tue, 2010-03-23 at 19:20 +0300, Anatoly Oreshkin wrote:
> I have wireless Access Point 3Com AirConnect 9150 configured with WPA2/AES
> and 802.1X EAP-PEAP-MSCHAPv2 authentication. It uses Free Radius server
> for authentication and wireless clients get ip fixed addresses from DHCP
> I configured this AP with second SSID (without security) in order for
> clients can authenticate through CoovaChilli using UAM method.
> It works.
> Now I would like to make both WPA2/802.1X and UAM authentication to work
> through CoovaChilli. I can specify CoovaChilli address as Radius server
> address in AP. But of course it's not enough. Is it possible at all to
> have CoovaChilli working in such configuration ?
> If so, how should I configure for this purpose CoovaChilli and Radius
> server ?
> Any hints.
> Chilli mailing list
> Chilli at coova.org
More information about the Chilli