Captive Portal stops firewall rules
I have pfSense 2.3.2-RELEASE (amd64) with captive portal enabled.
I am trying to allow ping from one computer in LAN (for example 192.168.1.72) to whatever public ip (for example 126.96.36.199), so i make a rule in firewall on LAN to allow ping from this computer (192.168.1.72) to the public ip (188.8.131.52). But the rule doesn't work, and i have to put the computer ip in the captive portal to allow this ping.
what can i do?
Captive portal, by design, breaks the internet.
If you want the traffic to flow prior to logging in through the portal you have to make an exception for that traffic in the portal.
2.3.2 is ancient. Upgrade.
@derelict Is there a way to allow all traffic to other LAN in the captive portal? because I am trying to make VPN site-to-site and i think that the captive portal is blocking the traffic.
you can give me a stable version to upgrade because i am reading about bugs in almost all versions
No. Captive portal blocks any traffic unless the user is either logged in through the portal or some sort of bypass is present in the portal.
If you don't want to block traffic why are you running captive portal?
You should be running pfSense 2.4.4
@derelict I am running captive portal because i am using squid proxy
That makes no sense.
@derelict If any user remove the proxy from internet options, he will access the free internet because i am using non transparent proxy.
I have some applications that don't work with transparent proxy.
So block the traffic to the internet with firewall rules, not a captive portal.
If your non-transparent proxy listens on 3128/3129, pass that and block connections to 80/443.
@derelict Thank you, i will try this, and hope that pfSense 2.4.4 will work without problems