Squid Returned to Packages *** PLEASE TEST ***
-
Squid can be run on any port in transparent mode. In Smoothwall, it runs on port 800. In pfSense, it is set up to run on port 80. The important thing is that the pf redirection and the port squid listens on must be the same. Maybe it is a good idea to have squid on port 3128, and just change the redirect rule in pf accordingly, then this whole issue with the webgui goes away.
my 2c.
Nicki -
I for one am happy to see squid working again, if it means running the webgui on a different port thats fine with me. I run it on https anyway. We should just thank everyone that took the time from it not working to working. So that being said;
Thank you to everyone that helped make squid work again. ;D
-
well squid doesnt crash anymore. I have yet to see any of the ACLs actually work. no matter what i do to the settings, it runs just like as if i didn't have squid installed.
-
Not sure about the acls, something might just be in the wrong order.
When I try windowsupdate with squid in transparent mode it fails to download the updates. When I enter the client IP in the unrestricted hosts field windowsupdate works again. So I am pretty sure there is something marginally worng.
Not suprised that authentication does not work. It was entirely untested.
-
I have an update, again…
I have changed some routing stuff, so that in transparent mode both the webgui and squid can run on port 80.
In normal mode (non transparent) you can't run them on the same port, because in that case the browser sends the packages to pfsense's ip...Ok here the updates...
Delete
if (($post['transparent_proxy'] == 'on')) { $port = 80; } else { $port = trim($post['proxy_port']); }change
if ($port == $webgui_port) {in
if (($post['transparent_proxy'] != 'on') && ($port == $webgui_port)) {then change
$conf .= "http_port {$real_ifaces[$i][0]}"; if (($settings['transparent_proxy'] == 'on')) { $conf .= ":80 transparent\n"; } else { $conf .= ":$port\n"; }in
if (($settings['transparent_proxy'] == 'on')) { $conf .= "http_port 127.0.0.1:80 transparent\n"; } else { $conf .= "http_port {$real_ifaces[$i][0]}:$port\n"; }and finally
change$rules .= "rdr on $iface proto tcp from any to !($iface) port 80 -> ($iface) port 80\n";in
$rules .= "rdr on $iface proto tcp from any to !($iface) port 80 -> 127.0.0.1 port 80\n"; -
I compiled a complete new squid to be sure it was not an option why the blacklist wouldn't work, but that sisn't help, so I think it's not that squid doesn't support acl, I know it did block the windows update site allready, but I wanted to be sure…
-
attaching to 127.0.0.1 seems like a good idea.
I'll change that.
-
might have to resort to the old Desk-Check method and do a manual trace thru the code to see if the logical flow of commands surrounding the blacklist makes sense. It can be extremely time consuming but it helps to pinpoint where the problems may be.
-
well, put the deny all acl on top and see if that works :-)
-
I upgraded package squid-2.5.14_2 to 2.6.5
Squid began to issue error:./restart_squid.sh
Restarting Squid whith config
2006/12/22 19:50:54| aclParseAclLine: Invalid ACL type 'snmp_community'
FATAL: Bungled squid.conf line 83: acl snmppublic snmp_community public
Squid Cache (Version 2.6.STABLE5): Terminated abnormally.
CompleteHow make on install –enable-snmp ???
Sergu
-
STOP INSTALLING THE PACKAGE FROM THE SHELL/CLI/CONSOLE.
reinstall the package from the webgui. Click System -> Packages -> Installed Packages -> reinstall package Icon.
-
Hmmm, here with my system it won't install at all…
That's what it tells me:_Downloading package configuration file… done.
Saving updated package information... done.
Downloading squid and its dependencies... done.
Checking for successful package installation... failed!Installation aborted._
-
Hmmm, here with my system it won't install at all…
That's what it tells me:_Downloading package configuration file… done.
Saving updated package information... done.
Downloading squid and its dependencies... done.
Checking for successful package installation... failed!Installation aborted._
May be previous version of squeed don't deinstall correctly?
Check this can in -
Command Prompt: pkg_info- deinstall squid
- run pkg_info - squid package exists?
- if present need deinstall them: pkg_delete squid-2.5.-next number–
after need install squid package again.
-
No, it's not that, I already tried…
I also use the latest snapshot 21-12in which package does the ldap client come along ?
might be that one ? -
save the config, reinstall your box. Then reinstall squid.
It only takes 10 minutes and you can run from livecd with the config on a usb stick whil you are installing.
Just put you existing config on a stick in the conf/ subdirectory named config.xml.After rebooting the newly installed system will allready have the correct config.
-
nice to see that squid is back.The problem is that is not working like before.I wanna use a transparent proxy as my gateway but it cannot be used like that because of an error that says that cannot run in the same mode like webgui.Wich is the protocol for the webgui?I`ve tried a lot of ports but still nothing
-
Change the port the webConfigurator is running on.
-
When I disable the checkbox log location and leave the field for the log location empty, I cannot save because it wants me to enter a location, even if i won't use it, so perhaps you should disable the check for the dir when the checkbox is disabled…
-
One more bugfix in squid.inc, string 352.
Original:foreach (explode(trim($post['msnt_secondary'])) as $server) {must be changed on:
foreach (explode(',', trim($post['msnt_secondary'])) as $server) { -
Thanks, commited!