Hi Ludovic,

We've confirmed we had it configured correctly.  Just wondering if it's a
limitation of the sensor with respect to DHCP reserved IPs.

On Tue, Mar 2, 2021 at 8:28 AM Ludovic Zammit <[email protected]> wrote:

> Hello Ted,
>
> If you followed the documentation it says to send it out to PF management
> interface or PF Management Virtual IP on the port 767.
>
> Check if you are not blocking UDP 767 from your DHCP server to PF
> management interface. Make sure alose the DHCP sensor services is started
> and running.
>
> You could do a quick check on the Packetfence server by doing a packet
> capture like so:
>
> tcpdump -I any port 767 -nn
>
> Thanks,
>
>
> Ludovic Zammit
> [email protected] ::  +1.514.447.4918 (x145) ::  www.inverse.ca
> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
> (http://packetfence.org)
>
>
>
>
>
>
>
>
> On Mar 1, 2021, at 1:25 PM, Ted Jones via PacketFence-users <
> [email protected]> wrote:
>
> We're using Microsoft DHCP server with the DHCP sensor installed but
> Packetfence is not getting the IP address of nodes that are assigned DHCP
> reservations.  Is this expected? Is there anything we're missing in order
> to see those addresses in Packetfence?
> _______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
>
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to