Squid, SquidGuard, Lightsquid status on 2.3
-
Lightsquid is broken in many ways (see the earlier posts in the thread) – no hope of it working util we fix up nginx for CGI.
We've made no attempt to test or work on clamav or c-icap, just the base functions of the forward proxy currently.
What does this mean? It's fixed in 2.3 final right?
The package version has no relation to 2.3 "final", it could be changed before or after release. Hopefully, before. It just means it isn't working or isn't tested now. The functions I stated we didn't work on may work fine, we just haven't tested them because they're not functions of squid we intend to "officially" support at this time.
Others are free to test and submit fixes as needed if they want, though.
-
Reading threads from older versions of pfSense, it sounds like this is a known issue, but I wanted to report that I am also having issues with the transparent proxy and getting "ERR_EMPTY_RESPONSE" on Chrome. However, my observation has been that everything works fine when the DNS response is still hanging around from the last time I visited the page (read: squid was off). To me, this might suggest that Squid is either having a hard time talking to the dns server (isn't pointed a the local machine/general DNS settings), squid isn't giving dns enough time to respond (timeout setting too short), or there's some conflicting setting between squid and dns.
-
There's a workaround for the transparent proxy issue in https://redmine.pfsense.org/issues/5869
chgrp squid /dev/pfProper fix to come.
-
Work around confirmed working on my end! Squidguard also functioning now that squid is responding. Thank you!!!
Now I await the return of Lightsquid for reporting but for now the important part of content filtering has returned!
-
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.
-
Work around did not survive a reboot. Reapplied and things work again. Just an FYI.
-
That's expected, it's just a temp workaround.
-
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.
-
Rebooted, updated squid package. Seems to be ok. Content filtering and virus scanning are working.
-
Thx for fixing this issue
Transparentproxy works fine now.
-
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.
-
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.
-
There is a port issue when you click Lightsquid. I see myip:9000:7445
-
There is a port issue when you click Lightsquid. I see myip:9000:7445
I'll look into that.
-
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…
-
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.
-
I fixed the perl path (should be /usr/local/bin/perl) and fixed the parsing of the link with the port.
-
I split the unrelated hit % posts off into their own thread and cleaned up the references here.
-
One more thing:
a) After reboot Lightsquid Web Server won
t 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.:)
-
a) After reboot Lightsquid Web Server won
t 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 ?
