E2guardian package for pfsense - $??
-
As of this date, what is the e2guardian version available for pfsense?
I need at least 3.1, for a working ssl_bump funtionThe current version in ports is 3.4.0.3, so if a package ever gets built, it will be at least that version.
-
As of this date, what is the e2guardian version available for pfsense?
I need at least 3.1, for a working ssl_bump funtionThe current version in ports is 3.4.0.3, so if a package ever gets built, it will be at least that version.
I tried to install e2g manually, but the pfsense repository does not have the application. Look for the application in pkg.freebsd.org but did not found the e2g version you are referring. Where do I get it?
-
You can install it manually, but I wouldn't suggest it. The way it stands now it's not all that stable. I would suggest (And it's what I did), installing E2Guardian on something like ubuntu then use nat to point all traffic at the second box running E2Guardian. Then E2Guardian can point all traffic back to the PFSense box and squid will proxy and send it on. Thats the most stabe way of setting up for now. It's not the best because configs are a pain, but it's more stable.
-
I tried to install e2g manually, but the pfsense repository does not have the application. Look for the application in pkg.freebsd.org but did not found the e2g version you are referring. Where do I get it?
pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/e2guardian-3.4.0.3.txz
This just installs the FreeBSD port, not the pfSense bits… -
You can install it manually, but I wouldn't suggest it. The way it stands now it's not all that stable. I would suggest (And it's what I did), installing E2Guardian on something like ubuntu then use nat to point all traffic at the second box running E2Guardian. Then E2Guardian can point all traffic back to the PFSense box and squid will proxy and send it on. Thats the most stabe way of setting up for now. It's not the best because configs are a pain, but it's more stable.
Can you send me a configuration file example for e2g, squid and NAT (screenshot) to follow your suggestion?
By the way the NAT is the one at Ubuntu or the one at pfsense (Newbie question) ? -
I tried to install e2g manually, but the pfsense repository does not have the application. Look for the application in pkg.freebsd.org but did not found the e2g version you are referring. Where do I get it?
pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/e2guardian-3.4.0.3.txz
This just installs the FreeBSD port, not the pfSense bits…Can I use this pkg to follow the manual installation procedure with Marcello codes?
-
Can I use this pkg to follow the manual installation procedure with Marcello codes?
You should be able to use the manual instructions from the 3.0.4 version, but I have not tried it. Let us know how it goes.
-
Can I use this pkg to follow the manual installation procedure with Marcello codes?
You should be able to use the manual instructions from the 3.0.4 version, but I have not tried it. Let us know how it goes.
Currently I am working with Captive Portal problems, but as soon as I try it, will post my findings here.
-
You can install it manually, but I wouldn't suggest it. The way it stands now it's not all that stable. I would suggest (And it's what I did), installing E2Guardian on something like ubuntu then use nat to point all traffic at the second box running E2Guardian. Then E2Guardian can point all traffic back to the PFSense box and squid will proxy and send it on. Thats the most stabe way of setting up for now. It's not the best because configs are a pain, but it's more stable.
Can you send me a configuration file example for e2g, squid and NAT (screenshot) to follow your suggestion?
By the way the NAT is the one at Ubuntu or the one at pfsense (Newbie question) ?I don't have all that together, but it's pretty easy to setup a nat on PFSense for all port 80 traffic to get routed to your E2Guardian box. Then you setup E2Guaridan to point at SquidProxy running on PFSense. The setup of E2Guardian can be found online fairly easily. All your doing with PFSense is funneling traffic through the E2Guadian box with NAT and then back out through Squid.
https://www.linux.com/learn/filter-content-your-home-network-e2guardian
Once you have E2Guardian installed
Edit ./etc/E2Guardian/E2Guardian.conf Change the Proxy IP and the Proxy port to match your PFSense Firewall and SquidProxy. After that it's just a matter of editing the configs for E2Guardian, which I admit is much harder than the PFSense plugin.
-
Is there any news on this? I'm more than happy to throw £20 at it - I really need content filtering on my network. I installed pfsense today primarily because I'd been told that dansguardian was a "one click install" only to discover that it isn't anymore…
-
Can I use this pkg to follow the manual installation procedure with Marcello codes?
You should be able to use the manual instructions from the 3.0.4 version, but I have not tried it. Let us know how it goes.
Currently I am working with Captive Portal problems, but as soon as I try it, will post my findings here.
Since I am doing my test on VMs I created a VM Clone to test the e2g manual install.
I did the install and seems OK. But after making changes to the configuration, it shows a message saying that I must apply for the changes to take effect. I do not find an Apply button so I do not know how to do the apply.
Also the service does not start (probably because is the first time and changes need to be applied). Any way I do not see e2g errors on system log. I do see e2g logs about saved changes being made.
I will really appreciate if someone shed some light.
-
I tried making the same question for Dansguardian and it seems that to Apply the changes one just have to restart the service.
Since the service did not started through the GUI I look for a way to do it manually. I found other services are found in /usr/local/sbin so I look for e2g there and it was. So I went to the shell and execute ./e2guardian without parameters and it executed no showing errors so I guess it run successfully. Went to Services Status and e2g appeared Running. I then did Restart on the GUI and it seem that worked. I tried to Stop the service using the GUI but it did not stop. Both times went to the System Logs but did not show any logs for e2g service start/restart/stop.
Then I went to shell again and tried to stop service by "./e2guardian stop" but it did not worked, it gives me a notice that it is running. So I do not know how to stop it and do not know if Restart is really working.
-
I found in a Dansguardian thread how to stop the service "./e2guardian -q" in shell. Then to start do "./e2guardian". To restart in one command I still have not found. When I execute ./e2guardian again says is already running, that message is shown on the System Logs, but stopping/starting is not shown. That is probably why the restart is not shown either.
If anyone know how to turn on in the System Logs the start/stop of e2g it will be appreciated.
-
I confirm the GUI Restart does not work. I made a change and it didn't pickup the changes when Restarting using the GUI. I had to go to shell and manually stop then restart to apply.
-
Is anyone working on getting official package? Or is that what you are all doing?
-
After installing e2guardian from freebsd ports using the manual procedure it seems to be working OK (Not perfect), but it did not work with SSL.
I run "./e2guardian -v". I did not see ssl support enabled. This is sad. :'(
The e2guardian 3.4 (current stable version) supports ssl, it should be compiled with ssl support enabled. I bet the majority of the people is expecting the e2g package with ssl support enabled.
-
After installing e2guardian from freebsd ports using the manual procedure it seems to be working OK (Not perfect), but it did not work with SSL.
I run "./e2guardian -v". I did not see ssl support enabled. This is sad. :'(
The e2guardian 3.4 (current stable version) supports ssl, it should be compiled with ssl support enabled. I bet the majority of the people is expecting the e2g package with ssl support enabled.
Do you mind if you share how you got the e2guardian packaged from the freebsd ports? I've added the pkg manually like this:
pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/e2guardian-3.4.0.3.txz
Fetching e2guardian-3.4.0.3.txzBut I'm not sure what to do after that… How do you even start it? If I type in "e2guardian" It says command not found.
-
I tried to install e2g manually, but the pfsense repository does not have the application. Look for the application in pkg.freebsd.org but did not found the e2g version you are referring. Where do I get it?
pkg add http://pkg.freebsd.org/freebsd:10:x86:64/latest/All/e2guardian-3.4.0.3.txz
This just installs the FreeBSD port, not the pfSense bits…This is it.
-
Sorry. You have to perform the full manual install procedure. In this thread you can find a link some pages before.
-
You can install it manually, but I wouldn't suggest it. The way it stands now it's not all that stable. I would suggest (And it's what I did), installing E2Guardian on something like ubuntu then use nat to point all traffic at the second box running E2Guardian. Then E2Guardian can point all traffic back to the PFSense box and squid will proxy and send it on. Thats the most stabe way of setting up for now. It's not the best because configs are a pain, but it's more stable.
I'm thinking this is pretty much the only option if you want to inspect content with pfsense. Is there any cons to this kind of set up? Is there any overhead in routing if you are routing traffic first to the pfsense box, then to the e2guardian box, then back to the pfsense box? I would like to keep my network as fast as possible. How would traffic monitoring look? Would the pfsense box see all bandwidth being used by the e2guardian box or would it preserve the original IP of the host?
Thanks!