Filter porn, virus's and ads with squid3, HAVP, Dansguardian and privoxy.

[krk]

When adding the privoxy package, here is a warning I get…  is there a privoxy version that uses pcre-8.32?

Fetching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/privoxy.tbz... Done.
pkg_add: warning: package 'privoxy-3.0.16_1' requires 'pcre-8.02', but 'pcre-8.32' is installed

[Ulich05]

I follwed the steps on the first post and got everything working w/o a hitch.

I also tried just the Dansguardian -> squid method which worked but for some reason it was much slower and didnt block any ads vs the dansquardian -> squid-> HAVP-> privoxy method (which makes no sense conceptually) and i could never get dansguardian's built in clamd to work properly (which also makes no sense)

besure to see this on the webupload bug fix as well http://forum.pfsense.org/index.php/topic,58442.15.html (which works as this post was sucessful)

[Ulich05]

@krk:

I get the following error when trying to start privoxy:
Starting privoxy.
/libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, required by "privoxy"

Has anyone else had this?  What did you do to resolve the issue?

thanks

I had this issue w/ a brand new install on another box just now. do a "find / -name libpcre.so.0" and ls -l the files, you should see that they're linked to libpcre.so.3, create a sym link to libpcre.so.0 instead and it should solve the privoxy issue. I have no idea if the new symlink location will screw anything else up. so far it hasn't.

Another tidbit is that you have to install dansguardian first before you install squid3 (if you want to use squid3). Dasguardian will install squid 2.7.x as a dependency which will cause pfsense to revert to using the older version if you have squid3 installed beforehand.

[ion9]

I was getting /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, required by "privoxy" to and i think there is a fast way to fix it

if your on a x64 box install the x64 software

pkg_add -r http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.1-release/Latest/privoxy.tbz

after i did that it work for me.

[mosfet]

@ion9:

I was getting /libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, required by "privoxy" to and i think there is a fast way to fix it

if your on a x64 box install the x64 software

pkg_add -r http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.1-release/Latest/privoxy.tbz

after i did that it work for me.

I tried this, both using …/amd64/packages-8.1-release/Latest/privoxy.tbz , .../amd64/packages-8.2-release/Latest/privoxy.tbz and .../amd64/packages-9.0-release/Latest/privoxy.tbz . I still get "libpcre.so.0 not found".

2.1-RC0 (amd64)
built on Sat Jun 8 09:20:03 EDT 2013
FreeBSD 8.3-RELEASE-p8

I've tried the same on 2.0.3 (amd64) without success.

Anyone successfully installed privoxy on pfSense? What version of pfSense and privoxy are you using?

[marcelloc]

@mosfet:

Anyone successfully installed privoxy on pfSense? What version of pfSense and privoxy are you using?

Did you tried installing pcre package too? what version of pcre do you have on your system?

[mosfet]

@marcelloc:

@mosfet:

Anyone successfully installed privoxy on pfSense? What version of pfSense and privoxy are you using?

Did you tried installing pcre package too? what version of pcre do you have on your system?

Well, I've not tried to install pcre as a package, but it is installed. The last attempt I tried, are using pcre-8.32 and privoxy-3.0.17.

This leads to: "/libexec/ld-elf.se.1: Shared object "libpcre.so.0" not found, required by "privoxy"".

[marcelloc]

@mosfet:

This leads to: "/libexec/ld-elf.se.1: Shared object "libpcre.so.0" not found, required by "privoxy"".

what version of libpcre you get on your system?

find / -name "libpcre.so*"

[mosfet]

@marcelloc:

@mosfet:

This leads to: "/libexec/ld-elf.se.1: Shared object "libpcre.so.0" not found, required by "privoxy"".

what version of libpcre you get on your system?

find / -name "libpcre.so*"

Output:
/usr/local/lib/libpcre.so.3
/usr/local/lib/libpcre.so

[marcelloc]

@mosfet:

Output:
/usr/local/lib/libpcre.so.3
/usr/local/lib/libpcre.so

Try to force it with a link

ln -s /usr/local/lib/libpcre.so.3 /usr/local/lib/libpcre.so.0

this is not the best way to workaround it but works.

[mosfet]

@marcelloc:

@mosfet:

Output:
/usr/local/lib/libpcre.so.3
/usr/local/lib/libpcre.so

Try to force it with a link

ln -s /usr/local/lib/libpcre.so.3 /usr/local/lib/libpcre.so.0

this is not the best way to workaround it but works.

Wow - that worked. Thanks a million!

[Chewy]

To answer Marcel's question from back in January (I know, I don't read the boards enough  ;))

You can filter ads very effectively with DG using a Regexp filter. This gets most of them including popups, sidebars and even YouTube video embedded ads. Just add it under
Dansguardian - Access Lists -> URL

