PacketFence is a fully supported, trusted, Free and Open Source network access control (NAC) solution. Boasting an impressive feature set including a captive-portal for registration and remediation, centralized wired and wireless management, powerful BYOD management options, 802.1X support, layer-2 isolation of problematic devices; PacketFence can be used to effectively secure networks small to very large heterogeneous networks.
PacketFence is deployed in a routed topology, with a hostname of packetfence.xxx.yy, users landing in the registration VLAN are not able to reach the captive portal as the FQDN is resolved via the default Debian entry in /etc/hosts pointing at 127.0.1.1.
Work around we're using at the moment is to hash out the default entry in the /etc/hosts file and then restart pfdns.
This appears to be a re-occurrence of the following bug: https://github.com/inverse-inc/packetfence/issues/5765
PacketFence is deployed in a routed topology, with a hostname of packetfence.xxx.yy, users landing in the registration VLAN are not able to reach the captive portal as the FQDN is resolved via the default Debian entry in /etc/hosts pointing at 127.0.1.1.
Work around we're using at the moment is to hash out the default entry in the /etc/hosts file and then restart pfdns.