Re: [PacketFence-users] Captive Portal is only accessible when iptables is disabled

2024-04-10 Thread Daniel Zook via PacketFence-users
Hi Eric, I saw your post from 8/21/23: https://sourceforge.net/p/packetfence/mailman/message/37887654/ I did not experience the problem on our test server (ZEN, 13.1.0), but I ran into the same issue with a brand-new cluster install (ISO 13.1.0). I found that it is because the DNS servers are

Re: [PacketFence-users] Captive Portal is only accessible when iptables is disabled

2024-04-10 Thread Daniel Zook via PacketFence-users
I compared the iptables.conf file between the ZEN and the ISO/Cluster install, and they are exactly the same. They both allow DNS inbound via these entries: :input-internal-vlan-if - [0:0] # DNS -A input-internal-vlan-if --protocol tcp --match tcp --dport 53 --jump ACCEPT -A

[PacketFence-users] Captive Portal is only accessible when iptables is disabled

2023-08-25 Thread Eric Rolleman via PacketFence-users
I recently upgraded my PacketFence install to 13.0.0 from 11.3.0 (in case this is related). I now have this issue where the captive portal is only available to those on the Registration Vlan if the iptables service is turned off. I have an interface assigned to Management, Registration and