(^ads.|/ads/|/ads.|.ads.|adcycle|adserv|/ad.|.ad.|/ad/|.adview|/adview|pagead|adpopup|phpAds|.adscript|/adscript|/adframe|.adframe)
(werbung|anzeige|banner|sponsors|advertising|adimg)
(doubleclick)

[SIPpyCup]

followed the guide until my/its first error

Select the /usr/local/etc/privoxy/config

This file does not exist.  After I tried starting privoxy it was created. I could then edit it.

I then encountered the libpcre error as above but could not create a link.

putty ssh as admin

same find output

/usr/local/lib/libpcre.so.3
/usr/local/lib/libpcre.so

and 20ish error lines follow (I don't know how to copy in putty ssh / ubuntu)
find: /var/spool/epilocks: Permission denied
find: /var/log/squid
find: /var  (12 more )
find: /tmp/lighttpdcompress (4 of these)

@marcelloc:

Try to force it with a link

ln -s /usr/local/lib/libpcre.so.3 /usr/local/lib/libpcre.so.0

this is not the best way to workaround it but works.

ln: /usr/local/lib/libpcre.so.0: Permission denied

installed from CD a few days ago

" 2.0.3-RELEASE (i386)
built on Fri Apr 12 10:22:21 EDT 2013
FreeBSD 8.1-RELEASE-p13"

on an older Dell Optiplex "Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz " with one pci-e two port intel 1000 nic and an older but never before used SSD

[EnglishRob]

Hi folks,

I'm a newbie here who's been having a play with pfSense with two ADSL connections.  I've managed to get multi-wan working (running a traceroute to different servers goes over each WAN connection) and I've also got this guide working, but anything going over the proxy only seems to go over the one connection (I've tried whatismyipaddress.com and it always returns the same IP address).

I just wondered if anyone could give any pointers on how I might be able to configure privoxy to go over the gateway group I've configured?  (I wasn't sure if it was possible to setup a firewall rule so anything over a certain port number goes to the gateway group?).

Ta,

Rob

[Treo]

I'm new to all of this, but am very intrigued by the vast capabilities of these varied pfSense configurations.  I'm starting to get the hardware components needed to put a home firewall together and want to make sure I understand the recommended installation steps from this thread (after all 3 pages of notes, adjustments, talks & ideas)….so let's see how much I'm missing.

My home network: 5Meg CableModem supporting 4 desktop PCs and 2 XBOX's (each with their own XBOX Live account)
Old 2GHz HP desktop PC will become the pfSense firewall box once I add a 2nd ethernet NIC.  Optional idea is installing a wireless card (which I'll hopefully be able to configure into a WAP for the home)

Goal of pfSense box:

• reliable firewall that filters out porn, virus/trojan/worm, and annoying ads & banners
• logging of visited websites grouped by home user's PC (either IP, MAC, and/or hostname)
• allow XBOX Live gaming for both consoles

pfSense steps (as I understand them so far from reading dozens of forum threads):

-Install stabe version of pfSense (v2.0.3) & reboot
-verify pfSense is up and running.....allowing internet traffic from one of the PCs) & no filters or rules in place (yet)
-from a regular PC on the home network, access pfSense via web interface
-set to HTTPS access for pfSense web interface instead of HTTP
-change pfSense admin password
-install Dansguardian from the packages screen of GUI (unsure what the current stable version is)

At this point, the next few steps might not be in the right order, so I need guidance:

-install stable squid package (v2.7.9 ?) from the packages screen of pfSense GUI (as opposed to the squid3 beta)
-verify Dansguardian is up properly....running "Dansguardian -Q" from the command line if needed

Does stable Dansguardian package and squid v2.7.9 startup & run the right way on pfSense v2.0.3...or is there some special tweaking needed?  What order to install DG & squid?  Or should I just try the pfSense v2.1 beta and squid3 beta instead?

-configure Dansguardian (somehow) for antivirus
-configure NAT as required to get the 2 XBOX's working properly (refer to thread under Gaming forum for specifics...ie multicast rules)

Have I got this first part right?  Or did I forget a few steps?

Thanks for all the work on this whole project.....the capabilities of this inspire me to consider diving head-first & learning all I can.

[eisenb11]

I'm having a tough time getting this to work. My goal was to set this up using just squid and privoxy.

To simplify the matters, I'm currently just trying to get squid to work on the loopback with pfsense 2.1 and I'm having no luck at all.

For this test I have the following config:

Squid:
All defaults except…
Changed proxy interface to loopback
Proxy port to 3128
I've also tried checking and unchecking the Allow users on interface and Transparent proxy options

Under NAT, I created a rule to forward all LAN HTTP destined for port 80 to 127.0.0.1 port 3128

In theory, this should forward all LAN HTTP traffic to Squid... but it's not working.

Whenever I enable the NAT rule, web browsing breaks and I get an "Invalid URL" error in my web browser from squid.

Can anyone help me out?

[marcelloc]

Enable proxy on lan and check transparent proxy. It will create forward rules. There is no need to create nat rules.