Thank you mates
LT
Em 2017-12-08 12:16, Roger Faria via
PacketFence-users escreveu:
> Yes Luis, my cluster acts the same way.
>
> On Thu, Dec 7, 2017 at 8:27 PM, Durand fabrice via
PacketFence-users wrote:
>
>>
Yes this is normal, the dhcp scope is divided by 2 so only 2 servers can
ru
Fabrice comment's:
Because for PacketFence a device is a mac address, not a ip.
If you hit the portal and if PacketFence is not able to a an IP to MAC then you
will have an error message on the portal.
Reply: I understand. Unfortuantely, we wish to manage users accesses to
internal resources,
Le 2017-12-08 à 09:45, Benoît Dubé via PacketFence-users a écrit :
>
> Merci beaucoup Fabrice,
>
>
> When external users are redirected to the PacketFence portal, IP
> packets contain the user's IP. I can install the DHCP remote sensor
> on the server, but question is why to do that if the IP in
Merci beaucoup Fabrice,
When external users are redirected to the PacketFence portal, IP packets
contain the user's IP. I can install the DHCP remote sensor on the server, but
question is why to do that if the IP info is already known by PacketFence?
Note: DNS, DHCP and AD will always be ava
Hi all,
My packetfence 7.3 cluster works great but I have a couple questions and I
hope you guys can help!
1. After my uses registers a device, it take a bit for my packetfence to
talk to the switch and the switch to change vlans so on the enabling
network access page the status bar runs and mess
Yes Luis, my cluster acts the same way.
On Thu, Dec 7, 2017 at 8:27 PM, Durand fabrice via PacketFence-users <
packetfence-users@lists.sourceforge.net> wrote:
> Yes this is normal, the dhcp scope is divided by 2 so only 2 servers can
> run dhcpd.
>
>
>
> Le 2017-12-07 à 18:01, Luís Torres via Pac