Hi Andi, On 04/18/2012 11:20 AM, Morris, Andi wrote: > Hi all, > > I’m just configuring our live servers (been on a dev network until > now). I set everything up following the admin guide, and everything was > going well and I could access the web interface successfully. Until I > started to customise the pf.conf and setup freeradius on the box. > Unfortunately I’m unsure at which point I lost it. > > Packetfence was installed using installer.pl and configured using > configurator.pl > > I can successfully ping the interface, and SSH to the box on the same > interface with no issues. The services startup ok as shown below in the > packetfence.log: > > I was running version 3.2 on my dev boxes, and the live box is now on > 3.3. I copied some settings from the pf.conf between boxes, but tried > not to do anything that was not compatible with the new version. > >
It probably caused by the firewall. Review the currently running firewall configuration: # iptables -L -nv and make sure that the management-input chain is jumped to from the management interface you expected. If you need to alter the default rules, firewall rules comes from conf/iptables.conf. Regards, -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
