PfSense 2.2 and Squid
-
Weird. I've installed 2.2 fresh about a dozen times and the steps I listed for Lightsquid worked every time without exception. You say you tried on a fresh install and the symlinks were already there??
Someone needs to get a hold of the Squid development team and have them fix this.
Some of the pfSense packages are/were maintained by volunteers. Lightsquid and Sarg are still two packages that have install issues and need to be tweaked to work. The vnstat2 packages was just fixed for 2.2 today, for example.
-
People should stop producing shitty symlink "fixes" on their boxes. Very much convinced at least half the of package "bugs" are a result of tons of similar hacks done by users that have since totally lost track of what they've actually done on their machines.
-
People should stop producing shitty symlink "fixes" on their boxes. Very much convinced at least half the of package "bugs" are a result of tons of similar hacks done by users that have since totally lost track of what they've actually done on their machines.
They should keep track of those kind of changes.
bug report for lightsquid was submitted awhile ago https://redmine.pfsense.org/issues/4198 to fix the pbi's.
-
here is the code change, i even commented on it.
https://github.com/pfsense/pfsense-packages/commit/6a6669a0919681284c05185246fc39de8dc06811
-
its the lightsquid package that needs to be fix, not the squid package.
-
Yes it seems Squid is working fine. I tired both Squid and Squid3 both worked on Squid3 had to do some config tweaks, but it worked..
It's SquidGuard that is not working. I've tried everything to get this to work.
-
with squid3 install, install squidguard-dev and run this
ln -s /usr/pbi/squidguard-devel-amd64/local/lib/libldap-2.4.so.8 /usr/local/lib/libldap-2.4.so.8 ln -s /usr/pbi/squidguard-devel-amd64/local/lib/libldap-2.4.so.8 /lib/libldap-2.4.so.8 ln -s /usr/pbi/squidguard-devel-amd64/local/lib/libdb-4.6.so.0 /usr/local/lib/libdb-4.6.so.0 ln -s /usr/pbi/squidguard-devel-amd64/local/lib/libdb-4.6.so.0 /usr/lib/libdb-4.6.so.0after that, make sure you download a blacklist and apply it.
-
I've seen that before, but my question is…. If they ever do get around fixing SquidGuard will there be issues because of those LN's?
-
There is always a risk… I've been keeping notes of what I've done to my box; so when SG if fix, I can remove the links I created.
-
SquidGuard used to work fine for me. Now it's broken and won't work without symlink hacks?
-
@KOM:
SquidGuard used to work fine for me. Now it's broken and won't work without symlink hacks?
JimP just committed some changes to SquidGuard for pfSense 2.2 : https://github.com/pfsense/pfsense-packages/commit/1b27c346293d8a53a80dd7563d787e9e073f801a
It would be worth reinstalling and trying…
-
Pbi for i386 has updates too.
-
I removed the symlinks I had for squidguard-dev and was was able to install squidGuard for the most part with no issues… Had to reboot and also reinstall dansguardian since that wouldnt auto start on reboot...
-
I removed the symlinks I had for squidguard-dev and was was able to install squidGuard for the most part with no issues… Had to reboot and also reinstall dansguardian since that wouldnt auto start on reboot...
Cino I had all sorts of trouble in 2.2 to get Squid3 (transparent proxy) and DansGuardian going
Would you mind sharing how did you make them work together? I have all the rules OK (pf2.1.5 works fine with squid + dansguardian) but I could never get squid3 working with Dans in 2.2.Appreciated.
-
I should had mention that before but I don't use transparent squid proxy. I do have a transparent setup for Dansguardian, which is on a different subnet.
This is the order I did my install a month ago… squid, squidguard... got them running... then added dansguardian into the mix
I have squid listening on my lan and loopback... dansguardian is listening on my lan and upstreams to squid via 127.0.0.1
here is the nat I use for dansguardian
KIDSNET TCP * * * 80 (HTTP) 127.0.0.1 8080 Dansguardian Transparent Proxy Re-Direct
