General question about RadSec implementation on FR 3.2.x

[Alan DeKok]

On Apr 19, 2025, at 1:26 PM, Dominic Stalder <dominic.stalder at bluewin.ch> wrote:
> 2. but I also sent the respective output of "radiusd -fxx -l stdout“ in my email before and got the following error instead (see full output below), as recommended in the „freeradius -X“ output:
> 
> Failed opening auth address :: port 1812 bound to server default: Address family not supported by protocol
> /usr/local/etc/raddb/sites-enabled/default[246]: Error binding to port for :: port 1812

  That's very odd.  But likely explained by the next issue:

> _EXIT(1) CALLED src/main/process.c[6325].  Last error was: /usr/local/lib/proto_auth.so: cannot open shared object file: No such file or directory
> 
> 3. At the same time, I just recognized, that when I started the debug output with "radiusd …“, it shows me output of FR 3.2.5:
> 
> root at id-radiustest1:/etc/freeradius/sites-enabled# radiusd -fxx -l stdout
> FreeRADIUS Version 3.2.5
> …
> 
> BUT I have FR 3.2.7 in place and started it with „freeradius -fxx -l stdout“ instead and now the correct FR instance is trying to start:

  You have two copies of FreeRADIUS installed on the same machine.  Don't do that.


> Thanks for somehow showing the right direction, even I don’t understand, why FR 3.2.5 is still in place when starting with „freerad -fxx -l stdout“ instead of „freeradius -fxx-l stdout“,

  See the local configuration on your machine.  i.e. PATH variable, and whatever else you've configured.

> any idea how I can cleanup this version situation on our freeradius server?

  Use your local OS tools to remove one of versions of FreeRADIUS.

  Alan DeKok.