You have to forward the DHCP requests to packet fence. That is the only
way it can determine the MAC address on a routed network. Think about it.
All PF sees is the IP connecting. Without getting the DHCP data forwarded
to it, it can't map that to a MAC address.
On Wed, Sep 10, 2014 at 11:57 AM, Brian Motts <[email protected]> wrote:
> We are using a remote DHCP server for the DHCP on registration/isolation.
> We have setup the remote networks in the packetfence server. The DHCP
> uses the PacketFence server DNS. Packetfence is over a VPN from the remote
> network and we dont want to forward DHCP requests over the VPN.
>
> We are getting an error when we try to connect:
> *Sorry!*
>
> Your computer was not found in the PacketFence database. Please reboot to
> solve this issue.
>
>
> I am assuming this is because of the remote DHCP server, is there any way
> to make it work with this setup or do we have to forward DHCP requests over
> the VPN?
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
