Hello, Try that:
/usr/local/pf/addons/pf-main.pl accept with y /usr/local/pf/bin/pfcmd service pf restart Retry to ask for DHCP. Thanks, Ludovic Zammit [email protected] <mailto:[email protected]> :: +1.514.447.4918 (x145) :: www.inverse.ca <http://www.inverse.ca/> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu <http://www.sogo.nu/>) and PacketFence (http://packetfence.org <http://packetfence.org/>) > On Apr 15, 2019, at 4:14 PM, Eric Rolleman <[email protected]> wrote: > > netstat -nlp | grep 67 : > udp 0 0 0.0.0.0:67 0.0.0.0:* > 230369/pfdhcp > udp 0 0 0.0.0.0:67 0.0.0.0:* > 230369/pfdhcp > udp 0 0 10.0.22.252:67 0.0.0.0:* > 230369/pfdhcp > udp 0 0 10.0.21.252:67 0.0.0.0:* > 230369/pfdhcp > > /usr/local/pf/bin/pfcmd service pfdhcplistener status > Service Status PID > packetfence-pfdhcplistener.service started 86675 > > /usr/local/pf/bin/pfcmd service pfdhcp status > Service Status PID > packetfence-pfdhcp.service started 230369 > > Seems to be running. > Interface eth0.21 is configured to be registration > > Interface info: > > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group > default qlen 1000 > link/ether 00:15:5d:83:cc:04 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.22/16 brd 192.168.255.255 scope global eth0 > valid_lft forever preferred_lft forever > inet6 fe80::215:5dff:fe83:cc04/64 scope link > valid_lft forever preferred_lft forever > 4: eth0.22@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue > state UP group default qlen 1000 > link/ether 00:15:5d:83:cc:04 brd ff:ff:ff:ff:ff:ff > inet 10.0.22.252/24 brd 10.0.22.255 scope global eth0.22 > valid_lft forever preferred_lft forever > inet6 fe80::215:5dff:fe83:cc04/64 scope link > valid_lft forever preferred_lft forever > 5: EXAMPLE-b@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue > state UP group default qlen 1000 > link/ether 0e:aa:47:f5:0a:30 brd ff:ff:ff:ff:ff:ff link-netnsid 0 > inet 169.254.0.2/30 brd 169.254.0.3 scope global EXAMPLE-b > valid_lft forever preferred_lft forever > inet6 fe80::caa:47ff:fef5:a30/64 scope link > valid_lft forever preferred_lft forever > 7: eth0.21@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue > state UP group default qlen 1000 > link/ether 00:15:5d:83:cc:04 brd ff:ff:ff:ff:ff:ff > inet 10.0.21.252/24 brd 10.0.21.255 scope global eth0.21 > valid_lft forever preferred_lft forever > inet6 fe80::215:5dff:fe83:cc04/64 scope link > valid_lft forever preferred_lft forever > > excerpt from network.conf: > > [10.0.21.0] > dns=10.0.21.252 > split_network=disabled > dhcp_start=10.0.21.10 > gateway=10.0.21.252 > domain-name=vlan-registration.example.com > <https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvlan-registration.example.com%2F&data=02%7C01%7C%7C3eea9ea68a15420ea06a08d6c198c26e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636909259168134490&sdata=TpxotHR5zXqggE%2B6BN9BKWQZHrXC3JFk5%2FszSZRDTaI%3D&reserved=0> > nat_enabled=disabled > named=enabled > dhcp_max_lease_time=30 > fake_mac_enabled=disabled > dhcpd=enabled > dhcp_end=10.0.21.246 > type=vlan-registration > netmask=255.255.255.0 > dhcp_default_lease_time=30 > > From: Ludovic Zammit <[email protected]> > Sent: April 15, 2019 04:52 > To: Eric Rolleman <[email protected]> > Cc: [email protected] > Subject: Re: [PacketFence-users] Registration VLAN DHCP not working > > Hello Eric, > > Do you have the pfdhcp pfdhcplistener services running ? > > What is the output of the command: > > netstat -nlp | grep 67 > > Does eth0.21 is configured has a registration interface ? > > Thanks, > > Ludovic Zammit > [email protected] <mailto:[email protected]> :: +1.514.447.4918 (x145) :: > www.inverse.ca > <https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.inverse.ca&data=02%7C01%7C%7C3eea9ea68a15420ea06a08d6c198c26e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636909259168114482&sdata=WOXXddwqOvMbpkyR6han2622HxHeLzIN1hBRtE%2B1XeE%3D&reserved=0> > Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu > <https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sogo.nu&data=02%7C01%7C%7C3eea9ea68a15420ea06a08d6c198c26e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636909259168124486&sdata=QCmhzPlfF6pavGw7ChNMHNGiLfYhlwmNa5KE4fNCaJQ%3D&reserved=0>) > and PacketFence (http://packetfence.org > <https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpacketfence.org&data=02%7C01%7C%7C3eea9ea68a15420ea06a08d6c198c26e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636909259168124486&sdata=VrhADODlXJwQOHndAlVBzD%2Fv%2FGRiSy31V2KdGM7Flwc%3D&reserved=0>) > > > > > > > On Apr 14, 2019, at 12:34 PM, Eric Rolleman via PacketFence-users > <[email protected] > <mailto:[email protected]>> wrote: > > I need to help troubleshooting DHCP on my registration VLAN. > > I used tcpdump to see if DHCP packets are making it to the packetfence server > and they are: > > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on eth0.21, link-type EN10MB (Ethernet), capture size 262144 bytes > 09:24:40.932786 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from 00:15:5d:83:cc:03 (oui Unknown), length 300 > 09:24:44.861274 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from 00:15:5d:83:cc:03 (oui Unknown), length 300 > 09:24:48.827419 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from 00:15:5d:83:cc:03 (oui Unknown), length 300 > 09:24:56.778174 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, > Request from 00:15:5d:83:cc:03 (oui Unknown), length 300 > > However, PacketFence isn’t offering an IP to the client. > > Here is my networks.conf file (I used the WebUI to configure the networks): > > [10.0.22.0] > dns=10.0.22.252 > split_network=disabled > dhcp_start=10.0.22.10 > gateway=10.0.22.252 > domain-name=vlan-isolation.example.com > <https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvlan-isolation.example.com%2F&data=02%7C01%7C%7C3eea9ea68a15420ea06a08d6c198c26e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636909259168134490&sdata=ziE0Y6o8zK%2BBBa4BBQYWAxvk4Puypnordly4MOCuHt8%3D&reserved=0> > nat_enabled=disabled > named=enabled > dhcp_max_lease_time=30 > fake_mac_enabled=disabled > dhcpd=enabled > dhcp_end=10.0.22.246 > type=vlan-isolation > netmask=255.255.255.0 > dhcp_default_lease_time=30 > > [10.0.21.0] > dns=10.0.21.252 > split_network=disabled > dhcp_start=10.0.21.10 > gateway=10.0.21.252 > domain-name=vlan-registration.example.com > <https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvlan-registration.example.com%2F&data=02%7C01%7C%7C3eea9ea68a15420ea06a08d6c198c26e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636909259168134490&sdata=TpxotHR5zXqggE%2B6BN9BKWQZHrXC3JFk5%2FszSZRDTaI%3D&reserved=0> > nat_enabled=disabled > named=enabled > dhcp_max_lease_time=30 > fake_mac_enabled=disabled > dhcpd=enabled > dhcp_end=10.0.21.246 > type=vlan-registration > netmask=255.255.255.0 > dhcp_default_lease_time=30 > > If I statically set an IP to the client (10.0.21.101/24), I can ping the > client from PacketFence and the client can ping PacketFence. Any idea what I > am missing? > _______________________________________________ > PacketFence-users mailing list > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/packetfence-users > <https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fpacketfence-users&data=02%7C01%7C%7C3eea9ea68a15420ea06a08d6c198c26e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636909259168144498&sdata=2ADRcxvVDTDESG5tWfXFjBU83fEABXnLr41c9wMs9y0%3D&reserved=0>
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
