Unofficial E2guardian package for pfSense
-
pfsensation,
not all could be as knowledgeable like you guys. see, anyone can play with pfsense as it is downloable. for instance, house or personal use.
so a manual for telling this device is 110 volts and not 220 volts is definitely valuable.
That's my point, I learnt it myself. The concept of E2 Guardian and getting it up and running is simple. If you need any fine detail just ask. Also as mentioned by others, most of DansGuardian documentation are still valid and apply, if you really need a manual read that. I used the manual only to better understand authentication types. If you are planning to run E2 Guardian from home, I suggest using IP addresses, it's quick and simple to setup.
The main problems you'll probably run into it in some cases overblocking, I've pushed out fixes for it to the official source code. It should help a lot against those.For a while I was having a lot of issues with E2 Guardian on my box, I reinstalled pfSense and now everything seems to work fine. So I have got everything working to a very good degree now. So it is actually usable, however if you have money and just want something that works go with Smoothwall Guardian.
Yes it costs money, but you never need to worry about blacklists or tinkering. Everything is done for you.
E2 Guardian although extremely powerful, it's still a work in progress and with the next version it'll improve massively (V5) as a lot of the code is being rewritten. -
My suggestion (if you are new) is get squid proxy filtering (transparent, mitm and wpad ) working for squidguard first then once it is all working try switching squidguard over to E2guardian.
I am sure once the package goes stable there will be more documentation.
-
its hard playing something that gets broken and you need to start from scratch again. everytime, it does not work and seems broken, you need to reformat and reinstall pfsense and such waste of time while the maker most probably knows the right way putting into clear and exacting documentation.
-
its hard playing something that gets broken and you need to start from scratch again. everytime, it does not work and seems broken, you need to reformat and reinstall pfsense and such waste of time while the maker most probably knows the right way putting into clear and exacting documentation.
If you don't know what you're doing, then it's probably what you will need to do with everything you try to play without a minimum knowledge.
Hope you improve your IT skills and spend more energy helping collaborative opensource projects than complaining, blaming, depreciating or whatever you're trying to do here.
-
its hard playing something that gets broken and you need to start from scratch again. everytime, it does not work and seems broken, you need to reformat and reinstall pfsense and such waste of time while the maker most probably knows the right way putting into clear and exacting documentation.
If you don't know what you're doing, then it's probably what you will need to do with everything you try to play without a minimum knowledge.
Hope you improve your IT skills and spend more energy helping collaborative opensource projects than complaining, blaming, depreciating or whatever you're trying to do here.
Marcello dropped the fire xD
Techbee, even I get frustrated and complain sometimes. However I contribute to the project as much as possible and the source code, even if it's small things I discover or big overhauls like the more modernised friendly block page. If you have issues at least post some logs or something so we can understand the problem better. But first of all I recommend you do a clean fresh pfsense install, this helped me massively even though it's annoying. Backup your settings and restore only rules, don't restore packages. And clean install E2 Guardian.
PS: @Marcello A certain closed source inferior alternative to E2 Guardian on pfSense is taking a hit due to E2 Guardian being free and open source and not requiring a subscription being charged at ultra stupid levels (not gonna name and shame). You should be happy lol xD
-
Is it just me or after around 2 days E2 Guardian goes haywire with RAM usage. This problem is certainly new, usage for E2 Guardian becomes really high and RAM gets swapped. This is the second time it's happened to me, reinstall fixes it for another two days.
Weird… Especially since now there's only one user, there should be nothing really using up that much RAM. Seems like there could be a memory leak somewhere.
-
Report it on e2guardian git issues. I'm using in the package the latest code from 4.1.2
Does a restart om the service is enough to free some memory?
-
Report it on e2guardian git issues. I'm using in the package the latest code from 4.1.2
Does a restart om the service is enough to free some memory?
Yep a restart pretty much instantly clears the RAM. So I guess it's a source issue? E2 Guardian ever only used 300mb ish RAM now it's going past 2gb and using swap lol. However restarting doesn't completely clean the swap. It's gone from 7% swap to 3%. If I leave the problem to develop it'll end up eating all the swap.
-
Squis was doing same thing. There is a contribution script that restarts it on 95% memory usage. With minor changes, it can be applied to e2guardian.
https://forum.pfsense.org/index.php?topic=126309.msg727239#msg727239
-
Squis was doing same thing. There is a contribution script that restarts it on 95% memory usage. With minor changes, it can be applied to e2guardian.
Shouldn't the issue be fixed instead? Especially if there is a memory leak, instead of finding workarounds?
Could you report it on Github instead? I'm currently on my phone. XD
Thanks Bud
-
I'm currently on my phone. XD
Me too.
I'll check my boxes. I have one stable at 2g on previous binaries. Will how it goes with 4.1.2
-
I'm currently on my phone. XD
Me too.
I'll check my boxes. I have one stable at 2g on previous binaries. Will how it goes with 4.1.2
Don't update for now, I guess until this is solved. Eventually I guess it'll cause the system to crash.
How many users does it have with 2gb RAM usage? With 15 or so devices at home usually I have around 300mb usage, now it's going well over 4gb. If you can't report it then I'll have to tomorrow, I have to edit my pull request anyways to get some fixes added to V5. I've been slightly busy recently.
By the way, what kind of organisation are you running your E2 Guardian box in? Is it a school? Have you realised over blocking? I pushed out some commits to disable alpha stage phrase lists.
-
ofcourse it a complain when you purchase something without manual and able to break it doing it and going over again.
its like you burn down your house because it does not say that the device will explode above 110 voltage. and your happy burning down your house then build it to burn again. lol
-
ofcourse it a complain when you purchase something without manual and able to break it doing it and going over again.
its like you burn down your house because it does not say that the device will explode above 110 voltage. and your happy burning down your house then build it to burn again. lol
First of all, you didn't pay for E2 Guardian.
Second of all, stop using those examples, it really doesn't work. Are you trying to say that you need a manual for everything to learn how it works? Like I said, if you want something that works and works really well, check out Smoothwall. It's a commercial product that works similar to this but nearly all the work has been taken out. That will be something you purchase and it comes with a manual and support. I'm not even trying to be rude to you here, I'm being serious.
However, if you decide to continue to use E2 Guardian, take 3 deep breaths. And explain the issue the best you can with some logs ideally. (Please don't tell me you need a manual for that too.)
-
Hi Marcello,
I reported the issue to E2 Guardian devs : https://github.com/e2guardian/e2guardian/issues/266
Could you please provide your input as you made the package and know exactly what changed since the last update?
Thanks
-
Hi Marcello,
I reported the issue to E2 Guardian devs : https://github.com/e2guardian/e2guardian/issues/266
Could you please provide your input as you made the package and know exactly what changed since the last update?
Thanks
I'm trying to reproduce de issue first on my boxes. try to include on git issue a screenshot of top showing e2guardian memory usage.
-
That issue caused my pfsense box to restart (after nearly a week) … Don't you get this issue Marcelloc?
-
That issue caused my pfsense box to restart (after nearly a week) … Don't you get this issue Marcelloc?
I'm really busy these days on my main job. I'll test it since I have some time.
Don't you think it's better to restart the process every two days to avoid these memory's problems until a new binary version?
-
That issue caused my pfsense box to restart (after nearly a week) … Don't you get this issue Marcelloc?
I'm really busy these days on my main job. I'll test it since I have some time.
Don't you think it's better to restart the process every two days to avoid these memory's problems until a new binary version?
Yes I do, but it may also be a log rotation issue. In some cases restarting the process doesn't give the allocated RAM back (from e2g). Clearing the logs seem to help quite significantly. Maybe you should try adding a access.log rotation every 24 hours until the issue is fixed?
It seems this is not even a BSD issue, as people on Ubuntu are also noticing high RAM usage.
Regarding work… I'm on the same boat. But this is annoying, whenever I am home I need to keep checking my pfSense, I absolutely hate logging in and seeing that it crashed...:/
-
I am also using the e2guardian and in a matter of hours the "memory ram" and swap are skyrocketing. I modified the script that marcelloc suggested in some posts above and when it restarts the service, for example 90% and 75% respectively, the values fall to 50% for memory and normalize the swap.
