Squid Returned to Packages *** PLEASE TEST ***
-
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!
-
So enter a log location anyways. It's required.
-
Using p5.
On line 915 of squid.inc a reference is made to $port:
$rules .= "pass in quick on $iface proto tcp from any to !($iface) port $port flags S/SA keep state\n";I have a port defined, however, at this point in the script the $port variable has nothing assigned to it so I get a bad rule. My fix was just to comment that line out as I'm only using transparent proxy.
-
Using p5.
On line 915 of squid.inc a reference is made to $port:
$rules .= "pass in quick on $iface proto tcp from any to !($iface) port $port flags S/SA keep state\n";I have a port defined, however, at this point in the script the $port variable has nothing assigned to it so I get a bad rule. My fix was just to comment that line out as I'm only using transparent proxy.
You are not running the latest squid package. There are only 863 lines in squid.inc on the latest and the pass rules do not look anything like that…
-
looks like we're back to:
stopping /usr/local/etc/rc.d/proxy_monitor.sh…
again.
just installed squid and used transparent proxy.
-
looks like we're back to:
stopping /usr/local/etc/rc.d/proxy_monitor.sh…
again.
just installed squid and used transparent proxy.
Upgrade to latest snapshot.
-
It's really late here so I could be off the mark; but I also think there's something funky going on. I'm also getting the empty $port creating:
There were error(s) loading the rules: /tmp/rules.debug:250: syntax errorpfctl: Syntax error in config file: pf rules not loaded - The line in question reads [250]: pass in quick on sk0 proto tcp from any to !(sk0) port flags S/SA keep state…
I've just reinstalled and am using 2.6.5_1-p5. I'll take another look tomorrow evening if I have a chance.... I'm sure someone will figure it out before I do.
-
My bad, fixing into P6
-
Fixed.
-
I wasn't seeing any results from the white or black lists under the 12-23 build with the latest package and transparent proxy. Will try a clean install and see if that fixes it. Anyone else?
-
Just tried a clean install. Still not seeing any effect from the access control lists, namely the blacklist and whitelist. This was on the 12/23 build and Squid 2.6.5_1-p6. I'm also seeing strange lines (errors?) in the sys log. A sample follows.
Dec 30 16:55:04 php: : Resyncing configuration for all packages.
Dec 30 16:55:04 php: : Reloading Squid for configuration sync
Dec 30 16:55:04 php: : Resyncing configuration for all packages.
Dec 30 16:55:05 php: : Reloading Squid for configuration sync
Dec 30 16:55:05 php: : Could not open for writing
Dec 30 16:55:05 last message repeated 13 times
Dec 30 16:55:05 check_reload_status: reloading filter
Dec 30 16:55:05 php: : Could not open for writing
Dec 30 16:55:05 last message repeated 13 times
Dec 30 16:55:05 squid[668]: Squid Parent: child process 992 started
Dec 30 16:55:05 squid[668]: Squid Parent: child process 992 exited with status 1
Dec 30 16:55:06 check_reload_status: updating dyndns
Dec 30 16:55:08 squid[668]: Squid Parent: child process 1117 started
Dec 30 16:55:08 squid[668]: Squid Parent: child process 1117 exited with status 1
Dec 30 16:55:11 squid[668]: Squid Parent: child process 1137 started
Dec 30 16:55:11 squid[668]: Squid Parent: child process 1137 exited with status 1
Dec 30 16:55:11 squid[668]: Exiting due to repeated, frequent failuresSquid is in fact running and I can use it manually through my browser or via transparent. Just not sure why none of the lists are working and the strange log entries.
-
I still have not found time to test the access control lists. Not sure what's wrong because acls are a integral part of squid.
The log lines that is exiting with error code 1 is weird. Because I don't see that, or at least not as much. The good thing is that process does not get killed but fails to startup. I see this particularly on boot.
I am pondering the thought of recommending squidguard to implement filtering although I have zerro experience with that. And i'm not sure if we have a package for that yet.
-
The lastest package causes squid to start twice, that's why where getting all the squid xxx exited due blah blah blah in the squid logs. It seems that when the package is synced with squid.inc on startup, it starts squid, then all the .sh files in rc.d are executed and it starts squid again. With the update to the package I think the *.sh stop was removed to fix the problem with proxy_monitor hanging, and it was effective, I think with some edits to the squid.inc file we could be good to go again. I'll take a look at it myself, but just wanted to let you know about it. It also seems one is started with the user root and the other the user proxy. I'll report back when I know more
-
Could the dual instances of Squid be killing the ACLs? Are the ACLs up and running on one instance but all traffic is being routed through the other?
-
I just performed a upgrade to the latest code and after a reboot there are no errors and start properly. At least with the current -p6 version.