Squid3 on amd64 snapshot?
-
ahja, there you need a changed squid.inc. I have made that changes manually. Try that version, it should work!
Here it is:
-
I just committed that file, give it a go. Should sync into the repo in a few minutes.
https://github.com/bsdperimeter/pfsense-packages/commit/2866d3ae45fdea9e6066f523a1fb8ebdceba5e90
Looks like you also made some whitespace changes (removed trailing tabs/spaces). It's a good change but usually those are done in separate commits so the functional changes are easier to see.
Jim
-
What remains is the error i encountered described here: http://forum.pfsense.org/index.php/topic,33616.msg174311.html#msg174311
and at the same time
reply_body_max_size SIZE [acl acl…]
(without units)So i tested with "reply_body_max_size 0 deny all" and with "reply_body_max_size 0 KB deny all". Tested with other values greater 0, but all time same result.
If anybody has an explanation to this strange behaviour, please feel free to tell me. -
I get the below error in both Squid 2 and 3. Service starts though. Can this be ignored? If not what do I need to do to rectify it? I have 3 VLANs.
php: /pkg_mgr_install.php: The command '/usr/local/sbin/squid -k kill' returned exit code '1', the output was '2011/05/26 14:30:16| WARNING: '10.0.2.0/255.255.255.0' is a subnetwork of '10.0.0.0/255.0.0.0' 2011/05/26 14:30:16| WARNING: because of this '10.0.2.0/255.255.255.0' is ignored to keep splay tree searching predictable 2011/05/26 14:30:16| WARNING: You should probably remove '10.0.2.0/255.255.255.0' from the ACL named 'localnet' 2011/05/26 14:30:16| WARNING: '10.0.3.0/255.255.255.0' is a subnetwork of '10.0.0.0/255.0.0.0' 2011/05/26 14:30:16| WARNING: because of this '10.0.3.0/255.255.255.0' is ignored to keep splay tree searching predictable 2011/05/26 14:30:16| WARNING: You should probably remove '10.0.3.0/255.255.255.0' from the ACL named 'localnet' squid: ERROR: Could not send signal 9 to process 1861: (3) No such process'
-
That looks like you have overlapping subnets on different interfaces, or you have a manual ACL that is much wider than the specific per-interface ACL you get when you check "allow users on interface". So either fix your subnet masks, remove the manual ACL, or uncheck "allow users on interface" and keep your manual ACL.
-
That is correct.. I have 3 VLAN interfaces with same subnet of 255.0.0.0.. the IP address allocations are different though.. 10.0.1.x, 2.x and 3.x
Is Squid working after the error? I would like to keep the overlapping subnet.
-
That is not a proper network configuration. They should either be all bridged inside of 10.0.0.0/8 or each be 10.0.x.0/24.
-
understood.
I changed each to be 10.0.x.x/24 for each VLAN. Should I just reboot for the changes to take effect or a simple squid service restart will be fine?
-
Pressing "Save" on the squid settings should suffice.
-
very cool.
So my Squid is all set.. right :D
-
Are these errors something to worry about?
May 26 15:01:52 php: : Not calling package sync code for dependency squidcache of squid because some include files are missing.
May 26 15:01:52 php: : Not calling package sync code for dependency squidusers of squid because some include files are missing.
May 26 15:01:52 php: : Not calling package sync code for dependency squidauth of squid because some include files are missing.
May 26 15:01:52 php: : Not calling package sync code for dependency squidupstream of squid because some include files are missing.
May 26 15:01:52 php: : Not calling package sync code for dependency squidtraffic of squid because some include files are missing.
May 26 15:01:52 php: : Not calling package sync code for dependency squid of squid because some include files are missing.
May 26 15:01:52 php: : Not calling package sync code for dependency squidnac of squid because some include files are missing.
May 26 15:01:52 php: : Not calling package sync code for dependency squidcache of squid because some include files are missing. -
You might need to uninstall squid, rm /usr/local/pkg/squid*, and then reinstall squid.
That may be a side effect of switching back and forth between squid2/squid3, not sure.
-
Did a clean install of pfsense again. a pain !!
Still getting the same errors.
On every first fresh install squid2 wont start after reboot. I have to go into var/squid/ and delete cache and logs folders, do a package reinstall to get the cache built again and then it works.
Are those errors serious? As I can see the service is started along with Squidguard.
I am using aufs file system.
