Unofficial E2guardian package for pfSense

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?

lindsay

Is there an option to edit first post in topic how to get e2guardian to show up atlest in list?

ravegen

@marcelloc

I have FQDN in one Firewall Alias that I created and used on Bypass Proxy for These Source IPs and Bypass Proxy for These Destination IPs. The problem is, I guess it is not working on alias because it is not bypassing on those FQDN but when I put it direct, it bypasses it properly.

I am on Pfsense 2.4.4

guilherme.lellis

Mesma situação aqui, acompanhando e aguardando a resposta do Marcello.

pfsensation

@ravegen said in Unofficial E2guardian package for pfSense:

@marcelloc

I have FQDN in one Firewall Alias that I created and used on Bypass Proxy for These Source IPs and Bypass Proxy for These Destination IPs. The problem is, I guess it is not working on alias because it is not bypassing on those FQDN but when I put it direct, it bypasses it properly.

I am on Pfsense 2.4.4

I'm doing something very similar to allow certain websites to bypass E2 Guardian. What's your alias type? You may have got that set incorrectly, because it works fine for me.

ravegen

@pfsensation

My alias type is HOST.

Yes, I have this configuration work. But now I have so many aliases at ip addresses placed there. I do not know if there is a limitation on how many aliases or ip addresses to place on that bypass list.

I noticed that when I placed sites, aliases and ip address on the bypass list, those will not appear on the realtime log. However, since the sites on the aliases I made shows on the realtime log, then i believe it is not working.

pfsensation

@ravegen said in Unofficial E2guardian package for pfSense:

@pfsensation

My alias type is HOST.

Yes, I have this configuration work. But now I have so many aliases at ip addresses placed there. I do not know if there is a limitation on how many aliases or ip addresses to place on that bypass list.

I noticed that when I placed sites, aliases and ip address on the bypass list, those will not appear on the realtime log. However, since the sites on the aliases I made shows on the realtime log, then i believe it is not working.

After placing new entries in your alias, are you going back to E2 Guardian and pressing save then apply? You need to actually restart the E2 Guardian daemon for the changes to take effect right away. It's just how it works unfortunately, E2 Guardian will only resolve the hosts in your alias when it starts up. That process seems to work for me, and allows me to keep it E2 Guardian GUI cleaner without having too many bypasses directly in there.

ravegen

I have another question about bypass list in e2guardian.

Why is there some sites that even you put it in the exception list in the ACL, it still does not work or inaccessible that you need to put it to the bypass list.

Why is that? What is wrong with those sites ?

pfsensation

@ravegen said in Unofficial E2guardian package for pfSense:

I have another question about bypass list in e2guardian.

Why is there some sites that even you put it in the exception list in the ACL, it still does not work or inaccessible that you need to put it to the bypass list.

Why is that? What is wrong with those sites ?

What sites? How are you accessing those sites? What's the error log?