Unofficial E2guardian package for pfSense

marcelloc

After 12hs, still no crashes. This week I'll push more clients to e2g and see how it goes.

good memory usage and performance. results from top -n -o res

e2g_top.PNG_thumb

Mr. Jingles

@marcelloc:

To remove tinyproxy, install it from Unofficial repo and then uninstall. The same with e2guardian.

The c-icap is a package from squid

Sorry to ask, Marcello, but how do install from unofficial repo? pkg install and then…?

Pfsensation above this reply says uninstalling isn't going to work(?)

marcelloc

@Mr.:

Sorry to ask, Marcello, but how do install from unofficial repo? pkg install and then…?

Just enabled the Unofficial repo following instructions from the first post and then go to GUI under system -> package manager

pfsensation

@marcelloc:

I'll remove the debug version from repo. Are you on 2.3 amd64?

EDIT

done. No debug version on repo. An uninstall and reinstall should fix.

Yes I am on 2.3 amd64. Reinstalled again, this time I got a new option in the GUI.

However when I type "/usr/local/sbin/e2guardian" I still get the output below.

EDIT: Ran update via console, and got a new E2Guardian update. I guess this is it?

EDIT2:
Updated from the console, now it's not giving me a tonne of information. Why the inconsistency when updating from the webgui or the console?? The annoying thing is, when updating from the console, usually it forces a reboot. You may not want your internet at your work, or whatever organisation you deployed it to go down for a minute or two.

marcelloc

There is no binary update on upgrade. You need to uninstall it to remove e2guardian bsd package.

And after installing, you need to save config and apply to be sure you are not using default bsd package conf files.

The menu on console is for a system upgrade, to update packages on console, use pkg update, pkg install, etc…

pfsensation

@marcelloc:

There is no binary update on upgrade. You need to uninstall it to remove e2guardian bsd package.

And after installing, you need to save config and apply to be sure you are not using default bsd package conf files.

The menu on console is for a system upgrade, to update packages on console, use pkg update, pkg install, etc…

Uninstalling and reinstalling didn't work for me, but updating via console just by hitting "13" did the trick, although restarting the entire system. I'll try pkg update next time. But what I meant was, why couldn't I return to normal version via GUI? Why was it necessary to upgrade via console to get E2Guardian on non-debug version?

Sorry for the questions, it's becoming a bit confusing. The latest E2Guardian seems to be behaving better so far. Lets see how it goes.

marcelloc

I have no idea why it doesn't work for you. Here every time I remove the package, the binaries, services and menus goes too.

pfsensation

@marcelloc:

I have no idea why it doesn't work for you. Here every time I remove the package, the binaries, services and menus goes too.

I guess it doesn't matter anymore, I've managed to get on the latest version of E2Guardian. Can you add a script to make sure when upgrading via the WebGUI, that the old binaries are always deleted or removed? This would remove the need to have to completely uninstall E2Guardian, then install it again.

Also what kind of hardware do you use Marcelloc? Have you tweaked around with any extra settings on E2Guardian for perhaps even better performance?

How many HTTP workers do you use? Have you tweaked anything in the limits tab?

marcelloc

I'm using 4000 http workers on a dell r710 hardware. I did not included all users yet but will do soon.

About the package, the normal process is this. The binaries package gets updated only on version changes. PfSense-pkg has the gui files and bsd package has the binaries.

jetberrocal

@marcelloc:

After 12hs, still no crashes. This week I'll push more clients to e2g and see how it goes.

good memory usage and performance. results from top -n -o res

Is this using all features of E2g?

marcelloc

@jetberrocal:

Is this using all features of E2g?

No MITM yet. I need to deploy the CA certificate first.

marcelloc

For those who wants an e2guardian widget until I push an update to the repo, run this on console or diagnostics -> command prompt

fetch -o /usr/local/www/widgets/widgets/e2guardian.widget.php https://raw.githubusercontent.com/marcelloc/Unofficial-pfSense-packages/master/pkg-e2guardian4/files/usr/local/www/widgets/widgets/e2guardian.widget.php

