Unofficial E2guardian package for pfSense
-
[quote] .patch --check --forward --ignore-whitespace Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- pkg_edit.orig.php 2017-04-05 16:25:04.960401000 +0000 |+++ pkg_edit.php 2017-04-03 22:56:33.184313000 +0000 -------------------------- Patching file pkg_edit.php using Plan A... Hunk #1 failed at 651. 1 out of 1 hunks failed while patching pkg_edit.php done [/quote] What pfSense version are you using? I'm on 2.3.3 2.3.3-RELEASE-p1 (amd64) built on Thu Mar 09 07:17:41 CST 2017 FreeBSD 10.3-RELEASE-p17 It doesn't bother me all that much. I can make the change manually. It was more for your benefit so that you could get it fixed for future installs. -
It doesn't bother me all that much. I can make the change manually. It was more for your benefit so that you could get it fixed for future installs.
Sure. I'll test all install process(including blacklist) on a 2.3.3_p1 version too.
-
Hmmm. That's what I did. I get the alert of "E2guardian - Blacklist update process started" but never one that it completes. How can I see what's going on?
/usr/local/www/e2guardian.php fetch_blacklistThis is the script that fetches and apply the blacklist.
-
Awesome, thanks! Now that it seems to be working, any advice on getting it to work with Squid transparently?
-
Awesome, thanks! Now that it seems to be working, any advice on getting it to work with Squid transparently?
Dansguardian as two work modes.
The sandwich mode, where there is a squid -> e2guardian -> tinyproxy or any other cache
Or the starndard mode where it stays in front of squid or any other cache and try to forward client authentication requests
What mode are you using?
E2guardian transparent mode while in front of squid is setup manually, creating a nat rule pointing to its listening port.
-
I've moved the download and apply blacklist options from combo values to buttons on xml
-
It might be just my setup but there isn't any defaults for the 4 options under Anti-Virus. The boxes have no text. Also, under Search Engine there are no options only an Add/Save button. Click on Add, no options; only save. I downloaded the latest xml files this morning.
running on
2.3.4-DEVELOPMENT (amd64)
built on Tue Apr 04 16:31:17 CDT 2017
FreeBSD 10.3-RELEASE-p17 -
I'll test it today.
I'm also including the ssl group options introduced on e2guardian since 3.1 version
-
Awesome, thanks! Now that it seems to be working, any advice on getting it to work with Squid transparently?
Dansguardian as two work modes.
The sandwich mode, where there is a squid -> e2guardian -> tinyproxy or any other cache
Or the starndard mode where it stays in front of squid or any other cache and try to forward client authentication requests
What mode are you using?
E2guardian transparent mode while in front of squid is setup manually, creating a nat rule pointing to its listening port.
It would be transparent. SquidGuard doesn't need any NAT rules and just integrates with Squid. Does e2Guardian not behave the same way? I want it transparent with Squid so do I need a NAT rule that points LAN 80 to LAN 8080 and then e2G will automatically forward to Squid?
-
E2guardian is a daemon, not a squid helper. You need to configure ip, port , forward rules as a normal proxy daemon.
-
Ah, it's completely independent of Squid, then. Where does it sit in-line? I'll check the manuals tomorrow but does it sit between Squid and the user or between Squid and the WAN? I'm sure the forwards needed are in the documentation so I'll see if I can find the ports needed in the morning. Thanks for all your help!
-
Ah, it's completely independent of Squid, then. Where does it sit in-line? I'll check the manuals tomorrow but does it sit between Squid and the user or between Squid and the WAN? I'm sure the forwards needed are in the documentation so I'll see if I can find the ports needed in the morning. Thanks for all your help!
E2guardian replaces squidguard and in some cases can do all squid job too but it needs a cache peer to fetch urls.
The idea of this package is to have a full-feature replacement for squidguard and depending on you user authentication needs, dansguardian package itsel will do the job as it include tynyproxy for url fetch.
-
I've updated the binaries and GUI to include dnsauth and icap antivirus integration. The idea is to call clamv exactly the same way squid does to avoid package conflict.
-
Latest TODO as far as I can see
-
add gui group ssl options introduced since E2guardian 3.1
-
fix search acl tab and configuration
-
increase tiny proxy config values to March E2guardian start process configuration
-
Configure clamav icap
-
-
A method of configuring it to listen on a CARP address via the GUI would be great too - Squid you can do this from the 'Advanced Features - Custom Options'… or is this not possible with e2g, looks like multi interface listen causes problems at the moment?
-
It looks like multi interface listen causes problems at the moment?
Not anymore. I've hard coded a config option util multi auth psr port is better implemented on gui.
-
How do we update? Rerun the script? That's what I've done and I've got some changes.
-
How do we update? Rerun the script? That's what I've done and I've got some changes.
Yes, rerun. Few days ago I've updated the e2guardian binaries to include icap and dnsauth.
-
I reran the script and suddenly e2Guardian wouldn't load. The error was:
/usr/local/etc/rc.d/e2guardian.sh: WARNING: failed to start e2guardian Error parsing the e2guardian.conf file or other e2guardian configuration files Error loading auth plugins auth_plugin_load() returned NULL pointer with config file: /usr/local/etc/e2guardian/authplugins/proxy-header.conf Unable read plugin config plugname variable /usr/local/etc/e2guardian/authplugins/proxy-header.confI was able to get it to start by uncommenting the last 3 lines in /usr/local/etc/e2guardian/authplugins/proxy-header.conf:
low case header = '' plugname = 'proxy-header'Not sure what uncommenting them does but it allows it to load.
-
Well, it loads but it doesn't do anything. Whether I try to create a NAT rule or just set the browser to 8080, no pages load. They all just time out. I'm watching /var/log/system.log but it isn't showing anything.
