Barry
Well, I'm glad you asked I am having a bit if an issue. This was a
working ( although limited since not fully deployed ) 3.1.0 box.
Now when I try to start pf I get the following:
Starting PacketFence...Checking configuration sanity...
Use of uninitialized value $net{"named"} in pattern match (m//) at
/usr/local/pf/lib/pf/pfcmd/checkup.pm line 362.
Use of uninitialized value $net{"dhcpd"} in pattern match (m//) at
/usr/local/pf/lib/pf/pfcmd/checkup.pm line 369.
FATAL - please define exactly one management interface
FATAL - internal network(s) not defined!
From what I can see from the provided config files, the followings
needs to be modified:
- Remove the entire [192.168.11.0] section from networks.conf. This is
your management network and don't need to be specified in the
networks.conf file
- You seems to be missing an isolation interface / network. PF will
complain if any of those (registration / isolation) is missing.
Try these fixes and let me know.
Thanks!
--
Derek Wuelfrath
[email protected] <mailto:[email protected]> :: +1.514.447.4918
x110 :: www.inverse.ca <http://www.inverse.ca>
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>)
and PacketFence (www.packetfence.org <http://www.packetfence.org>)
------------------------------------------------------------------------------
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
