Squid / Squidguard - or go with freestanding instances?
-
I'm hearing rumblings in the forums that squidguard is badly neglected with no maintainer.
I've been using it with decent enough results, but just kind of here and there.
I need to get more serious and structured as I roll out web filtering across our sites.
Where are the pain points?
Is it an issue with just newer pf builds?
Most of my sites are 2.2.6 - but I added squid - no squidguard yet - to a 2.3.2 site with no issues yet.
Mind you, that was just an hour or so ago, but I did it unannounced so as not to influence user perception.
I can add a separate vm for squid if that's going to make a big difference in stability.
pf is already running under vsphere, so adding another vm is nothing.
-
Where are the pain points?
Is it an issue with just newer pf builds?The pain points? There's a slew of annoying serious bugs in the code that will not ever get fixed because the code is unreadable piece of mess that will make your head explode in minutes when trying to decipher it. (And no, it has no relation to pfSense version.)
-
Where are the pain points?
Is it an issue with just newer pf builds?The pain points? There's a slew of annoying serious bugs in the code that will not ever get fixed because the code is unreadable piece of mess that will make your head explode in minutes when trying to decipher it. (And no, it has no relation to pfSense version.)
Though for people who like a challenge, here is the github page (fixed) https://github.com/pfsense/FreeBSD-ports/tree/devel/www/pfSense-pkg-squidGuard
side note why is the link wrong in the package manger? points to https://github.com/pfsense/FreeBSD-ports/commits/devel/www/pfSense-pkg-squidGuard
-
dok, should we use pfblocker_ng instead in your opinion?
-
I love pfBNG but it's a limited replacement because it's DNS – can only use that for things that should be always blocked, no matter what URL.
side note why is the link wrong in the package manger? points to https://github.com/pfsense/FreeBSD-ports/commits/devel/www/pfSense-pkg-squidGuard
It's not wrong, it's supposed to be used as a changelog, not a pointer to code. Plus you've linked a wrong repo; should be https://github.com/pfsense/FreeBSD-ports/tree/devel/www/pfSense-pkg-squidGuard - pfsense-packages is dead pre-2.3 stuff.
-
ah thanks was a bit hard to find
with https://github.com/pfsense/FreeBSD-ports/commits/devel/www/pfSense-pkg-squidGuard i get Sorry, this commit history is taking too long to generate
-
ah thanks was a bit hard to find
https://doc.pfsense.org/index.php/Package_Port_List
with https://github.com/pfsense/FreeBSD-ports/commits/devel/www/pfSense-pkg-squidGuard i get Sorry, this commit history is taking too long to generate
GitHub sucks.