Unofficial E2guardian package for pfSense

pfsensation

@kenpachizaraki said in Unofficial E2guardian package for pfSense:

@pfsensation yes dhcp vlans are working correctly. Right now i enabled squid but no blocking on sites. Just pure proxy. I want to use e2g since it can block https without installing cert. Ill post result later.

I personally would steer away from Squid unless you really need to fill in the gap for multiwan support. Pfsense runs a old version of Squid that's pretty slow by today's standards. In my own testing, streaming sites like YouTube were a lot slower with Squid. E2 Guardian v5 on the other hand has been super fast and the code is way more efficient now.

kenpachizaraki

@pfsensation yes that why i like e2g coz of that reason. However without multi wan support the only way is to use squid. If only e2g works multiwan then i can ditched squid. Maybe someone was able to work it out since it is common to have multi wan.

pfsensation

@kenpachizaraki said in Unofficial E2guardian package for pfSense:

@pfsensation yes that why i like e2g coz of that reason. However without multi wan support the only way is to use squid. If only e2g works multiwan then i can ditched squid. Maybe someone was able to work it out since it is common to have multi wan.

I used to use multi wan with gateway groups before but it turned out to be a pain sometimes, you need to spend quite some time setting it up correctly. You can't truly use both lines as one as the Web server on the other end will always see two IP's. Now at home I've only got a multi wan to fail over to free street WiFi lol, if my main connection fails. So pfsense can at least get a connection to send out an email notification to me.

pfsensation

Just as a heads up guys, pfSense 2.4.4 is released. But E2Guardian package has not yet been updated to support it. Hopefully it will be updated shortly by @marcelloc
so don't update until a new package has come out. Otherwise you'll be left with a wide open network without filtering!

Also if you have pfBlockerNG installed, do not update it!! - It completely messes up the PHP GUI! I found out the hard way...

marcelloc

Starting with 2.4.4, only official packages are listed on default installation.

To workaround this limitation, apply the patch on my unofficial repo.

https://github.com/marcelloc/Unofficial-pfSense-packages/blob/master/244_unofficial_packages_list.patch

apply using system patches package.

ravegen

Marcelloc,

I applied the patch thru system patches package but the E2Guardian package is still not available on the package list. How can I reinstall E2Guardian package. What will we do now !

asterix

Same here. The patch does not work. Can’t see e2 or wpad packages.

pfsensation

The patch works perfectly fine. I'm using it at the moment.

Make sure you run the command in the first post again after the update to make sure that the unofficial repo is still added to pfsense.

Steps : run the command in the first post to add the unofficial repo

Install system patches

Copy the code from the patch Marcello posted (the entire thing) give the patch a description and save it. Click test and then apply. Now when you go to the package manager, you will see E2 Guardian and WPAD.

ravegen

pfsensation,

yes, I have run the command of the unofficial repo ,installed the system patches and placed the url https://github.com/marcelloc/Unofficial-pfSense-packages/blob/master/244_unofficial_packages_list.patch on the URL/COMMIT ID and then applied it. but nothing happened, no e2guardian package on the package list.

I used base directory : /usr/local/etc/pkg/repos/
all other options are defaults

I have also tried base directory : / but still no progress.

pfsensation

@ravegen said in Unofficial E2guardian package for pfSense:

pfsensation,

yes, I have run the command of the unofficial repo ,installed the system patches and placed the url https://github.com/marcelloc/Unofficial-pfSense-packages/blob/master/244_unofficial_packages_list.patch on the URL/COMMIT ID and then applied it. but nothing happened, no e2guardian package on the package list.

I used base directory : /usr/local/etc/pkg/repos/
all other options are defaults

I have also tried base directory : / but still no progress.

Don't place the URL. Copy the contents of the script and paste it into the patch box. Remember to remove the URL... Leave base directory as default "/"

ravegen

you mean this content below,

--- /etc/inc/pkg-utils.orig 2018-09-24 17:51:32.458825000 -0300
+++ /etc/inc/pkg-utils.inc 2018-09-24 17:51:54.387033000 -0300
@@ -388,7 +388,7 @@
if ($base_packages) {
$repo_param = "";
} else {

  $repo_param = "-r {$g['product_name']}";

```
  $repo_param = "";
```
}

