PfSense 2.2 and Squid

Rickinfl

Ok. Come on Guys if Squid is not ready for pfSense 2.2 remove it from being able to install on 2.2.

Upgraded from 2.1 to 2.2 > Squid Failed will not start
Did fresh install of 2.2 > Squid Failed and will not start
Did fresh install of 2.2 > Using Squid3 > Failed will not start and Clamav will not start

Did a fresh install of 2.1 > Squid installed everything works perfect. smh

I think there is an issue! lol

fragged

It took me 10 minutes to get Squid to run on my test VM with pfSense 2.2. What I had to do was go save all the tabs, slightly edit both squidclamav.conf and c-icap.conf as told by the GUI when you save the page again and then restart the services. I now have Squid running as a transparent proxy with ClamAV.

Based on another thread, you might need to invoke command: freshclam on ssh/console to get ClamAV to download virus definitions.

Rickinfl

Ok Tried that, but this just keeps getting worst and worst. I actually had it running once! Until I rebooted then everything stopped working.

now I get this error:

Shared object "libldap-2.4.so.2" not found, required by "squidGuard"

marcelloc

What 2.2 version? amd64, i386,nano?

djzort

there was a decision to move the paths around inside the squid module which seems to have been done hastily. see also https://forum.pfsense.org/index.php?topic=87969.0

ditrone

what i currently get from lightsquid with 2.2 & squid3
was working before upgrade
https://myrouter/lightsquid/index.cgi

Software error:
Can't locate /usr/local/etc/lightsquid/lightsquid.cfg in @INC (@INC contains: /usr/local/lib/perl5/site_perl/mach/5.18 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.18/mach /usr/local/lib/perl5/5.18 /usr/local/lib/perl5/site_perl/5.18 /usr/local/lib/perl5/site_perl/5.18/mach . /usr/local/www/lightsquid/) at /usr/local/www/lightsquid/index.cgi line 17.

KOM

To fix Lightsquid, run these from the shell:

ln -s /usr/pbi/lightsquid-amd64/local/www/lightsquid /usr/local/www/lightsquid
ln -s /usr/pbi/lightsquid-amd64/local/etc/lightsquid /usr/local/etc/lightsquid
pkg install perl5
pkg install p5-gd
/usr/bin/perl /usr/pbi/lightsquid-amd64/www/lightsquid/lightparser.pl today

This assumes x64. For i386, replace 'lightsquid-amd64' with 'lightsquid-i386' (I think).

ditrone

@KOM:

To fix Lightsquid, run these from the shell:
ln -s /usr/pbi/lightsquid-amd64/local/www/lightsquid /usr/local/www/lightsquid
ln -s /usr/pbi/lightsquid-amd64/local/etc/lightsquid /usr/local/etc/lightsquid
pkg install perl5
pkg install p5-gd
/usr/bin/perl /usr/pbi/lightsquid-amd64/www/lightsquid/lightparser.pl today
This assumes x64. For i386, replace 'lightsquid-amd64' with 'lightsquid-i386' (I think).

ssdh'd into box and ran commands. looks like links existed. pkg install went fine, no errors

2.2-RELEASE][root@pfsense.localdomain]/root: ln -s /usr/pbi/lightsquid-amd64/local/www/lightsquid /usr/local/www/lightsquid
ln: /usr/local/www/lightsquid/lightsquid: File exists
[2.2-RELEASE][root@pfsense.localdomain]/root: ln -s /usr/pbi/lightsquid-amd64/local/etc/lightsquid /usr/local/etc/lightsquid
ln: /usr/local/etc/lightsquid/lightsquid: File exists

then when i run the update i get

[2.2-RELEASE][root@pfsense.localdomain]/root: /usr/bin/perl /usr/pbi/lightsquid-amd64/www/lightsquid/lightparser.pl today
Can't locate /usr/local/etc/lightsquid/lightsquid.cfg in @INC (@INC contains: /usr/local/lib/perl5/site_perl/mach/5.18 /usr/local/lib/perl5/site_perl /usr/local/lib/perl5/5.18/mach /usr/local/lib/perl5/5.18 /usr/local/lib/perl5/site_perl/5.18 /usr/local/lib/perl5/site_perl/5.18/mach . /usr/pbi/lightsquid-amd64/www/lightsquid/) at /usr/pbi/lightsquid-amd64/www/lightsquid/lightparser.pl line 35.

Rickinfl

@marcelloc:

What 2.2 version? amd64, i386,nano?

I'm running pfSense 2.2 amd64. Not the nano version.

Rickinfl

This is NOT a pfSense issue. pfSense runs perfect. Someone needs to get a hold of the Squid development team and have them fix this. Or are they on here? Has anyone notified them?

KOM

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.

doktornotor

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.

Cino

@doktornotor:

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.

djzort

here is the code change, i even commented on it.

https://github.com/pfsense/pfsense-packages/commit/6a6669a0919681284c05185246fc39de8dc06811

Cino

its the lightsquid package that needs to be fix, not the squid package.

Rickinfl

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.

Cino

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.0

after that, make sure you download a blacklist and apply it.

Rickinfl

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?

Cino

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.

KOM

SquidGuard used to work fine for me. Now it's broken and won't work without symlink hacks?