This issue seems to be solved now. I just tested with :
packetfence-pfcmd-suid-4.0.0-0.20130430.el6.x86_64
packetfence-4.0.0-0.20130430.el6.noarch
and adding / removing networks as well as restarting services seems to work
properly.
Jake Sallee
Godfather of Bandwidth
System Engineer
University of Mary Hardin-Baylor
900 College St.
Belton TX. 76513
Fone: 254-295-4658
Phax: 254-295-4221
HTTP://WWW.UMHB.EDU
From: Sallee, Stephen (Jake) [mailto:jake.sal...@umhb.edu]
Sent: Friday, April 26, 2013 10:07 AM
To: packetfence-devel@lists.sourceforge.net
Subject: [PacketFence-devel] v4 Snapshot issue: Routed Networks
I am running:
packetfence-pfcmd-suid-4.0.0-0.20130426.el6.x86_64
packetfence-4.0.0-0.20130426.el6.noarch
I added 3 routed networks through the webGUI without any errors, however if I
run the pfcmd checkup command I get the following:
[root@localhost ~]# /usr/local/pf/bin/pfcmd checkup
Checking configuration sanity...
FATAL - networks.conf: Incomplete DHCP information for network 10.11.10.0
FATAL - networks.conf: Incomplete DHCP information for network 10.11.30.0
FATAL - networks.conf: Incomplete DHCP information for network 10.11.70.0
On closer inspection I noticed a difference between the way the networks that
are created through the normal webGUI are declared and the way the network
created in the configurator GUI are declared.
Here is the declaration from the webGUI:
[10.11.70.0]
dns=10.2.1.32
next_hop=10.2.1.1
gateway=10.11.70.1
dhcp_start=10.11.70.1
named=enabled
dhcp_max_lease_time=600
dhcpd=enabled
dhcp_end=10.11.70.254
netmask=255.255.255.0
dhcp_default_lease_time=600
Here is the declaration from the configurator page:
[192.168.2.0]
netmask=255.255.255.0
gateway=192.168.2.1
next_hop=
domain-name=registration.umhb.edu
dns=192.168.2.1
dhcp_start=192.168.2.10
dhcp_end=192.168.2.200
dhcp_default_lease_time=300
dhcp_max_lease_time=600
type=vlan-registration
named=enabled
dhcpd=enabled
Notice the "domain-name" and "type" fields are not present. Manually adding
the "domain-name" field to the networks.conf file fixes the error thrown by
pfcmd checkup. However, I am not sure if the "type" field is important or not.
BTW, this error stops PF from starting / restarting.
Jake Sallee
Godfather of Bandwidth
System Engineer
University of Mary Hardin-Baylor
900 College St.
Belton TX. 76513
Fone: 254-295-4658
Phax: 254-295-4221
HTTP://WWW.UMHB.EDU
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
PacketFence-devel mailing list
PacketFence-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-devel
