FreeRadius - Failed binding to authentication address

Question

When I run the following command, I can get successfull result.

root@ubuntu:/home/can# radtest user password 127.0.0.1 1812 testing123

Sending Access-Request of id 78 to 127.0.0.1 port 1812

User-Name = "user"
User-Password = "password"
NAS-IP-Address = 127.0.1.1
NAS-Port = 1812
Message-Authenticator = 0x00000000000000000000000000000000

rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=78, length=20

---

However When I run the "freeradius -X" , I get error message as following :

.....

Failed binding to authentication address * port 1812: Address already in use /etc/freeradius/radiusd.conf[250]: Error binding to port for 0.0.0.0 port 1812

Please Help Me

Thank you for your efforts.

Can

Hairsplitter

radiusd is already running. sudo service radiusd stop – Cherish

@ArranCudbard-Bell That worked however I send the request via NTRadPing Radius Server Test Tool, I get : Ready to process requests. Ignoring request to authentication address * port 1812 from unknown client 192.168.111.1 port 55604.. Do you have any suggestion Bell? Thank you so much – Hairsplitter

Answer 1

radiusd is already running. sudo service freeradius stop will stop it, and allow freeradius -X to bind to the address/port that was previously used by the RADIUS daemon.

Cherish

I don't see a question, I see a statement 'Please help me'. I actually provided the answer as a comment to the original post, just decided to make it official. – Cherish

Answer 2

Run 'service freeradius restart' and 'service freeradius stop' commands Then run the command,'freeradius -X' you will not face binding issue anymore.

Diurnal

Answer 3

Even having finished the service, there were pending zombie process. Searching for a zumbi process I´ve found one:

[root@localhost sites-enabled]# ps aux | grep radi
radiusd   25042  0.0  0.7 186360 14980 ?        Ssl  Fev17   0:00 /usr/sbin/radiusd -d /etc/raddb

[root@localhost sites-enabled]# kill -9 25042

Service was start sucessfully after this.

Emory

Answer 4

Basically the port freeradius is looking to use is already in use by another background running instance of freeradius. Ending the first instance of freeradius will allow you to use that same port for the newly run instance.

Yellow

Answer 5

In my case it was loading two configuration files declaring the same listen. The error looked strange because there was nothing else listening on that port.

Boche