I was having similar issues on a fresh install of packetfence 13.1 on rocky linux using the RPMs.
I had trouble creating the isolation and registration sub-interfaces (vlans), with the config not sticking on the configurator.. as such, the haproxy-portal config was not having the correct interface settings / the redirect.lua script seems to have been missing options. Im still troubleshooting.. but its very weird. On Tue, May 7, 2024 at 11:50 AM Nate Tremmel via PacketFence-users <packetfence-users@lists.sourceforge.net> wrote: > > I’m running Packetfence 13.1 from ISO and have a registration VLAN. I am > using Merakis APs with radius role by VLAN. My test computer joins the > network, get a registration VLAN IP from the packet fence server, and it > tries to open the fqdn of the packetfence server and get a connection timed > out error. On the computer, the fqdn is resolving to 66.70.255.147 which > seems to be what is supposed to happen in the admin settings and I can ping > that IP. I have allowed access to the management IP through the firewall for > HTTPS from the registration VLAN. > > Any advice would be welcome. > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
