On Sun, Feb 06, 2022 at 04:08:14PM +0100, Maurizio Caloro wrote: > Thanks for your answer, please have a look: > > > root@Name:# systemctl status freeradius > ● freeradius.service - FreeRADIUS multi-protocol policy server > Loaded: loaded (/lib/systemd/system/freeradius.service; enabled; vendor > preset: enabled) > Active: active (running) since Sun 2022-02-06 08:57:45 CET; 7h ago > Docs: man:radiusd(8) > man:radiusd.conf(5) > http://wiki.freeradius.org/ > http://networkradius.com/doc/ > Process: 21647 ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx > -lstdout (code=exited, s> > Main PID: 21648 (freeradius) > Status: "Processing requests" > Tasks: 6 (limit: 8869) > Memory: 79.3M (limit: 1.0G) > CPU: 846ms > CGroup: /system.slice/freeradius.service > └─21648 /usr/sbin/freeradius -f -P > > root@name:# lsof -i :1812 > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > freeradiu 21648 freerad 8u IPv4 1149216 0t0 UDP *:radius
These results confirm that something *is* using the port. Specifically, it's "freeradius", which is apparently a user name, a program name, and a service name. > Freeradius -X > [SNIP] > Failed binding to auth interface enp3s0 address * port 1812 bound to server > default: Address already in use > /etc/freeradius/3.0/sites-enabled/default[59]: Error binding to port for > 0.0.0.0 port 1812 > root@name:# So... it's not surprising that you get this result when you try to use the port a second time. What result were you expecting to see? What are you trying to do?
