Squid3 can't find libmd5.so.0

marcelloc

Hi guys.

The /var/run/squid issue pointed by cino will be fixed on next package update

The Cannot bind socket FD 30 to 192.168.1.1:443: (13) Permission denied on reverse proxy maybe related to this
https://www.freebsd.org/doc/handbook/mac-policies.html

~~For now, listen squid on high ports and nat it too 80,443 until I find a way to workaround it.~~

To fix it without mac-policies, edit net.inet.ip.portrange.first system tunable(system advanced menu) option from 1024 to 0.

After config option change, stop and start squid.

Cino

Thanks Marcelloc!!!

Do you think the below error could also be related to the permissions of the user?


2015/01/12 01:09:47 kid1| Starting Squid Cache version 3.4.10 for amd64-portbld-freebsd10.0...
2015/01/12 01:09:48| pinger: Initialising ICMP pinger ...
2015/01/12 01:09:48|  icmp_sock: (1) Operation not permitted
2015/01/12 01:09:48| pinger: Unable to start ICMP pinger.
2015/01/12 01:09:48|  icmp_sock: (1) Operation not permitted
2015/01/12 01:09:48| pinger: Unable to start ICMPv6 pinger.
2015/01/12 01:09:48| FATAL: pinger: Unable to open any ICMP sockets.

marcelloc

@Cino:

Do you think the below error could also be related to the permissions of the user?

I'll try to test it too.

BTW, you can disable icmp pinger on squid config options.

Escorpiom

Marcelloc, do you have any tips how we can troubleshoot the transparent proxy issue?

Cheers.

marcelloc

@Escorpiom:

Marcelloc, do you have any tips how we can troubleshoot the transparent proxy issue?

Transparent proxy is working on my tests…

trouserless

@marcelloc:

@Escorpiom:

Marcelloc, do you have any tips how we can troubleshoot the transparent proxy issue?

Transparent proxy is working on my tests…

This is strange - I've updated to the latest 2.2RC as of 1/13/15 and I still have to create the /var/run/squid directory, change perms and chmod it in order to get squid3 to work. I've also noticed that once this starts running for a little while my load average climbs very high. I have an 8-core atom (c2758) and it scales to over 13x load average. When running top it shows either the squid or proxy user running 12 instances of .pbirun with WCPU evenly divided between the process (~8-9% each totally just shy of 100%). The proxy is working - the only other CPU intensive process is snort (and that is barley using any CPU according to top).

Anyone else see this?

Cino

@trouserless:

This is strange - I've updated to the latest 2.2RC as of 1/13/15 and I still have to create the /var/run/squid directory, change perms and chmod it in order to get squid3 to work.

The new PBIs for squid haven't been build yet.

from https://files.pfsense.org/packages/10/All/


squid-3.4.10_2-amd64.pbi                           09-Jan-2015 20:25            19231214
squid-3.4.10_2-amd64.pbi.sha256                    09-Jan-2015 20:25                  65
squid-3.4.10_2-i386.pbi                            09-Jan-2015 20:45            18317590
squid-3.4.10_2-i386.pbi.sha256                     09-Jan-2015 20:45                  65

marcelloc

wait pkg version bump (maybe 0.2.3)…

marcelloc

0.2.3 package version is out! :)

https://github.com/pfsense/pfsense-packages/pull/786

Cino

@marcelloc:

0.2.3 package version is out! :)

https://github.com/pfsense/pfsense-packages/pull/786

Awesome!! You da the man!

I'm installing on a fresh amd64 install and will let you know if I run into any problems.