[Chilli] Radsec config

[David Bird]

Chilli in radsec mode will connect to port 2083 at radiusserver1. The
radiusauth/acctport are used to control what local ports the radsec proxy
binds to. You can leave them on the default RADIUS ports. Then move your
radsecproxy server to port 2083 instead.


On Mon, Feb 17, 2014 at 10:36 AM, Peter Wagner <peter.wagner at unwired.at>wrote:

> Hi,
>
> i configured chilli to use radsec
>
> radiusserver1   "192.168.1.1"
> radiusserver2   "192.168.1.1"
> radiusauthport  2084
> radiusacctport  2084
> sslkeyfile      /etc/ssl/radsec/radsec.key
> sslcertfile     /etc/ssl/radsec/radsec_certificate.crt
> sslcafile       /etc/ssl/radsec/radsec_certificate.crt
> radiussecret    radsec
> radsec
>
>
> and radsecproxy is listening on 192.168.1.1:2084 and waiting for requests.
>
> As it seems chilli trys to bind to 0.0.0.0
>
> as i get this message on startup:
>
> radius.c: 1315: 0 (Debug) RADIUS client 0.0.0.0:2084
> radius.c: 1315: 0 (Debug) RADIUS client 0.0.0.0:2084
> radius.c: 1318: 98 (Address already in use) bind() failed!
>
>
> What am i doing wrong?
>
> With kind regards
> Peter
> _______________________________________________
> Chilli mailing list
> Chilli at coova.org
> http://lists.coova.org/cgi-bin/mailman/listinfo/chilli
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20140218/5b0b5233/attachment.html>