Hi,
I'm trying out the new version, and I've found if I set the management
interface to have a extra radius daemon, like this:
[image: Inline image 1]
radiusd won't start, because its already listening on that address:
server packetfence-cli { # from file
/usr/local/pf/raddb/sites-enabled/packetfence-cli
# Loading authenticate {...}
# Loading authorize {...}
# Loading post-proxy {...}
# Loading post-auth {...}
} # server packetfence-cli
auth: #### Opening IP addresses and Ports ####
listen {
type = "auth"
virtual_server = "packetfence"
ipaddr = 127.0.0.1
port = 18120
}
listen {
type = "auth"
virtual_server = "packetfence"
ipaddr = 1.2.3.4
port = 0
}
listen {
type = "auth"
virtual_server = "packetfence"
ipaddr = 1.2.3.4
port = 0
Failed binding to auth address 1.2.3.4 port 1812 bound to server
packetfence: Address already in use
/usr/local/pf/raddb/auth.conf[23]: Error binding to port for 1.2.3.4 port
1812
It's possibly worth fixing that in the gui so as to stop autofoot shooting?
Cheers,
David
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
