I added both directives for internal and managed to my interface config in my
pf.conf file, worked like a charm.
[interface eth0]
ip=blah
mask=255.255.255.0
gateway=10.2.1.1
type=management,internal
enforcement=vlan
Jake Sallee
Godfather of Bandwidth
System Engineer
University of Mary Hardin-Baylor
900 College St.
Belton, Texas
76513
Fone: 254-295-4658
Phax: 254-295-4221
From: Sallee, Stephen (Jake)
Sent: Wednesday, November 30, 2011 4:48 PM
To: [email protected]
Subject: new install of 3.03 won’t start
Hello All!
I am setting up a new server with 3.0.3 and I have gotten to the first instance
of starting the PF services but I keep getting this error:
Starting PacketFence...Checking configuration sanity...
FATAL - internal network(s) not defined!
But I don’t know where to go to fix it… any ideas?
Jake Sallee
Godfather of Bandwidth
System Engineer
University of Mary Hardin-Baylor
900 College St.
Belton, Texas
76513
Fone: 254-295-4658
Phax: 254-295-4221
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
