Squid 3.3.4 package for pfsense with ssl filtering
-
Check if squid is listening(netstat -an | grep -i listen) on the port you have configured on dansguardian.
-
Check if squid is listening(netstat -an | grep -i listen) on the port you have configured on dansguardian.
It is closed.
-
-
It is closed.
Next step is to check why squid is not starting…
The service is running, just doesn't listen to the port.
-
The service is running, just doesn't listen to the port.
Enable ipv6 on pfsense and then killall and start squid daemon.
It's something on squid 3.3 version, I have a squid 3.3 version on my repo without ipv6 that works fine.
If you do not want to enable ipv6 on your server, install squid 3.3.4 form my repo using pkg_delete and pkg_add from console/ssh
-
The service is running, just doesn't listen to the port.
Enable ipv6 on pfsense and then killall and start squid daemon.
It's something on squid 3.3 version, I have a squid 3.3 version on my repo without ipv6 that works fine.
If you do not want to enable ipv6 on your server, install squid 3.3.4 form my repo using pkg_delete and pkg_add from console/ssh
Thank you very much! Enabling ipv6 works.
;D
-
MULTIWAN
Hello, you work the proxy-dev ver. 3.3.8 with the multi-WAN? Before working with version 2.7.9 using this guide http://forum.pfsense.org/index.php?topic=60977.0, now I installed version 3.3.8-dev and it does not work. With the release of squid that is found in this post (3.3.4) will it work?
thanks
greetings -
Did you upgraded pfsense too?
What version are you using?
-
-
If you are getting missing libs erros like Shared object "libgssapi.so.10" not found, required by "squid"',
Copy it from my personal repo or from any freebsd with the same version.
These are libs that are not included on pfsense base install bu required to sasl.
save it to /usr/local/lib
amd64
http://e-sac.siteseguro.ws/pfsense/8/amd64/All/ldd/i386
http://e-sac.siteseguro.ws/pfsense/8/All/ldd/
- Shared object "libheimntlm.so.10" not found,
-
-
sorry I don't understand
On console/ssh use pkg_delete to remove squid-3.3.4 and pkg_add to get squid 3.3.5
i386 systems
pkg_add -r http://e-sac.siteseguro.ws/packages/8/All/squid-3.3.5.tbzamd64 systems
pkg_add -r http://e-sac.siteseguro.ws/packages/amd64/8/All/squid-3.3.5.tbzCan you provide a URL that is available from the USA? This URL returns "Unable to get the … and Operation timed out."
The URL when Pinged gives me an IP address, but I cannot replace the "e-sac.siteseguro.ws" with an IP address and have it work.
David
-
Can you provide a URL that is available from the USA?
Unfortunately No. :(
Do you have pfblocker enabled with brazil on your block list?
To get squid working without changing package files, just enable ipv6 on your 2.0.x version and get missing files from any freebsd 8.1 server.
The URL when Pinged gives me an IP address, but I cannot replace the "e-sac.siteseguro.ws" with an IP address and have it work.
It's a hosting server, only dns http headers will reach my files.
-
Tested:
i386 systems
pkg_add -r http://e-sac.siteseguro.ws/packages/8/All/squid-3.3.5.tbzamd64 systems
pkg_add -r http://e-sac.siteseguro.ws/packages/amd64/8/All/squid-3.3.5.tbzand they are dead for us as well.
-
Check your firewall rules and blocked ips.
I've just tested and it's working.
Use default package binaries with ipv6 enabled.
fetch missing files from any freebsd 8.1 for pfsense 2.0.x
-
Interestingly it's timing out for me too Marcello. And it's worked for me before, many times. I'm at work, in Oz, corporate firewall but it's not blocking.
-
Sorry for my bad english.
Can someone explain, how to block https urls with squid3 + squidguard?
Http urls are blocked correctly, but https urls won't be blocked :(
Thank you so much.
-
-
Create a Certificate authority on pfsense
-
Export ca certificate on gui and import on each client you what to filter ssl without certificate error messages
-
Enable ssl interception/transparent proxy on squid3-dev gui.
-
-
Marcelloc I am telling you it is DEAD. We have tried going outside pFsense, direct to our ISP, and also on our VPN.
It is unreachable.
The PBI manager within pFsense works fine.
Why not update the Squid 3.3.8.package so we can access it from within pFsense rather than from a third-party website?
Interestingly it's timing out for me too Marcello. And it's worked for me before, many times. I'm at work, in Oz, corporate firewall but it's not blocking.
-
Why not update the Squid 3.3.8.package so we can access it from within pFsense rather than from a third-party website?
As I told you on other post.
-
Install squid3-dev
-
Enable ipv6 on system advanced
-
fetch missing libs from any freebsd 8.3
I've asked core team to include these libs on official repo, this way, postfix, freeradius2, squid3 and other package I do not remember now can be installed automatically via gui. But I had no success on it.
The libs are there to help people not to mess things up.
Last point. It's a dev package, not a release or stable one. So people who tries it must know how to workaround things.
-
-
Hi,
I am planning tu use squid3 for transparent proxy for http and ssl intercepting proxy (443) on a Multi-WAN environment.
So my question ist not directly related to the package but how do you use loadbalancing for ports 80/443 if these connections alsways have the same source like 127.0.0.1 ?To make it a little bit clearer
I am not asking how to configure a pfsense with Multi-WAN and squid to use all WAN connections and not only one.
I am interested in how to make it work that port 80 and port 443 can be loadbalanced even if the source is always squid/pfsense itself (127.0.0.1) and so I can not balance based on the source-IP. Policy based routing for these two ports will not make sense and sticky connections - I think they will always use one WAN for these two ports.I explained a little bit more here:
http://forum.pfsense.org/index.php/topic,68120.0.htmlI would really appreciate any help so that I can configure my test machine and do some tests ;-)
-
Maybe with a lot of acls based on source ip acls to define tcp_outgoing address.
I'm seeing some posts related to problems with 127.0.0.1 load balance on 2.1
