Bug #868
closed
The issue is likely that the two are competing for trying to redirect connections going to port 80 and the squid package is the one that gets the redirect.
It may need a redirect in ipfw that catches attempts to access squid by systems that are not logged into the captive portal.
The ipfw fwd gets hit, but I believe after that it gets hit by the pf rdr for Squid. A 'no rdr' for traffic destined to the interface IP (even manually entered as a user rule if the ordering suffices) would probably fix.
I had the same problem and found a workaround.
Edit the following line in /usr/local/captiveportal/index.php
$ourhostname = „{$ifip}:8000“; ändern in $ourhostname = „<IP pfsense>:8000“;
Then it should work fine again.
Burkart Orlowski wrote:
I had the same problem and found a workaround.
Edit the following line in /usr/local/captiveportal/index.php
$ourhostname = „{$ifip}:8000“; and change it to
$ourhostname = „<IP pfsense>:8000“;
Then it should work fine again.
add header("Connection: close"); in /usr/local/captiveportal/index.php will fix the issue
header("Expires: 0");
header("Cache-Control: no-store, no-cache, must-revalidate");
header("Cache-Control: post-check=0, pre-check=0", false);
header("Pragma: no-cache");
header("Connection: close");
With adding :header("Connection: close"), Portal Captive work fine even squid is installed.
Thanks
- Status changed from New to Feedback
- Status changed from Feedback to Closed
Also available in: Atom
PDF