On Thu, Jul 5, 2012 at 3:31 AM, Mark Holmes <[email protected]> wrote: > Hi Kim, > > Do > > radiusd -X > > and review the debug output.
radiusd when started with -X appears to be running fine, output ending with: Listening on authentication address * port 1812 as server packetfence Listening on accounting address * port 1813 as server packetfence Listening on command file /var/run/radiusd/radiusd.sock Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Ready to process requests. It does not start with the other processes when starting packetfence. Its been suggested this is due to my configuration not requiring radius, I am starting it for testing purposes. thanks -kim ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
