Hey everyone,
I want to configure PacketFence as a RADIUS-only server (Clusterd with 3 nodes,
which works) and I am crying my eyes out.
When I do a radtest there is no connection on localhost:18120.
When I do a portscan with lsof on the machine, there is no service on port
18120.
When I restart the radius services everything is started up to
packetfence-radiusd-acct.service.
When I check journalctl -xeu packetfence-radiusd-acct.service:
Error: Failed binding to acct address * port 1823 bound to server packetfence:
Address already in use
Error: /usr/local/pf/raddb/acct.conf[8]: Error binding to port for 0.0.0.0 port
1823
And then I did a port scan:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
docker-pr 2353150 root 4u IPv4 91574364 0t0 UDP *:1823
So the docker proxy is reserving a port that I need for radiusd-acct and for a
RADIUS request?
In Configuration - System Configuration - RADIUS - General Configuration I have
deselected everything, including the other columns.
In the Authentication Sources I created a RADIUS-Source and created a
Authentication rule "catchall" and assigned the Default-Realm under Associated
Realms.
In the Defalt Realm i left all unchanged.
When I try out a Connection Profile with my AD query (without joinig my AD) and
everthing works fine in the test-captive portal.
Can someone help? Thanks for your help.
Lennart
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