/*
@@ -485,7 +485,7 @@
$err);
if (!$base_packages &&
rtrim($out) != $g['product_name']) {

```
  		continue;
```

  		//continue;
  	}

  	$pkg_info['installed'] = true;

ravegen

pfsensation

thanks so much, it went ok.

pfsensation

@ravegen said in Unofficial E2guardian package for pfSense:

pfsensation

thanks so much, it went ok.

Awesome, glad it worked!

ucribrahim

@pfsensation I just tried over again over and over but damn it. I didn't understand while I was reading your instructions. I'm just confused, could you please tell me the steps one by one that I need to do for install e2guardian in 2.4.4 version of pfsense.)

Thank you.

asterix

Getting this PHP error.. in crash reports.

PHP ERROR: Type: 1, File: /etc/inc/service-utils.inc, Line: 668, Message: Uncaught ArgumentCountError: Too few arguments to function service_control_stop(), 1 passed in /usr/local/www/e2guardian_logrotate.php on line 42 and exactly 2 expected in /etc/inc/service-utils.inc:668
Stack trace:
#0 /usr/local/www/e2guardian_logrotate.php(42): service_control_stop('e2guardian')
#1 {main}

pfsensation

@ucribrahim said in Unofficial E2guardian package for pfSense:

@pfsensation I just tried over again over and over but damn it. I didn't understand while I was reading your instructions. I'm just confused, could you please tell me the steps one by one that I need to do for install e2guardian in 2.4.4 version of pfsense.)

Thank you.

Copy and paste the patch in, as I've done in the screenshot below
alt Unofficial packages patch

Then save it, press test and then apply the patch. Now if you go to the package manager. You will see E2 Guardian!

pfsensation

@asterix said in Unofficial E2guardian package for pfSense:

Getting this PHP error.. in crash reports.

PHP ERROR: Type: 1, File: /etc/inc/service-utils.inc, Line: 668, Message: Uncaught ArgumentCountError: Too few arguments to function service_control_stop(), 1 passed in /usr/local/www/e2guardian_logrotate.php on line 42 and exactly 2 expected in /etc/inc/service-utils.inc:668
Stack trace:
#0 /usr/local/www/e2guardian_logrotate.php(42): service_control_stop('e2guardian')
#1 {main}

I haven't experienced that at all, is this after upgrading to 2.4.4?

Go ahead and start by re-installing E2 Guardian and see if that removes the error.

asterix

Again crashed,. Did a reinstall yesterday. Looks like the log rotation script is killing it.

amd64
11.2-RELEASE-p3
FreeBSD 11.2-RELEASE-p3 #17 e6b497fa0a3(RELENG_2_4_4): Thu Sep 20 09:04:45 EDT 2018 root@buildbot3:/crossbuild/ce-244/obj/amd64/WvDslnYb/crossbuild/ce-244/pfSense/tmp/FreeBSD-src/sys/pfSense

Crash report details:

PHP Errors:
[27-Sep-2018 00:00:00 America/New_York] PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function service_control_stop(), 1 passed in /usr/local/www/e2guardian_logrotate.php on line 42 and exactly 2 expected in /etc/inc/service-utils.inc:668
Stack trace:
#0 /usr/local/www/e2guardian_logrotate.php(42): service_control_stop('e2guardian')
#1 {main}
thrown in /etc/inc/service-utils.inc on line 668

No FreeBSD crash data found.

pfsensation

@asterix said in Unofficial E2guardian package for pfSense:

Again crashed,. Did a reinstall yesterday. Looks like the log rotation script is killing it.

amd64
11.2-RELEASE-p3
FreeBSD 11.2-RELEASE-p3 #17 e6b497fa0a3(RELENG_2_4_4): Thu Sep 20 09:04:45 EDT 2018 root@buildbot3:/crossbuild/ce-244/obj/amd64/WvDslnYb/crossbuild/ce-244/pfSense/tmp/FreeBSD-src/sys/pfSense

Crash report details:

PHP Errors:
[27-Sep-2018 00:00:00 America/New_York] PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function service_control_stop(), 1 passed in /usr/local/www/e2guardian_logrotate.php on line 42 and exactly 2 expected in /etc/inc/service-utils.inc:668
Stack trace:
#0 /usr/local/www/e2guardian_logrotate.php(42): service_control_stop('e2guardian')
#1 {main}
thrown in /etc/inc/service-utils.inc on line 668

No FreeBSD crash data found.

I experienced it today. Yeah it looks like the log rotate script is what's causing the crash. Which means logs won't be rotated. I'll have a look at it when I have a chance.

pfsensation

@marcelloc I had a look, it looks like e2guardian isn't defined in /etc/inc/service-utils.inc. I attempted to manually define it but wasn't too sure of the parameters. Can you shed some light?