Squid, SquidGuard, Lightsquid status on 2.3

brianc69

Also pleased to report that enabling antivirus is working too! I attempted to download the eicar.txt file and it was blocked with a virus warning as it should be!

Only thing left I notice is on the realtime log page.

Message
WARNING: Clamd was NOT notified: Can't connect to clamd through /var/run/clamav/clamd.sock: No such file or directory
Database updated (6435493 signatures) from db.us.clamav.net (IP: 194.8.197.22)

Everything else looks good to my knowledge.

brianc69

Work around did not survive a reboot. Reapplied and things work again. Just an FYI.

jimp

That's expected, it's just a temp workaround.

jimp

New revision of the squid package is up now for testing. If you did the chgrp work around you need to change it back to 'proxy' or reboot before upgrading the package.

brianc69

Rebooted, updated squid package. Seems to be ok. Content filtering and virus scanning are working.

rubinho

Thx for fixing this issue

Transparentproxy works fine now.

UltramaticOrange

I'm noticing that between the 12-24hr mark, DNS issues return. Timing has seemed relatively inconsistent and I haven't really narrowed down any possible causes just yet.

Here's what I've observed so far:
I restarted unbound, and the issue persisted.
I disabled squid and the issue went away.
I re-enabled squid and everything stayed good.

Next time, I'll check the squid logs and restart the service and report back.

jimp

Update on Lightsquid: The package now runs in its own web server instance using lighttpd, on its own port and with password protection. It was the smoothest way to get perl cgi support without dragging extra dependencies into base.

Note there are some subtle changes to navigation in the package.

brianc69

There is a port issue when you click Lightsquid. I see myip:9000:7445

jimp

@brianc69:

There is a port issue when you click Lightsquid. I see myip:9000:7445

I'll look into that.

maverick_slo

Also nothing happens if I hit refresh buttons.
It seems like it is working but I have no data in the logs.

When I: /usr/local/www/lightsquid/lightparser.pl from console, data appears.
In logs I have: /pkg_edit.php: [lightsquid] Parsing today's entries in access.log using '/usr/bin/perl /usr/local/www/lightsquid/lightparser.pl today'

There has to be something wrong here…

maverick_slo

Oh and one more thing..

If I manually do: /usr/bin/perl /usr/local/www/lightsquid/lightparser.pl today
This is in the crontab.

Output is /usr/bin/perl: Command not found.

jimp

I fixed the perl path (should be /usr/local/bin/perl) and fixed the parsing of the link with the port.

jimp

I split the unrelated hit % posts off into their own thread and cleaned up the references here.

maverick_slo

One more thing:

a) After reboot Lightsquid Web Server wont come up b) Starting it from status_services.php wont start it
c) Saving settings in pkg_edit.php?xml=lightsquid.xml will start it.

:)

jimp

@maverick_slo:

a) After reboot Lightsquid Web Server wont come up b) Starting it from status_services.php wont start it
c) Saving settings in pkg_edit.php?xml=lightsquid.xml will start it.

I can't reproduce this, it starts every time for me. Any errors in the system log, or in /var/log/lighttpd_lightsquid.log ?

whitexp

lightsquid :

disable ssl , now click "open lightsquid" .. url go to "https" ….

jimp

@whitexp:

lightsquid :

disable ssl , now click "open lightsquid" .. url go to "https" ….

I pushed a fix for that just now.

maverick_slo

@jimp:

@maverick_slo:

a) After reboot Lightsquid Web Server wont come up b) Starting it from status_services.php wont start it
c) Saving settings in pkg_edit.php?xml=lightsquid.xml will start it.

I can't reproduce this, it starts every time for me. Any errors in the system log, or in /var/log/lighttpd_lightsquid.log ?

That`s odd.
I cleared browsers cache and now it starts correctly.

UltramaticOrange

@UltramaticOrange:

I'm noticing that between the 12-24hr mark, DNS issues return. Timing has seemed relatively inconsistent and I haven't really narrowed down any possible causes just yet.

Here's what I've observed so far:
I restarted unbound, and the issue persisted.
I disabled squid and the issue went away.
I re-enabled squid and everything stayed good.

Next time, I'll check the squid logs and restart the service and report back.

Turns out that my issues are symptomatic of packet loss with my ISP and nothing to do with pfsense.