RE: error after updating to freeradius 2.0.1

2008-02-12 Thread Joep Ruiter
>> > Check that nothing is listening on port 1812, even for IPv6. >> >> Nothing listening except for ssh. >Since ssh is TCP, you know that radius is UDP and you need to check with >"netstat -ulnp" Oops, thanks! There was indeed another radius-service running. Killed it and the error's gone

Re: error after updating to freeradius 2.0.1

2008-02-12 Thread Alan DeKok
Joep Ruiter wrote: ... > This is the full log: ... > radiusd: Opening IP addresses and Ports > listen { > type = "auth" > ipaddr = * > port = 0 > ERROR: Failed to open socket: > /etc/freeradius/radiusd.conf[182]: Error binding to port for 0.0.0.0 port > 1812 The

Re: error after updating to freeradius 2.0.1

2008-02-11 Thread Damjan
> > Check that nothing is listening on port 1812, even for IPv6. > > Nothing listening except for ssh. Since ssh is TCP, you know that radius is UDP and you need to check with "netstat -ulnp" > ERROR: Failed to open socket: > /etc/freeradius/radiusd.conf[182]: Error binding to port for 0.0.0.

RE: error after updating to freeradius 2.0.1

2008-02-11 Thread Joep Ruiter
> Check that nothing is listening on port 1812, even for IPv6. Nothing listening except for ssh. > Also try posting the full debug log. Maybe there's another "listen" > section which is conflicting with the 0.0.0.0:1812. > > Alan DeKok. > - > List info/subscribe/unsubscribe? See http://www.

Re: error after updating to freeradius 2.0.1

2008-02-11 Thread Alan DeKok
Joep Ruiter wrote: > ERROR: Failed to open socket: > /etc/freeradius/radiusd.conf[182]: Error binding to port for 0.0.0.0 port > 1812 This is likely due to the system having IPv6 support. Version 2.0 adds IPv6, and there are issues with binding to IPv4 and IPv6 sockets. > All 1.1.x versions h