Developers guide

Chapter 5

Configuration 26

For dhcpd, make sure that the clients DHCP requests are correctly forwarded (IP Helpers in the remote

routers) to the PacketFence server. Then make sure you followed the instructions in the DHCP and DNS

Server Configuration (networks.conf) for your locally accessible network.

If we consider the network architecture illustrated in the above schema, conf/pf.conf will include the

local registration and isolation interfaces only.

[interface eth0.2]

enforcement=vlan

ip=192.168.2.1

type=internal

mask=255.255.255.0

[interface eth0.3]

enforcement=vlan

ip=192.168.3.1

type=internal

mask=255.255.255.0

Note

PacketFence will not start unless you have at least one internal interface, so you need

to create local registration and isolation VLANs even if you don’t intend to use them.

Also, the internal interfaces are the only ones on which dhcpd listens, so the remote

registration and isolation subnets need to point their DHCP helper-address to those

particular IPs.

Then you need to provide the routed networks information to PacketFence. You can do it through the GUI

in Administration � Networks (or in conf/networks.conf).

conf/networks.conf will look like this:

[192.168.2.0]

netmask=255.255.255.0

gateway=192.168.2.1

next_hop=

domain-name=registration.example.com

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