jetberrocal

@marcelloc:

@jetberrocal:

Is this using all features of E2g?

No MITM yet. I need to deploy the CA certificate first.

Assuming that mitm works without crashing, how stable do you think is e2g (scale 1 to 10)?

marcelloc

@jetberrocal:

Assuming that mitm works without crashing, how stable do you think is e2g (scale 1 to 10)?

With squid "protecting it from crashes", 10. No crashes since I've configured this way but the code need to be fixed. Unfortunately I'm not c++ devel, so I take ours trying to debug.

pfsensation

@marcelloc:

@jetberrocal:

Assuming that mitm works without crashing, how stable do you think is e2g (scale 1 to 10)?

With squid "protecting it from crashes", 10. No crashes since I've configured this way but the code need to be fixed. Unfortunately I'm not c++ devel, so I take ours trying to debug.

Sun Jun 11 00:13:47 BST 2017 start
Sun Jun 11 00:13:58 BST 2017 start
Sun Jun 11 10:11:38 BST 2017 start
Sun Jun 11 10:11:40 BST 2017 start
Sun Jun 11 10:11:45 BST 2017 start
Sun Jun 11 10:11:50 BST 2017 start
Sun Jun 11 10:12:00 BST 2017 start
Sun Jun 11 10:12:05 BST 2017 start
Sun Jun 11 10:12:15 BST 2017 start
Sun Jun 11 11:17:38 BST 2017 start
Sun Jun 11 11:17:46 BST 2017 start
Sun Jun 11 11:30:12 BST 2017 start
Sun Jun 11 11:30:21 BST 2017 start
Sun Jun 11 11:58:47 BST 2017 start
Sun Jun 11 11:59:05 BST 2017 start
Sun Jun 11 13:37:00 BST 2017 start
Sun Jun 11 13:37:05 BST 2017 start
Sun Jun 11 13:37:10 BST 2017 start
Sun Jun 11 13:37:15 BST 2017 start
Sun Jun 11 13:37:20 BST 2017 start
Sun Jun 11 13:37:25 BST 2017 start
Sun Jun 11 13:37:30 BST 2017 start
Sun Jun 11 13:37:35 BST 2017 start
Sun Jun 11 13:37:40 BST 2017 start
Sun Jun 11 13:37:45 BST 2017 start
Sun Jun 11 13:37:50 BST 2017 start
Sun Jun 11 13:38:00 BST 2017 start
Sun Jun 11 13:38:05 BST 2017 start
Sun Jun 11 16:25:20 BST 2017 start
Sun Jun 11 22:30:00 BST 2017 start
Sun Jun 11 22:30:05 BST 2017 start
Sun Jun 11 22:30:10 BST 2017 start
Sun Jun 11 22:30:15 BST 2017 start
Sun Jun 11 22:30:20 BST 2017 start
Sun Jun 11 22:30:25 BST 2017 start
Sun Jun 11 22:30:35 BST 2017 start
Sun Jun 11 23:56:10 BST 2017 start

Haven't had any crashes since the last update it seems… :o

I had to increase HTTP workers though, even in my home environment.

PS: Fred pushed out some more fixes on Github on the retryfix branch.

marcelloc

@pfsensation:

I had to increase HTTP workers though, even in my home environment.

Did you added the widget too?

jetberrocal

What is the widget about?

pfsensation

@marcelloc:

@pfsensation:

I had to increase HTTP workers though, even in my home environment.

Did you added the widget too?

I did now :D - Although there's not much load on right now.

marcelloc

@pfsensation, Do you mind if I suggest your custom error page to be the default error page of e2guardian package on github's project?

error_page_en.txt

pfsensation

@marcelloc:

@pfsensation, Do you mind if I suggest your custom error page to be the default error page of e2guardian package on github's project?

Sure! However, you may want to add the users group to the information too. It can be incredibly useful for debugging, or is that still crashing E2Guardian?

Here's a screenshot below