After running both ./installer.pl and ./configurator.pl scipts, I try to
start PacketFence by running /sbin/service packetfence start
I get the following error:
root@packetfence sbin]# /sbin/service packetfence start
starting PacketFence....Checking configuration sanity...
FATAL = please define exactly one management interface
FATAL = internal network(s) not defined
FATAL = networks.conf cannot be empty when services.dhcpd is enabled
FATAL = networks.conf cannot be empty when services.named is enabled
I can now see that /usr/local/pf/conf/networks.conf is empty.
I would appreciate any direction as to how I can manually define my
networks.conf file. (or am I not doing something right so that
networks.conf is not being generated?)
When I run configurator.pl, I am selecting:
1.) PacketFence standalone (Basic configuration)
Enforcement choice = 1.) VLANS
I've tried this on two setups. One is a virtual machine with 3 virtual
NICS. The other is a Dell Poweredge sc430 with a nic in the mb as well
as a dual port Intel nic. Both are running CentOS 6. Both
configurations are giving me the same identical empty networks.conf file.
I'm happy to read a FAQ, or any direction one might have if I knew where
to look. To see a working networks.conf file would be a real help.
Thanks for your time.
Chuck
I I would appreciate
------------------------------------------------------------------------------
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
