HI Adrian,

At the first sight, the config appears to be fine.

Is the DHCP process listening on the registration interface?  Use 'ps' 
to see the process status.

Thanks.

On 12-03-15 11:01 AM, Adrian Mulgrew wrote:
> Hi
>
> I'm still trying to setup my test PF installation.
> I have PF changing the VLAN from Mac Detection to Registration OK but
> once in the Registration VLAN the machine requests a DHCP IP address but
> PF never responds. I have wire shark running on the PF server and I can
> see the DHCP Requests arriving but the DHCP server in PF doesn't do
> anything.
> I have one physical Network card connected to the switch. Can you tell
> me how this port should be configured (Cisco). Is there anywhere else I
> should be checking.
>
> I've attached my setup config below.
>
> ------------------------Nic Startup scripts-------------------------------
> DEVICE=eth0
> BROADCAST=192.168.1.255
> IPADDR=192.168.1.5
> NETMASK=255.255.255.0
> NETWORK=192.168.1.0
> ONBOOT=yes
> TYPE=Ethernet
> GATEWAY=192.168.1.13
> DNS=8.8.8.8
> HWADDR=6c:62:6d:b6:df:11
> BOOTPROTO=none
> DNS1=62.6.40.162
> IPV6INIT=no
> USERCTL=no
> DNS2=194.72.0.98
>
>
> DEVICE=eth0.2
> IPADDR=192.168.2.1
> NETMASK=255.255.255.0
> ONBOOT=yes
> VLAN=yes
> BOOTPROTO=static
>
> DEVICE=eth0.3
> IPADDR=192.168.3.1
> BOOTPROTO=static
> NETMASK=255.255.255.0
> ONBOOT=yes
> VLAN=yes
>
> DEVICE=eth0.5
> IPADDR=192.168.5.1
> BOOTPROTO=static
> NETMASK=255.255.255.0
> ONBOOT=yes
> VLAN=yes
> -----------------------------------------
>
>
> ------------------------pf.conf----------------------------------------
> [alerting]
> #
> # alerting.emailaddr
> #
> # Email address to which notifications of rogue DHCP servers, violations
> with an action of "email", or any other
> # PacketFence-related message goes to.
> [email protected] <mailto:[email protected]>
>
> [database]
> #
> # database.pass
> #
> # Password for the mysql database used by PacketFence.
> pass=admin
>
>
> [general]
> domain=yourdomain.org <http://yourdomain.org>
> #Put your External/Infra DNS servers here
> dnsservers=4.2.2.2,4.2.2.1
> dhcpservers=192.168.2.1,192.168.3.1,192.168.5.1
>
> [trapping]
> registration=enabled
> detection=enabled
> range=192.168.2.0/24,192.168.3.0/24,192.168.5.0/24
> <http://192.168.2.0/24,192.168.3.0/24,192.168.5.0/24>
>
> [registration]
> auth=ldap
>
> [interface eth0]
> mask=255.255.255.0
> type=management
> gateway=192.168.1.1
> ip=192.168.1.5
>
> [interface eth0.2]
> mask=255.255.255.0
> type=internal
> enforcement=vlan
> gateway=192.168.2.1
> ip=192.168.2.1
>
> [interface eth0.3]
> mask=255.255.255.0
> type=internal
> enforcement=vlan
> gateway=192.168.3.1
> ip=192.168.3.1
>
> [interface eth0.5]
> mask=255.255.255.0
> type=internal
> enforcement=inline
> gateway=192.168.5.1
> ip=192.168.5.1
>
> [interface eth1]
> mask=255.255.255.0
> type=monitor
> enforcement=inline
> gateway=192.168.1.5
> ip=192.168.1.1
>
> -----------------------------------------
> --------------------------------networks.conf----------------------------
> [192.168.2.0]
> netmask=255.255.255.0
> gateway=192.168.2.1
> next_hop=192.168.2.254
> domain-name=registration.example.com <http://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
>
> [192.168.3.0]
> netmask=255.255.255.0
> gateway=192.168.3.1
> next_hop=192.168.3.254
> domain-name=isolation.example.com <http://isolation.example.com>
> dns=192.168.3.1
> dhcp_start=192.168.3.10
> dhcp_end=192.168.3.200
> dhcp_default_lease_time=300
> dhcp_max_lease_time=600
> type=vlan-isolation
> named=enabled
> dhcpd=enabled
>
> [192.168.5.0]
> netmask=255.255.255.0
> gateway=192.168.5.1
> next_hop=
> domain-name=inline.example.com <http://inline.example.com>
> dns=4.2.2.2,4.2.2.1
> dhcp_start=192.168.5.10
> dhcp_end=192.168.5.254
> dhcp_default_lease_time=300
> dhcp_max_lease_time=600
> type=inline
> named=disabled
> dhcpd=enabled
>
> -----------------------------------------
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
>
>
>
> _______________________________________________
> Packetfence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users


-- 
Francois Gaudreault, ing. jr
[email protected]  ::  +1.514.447.4918 (x130) ::  www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence 
(www.packetfence.org)

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to