Unofficial E2guardian package for pfSense
-
**Hello !
I need a little help with e2guardian5 install, when I tried to install it over "package manager" I got this error:**
Installing pfSense-pkg-E2guardian5…
Updating Unofficial repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: . done
Processing entries: .. done
Unofficial repository update completed. 14 packages processed.
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 3 package(s) will be affected (of 0 checked):New packages to be INSTALLED:
pfSense-pkg-E2guardian5: 0.5.0.1_4 [Unofficial]
e2guardian: 5.0.2 [Unofficial]
openssl: 1.0.2l,1 [Unofficial]Number of packages to be installed: 3
The process will require 14 MiB more space.
3 MiB to be downloaded.
[1/3] Fetching e2guardian-5.0.2.txz: …....... done
pkg-static: cached package e2guardian-5.0.2: size mismatch, fetching from remote
[2/3] Fetching e2guardian-5.0.2.txz: …....... done
pkg-static: cached package e2guardian-5.0.2: size mismatch, cannot continue
FailedThanks in advance
Bogdan -
Try again, I've pushed latest v5 version from e2g repository.
-
Thanks Marcello, now installation went OK.
Best Regards
Bogdan -
Try again, I've pushed latest v5 version from e2g repository.
Latest version is not being detected by pfSense for me. I haven't checked yet, but have you bumped the version?
-
I've updated the binaries but no changes on gui pkg.
An uninstall/install should update e2guardian to 5.0.2_1
-
I've updated the binaries but no changes on gui pkg.
An uninstall/install should update e2guardian to 5.0.2_1
Awesome, I've just gone ahead and updated it. How many HTTP workers do you use Marcello? I was initially using 1000 for home, but it seems it's not enough anymore lol. Sometimes all workers become busy and the internet becomes slow, so I've bumped the HTTP workers up to 2500.
-
does you update include this bug fixed
Fix forwarded_for not working - bug #370
https://github.com/e2guardian/e2guardian/commit/2d23affe316fcdf4aacb155a1858887d07ea88b8
-
does you update include this bug fixed
Fix forwarded_for not working - bug #370
https://github.com/e2guardian/e2guardian/commit/2d23affe316fcdf4aacb155a1858887d07ea88b8
Yes. Its the current v5 develop code.
-
I still getting some random E2 Guardian crashes here and there, its severely reducing performance. Sometimes. Anyone else having this issue?
I'm also using pfBlockerNG with this, not sure if it matters.
@Marcelloc why did you remove the E2 Guardian start log? It was pretty useful in situations like this.
-
@Marcelloc why did you remove the E2 Guardian start log? It was pretty useful in situations like this.
I didn't. It was removed by robotman3000.
-
@Marcelloc why did you remove the E2 Guardian start log? It was pretty useful in situations like this.
I didn't. It was removed by robotman3000.
Ah yes, you're right. He removed the entire watch dog code because it caused problems like switching on E2G when it was set to disabled.
However, have you got any ideas why my E2 Guardian could be randomly crashing? It seemed to start when I started experimenting with Traffic Shaper, but I really can't be sure without anything useful in logs. Have you checked to see if it has crashed in your production environment at all?
Other than the hiccup here and there, I've been loving v5. Transparent proxy is awesome, and seems to work well!
EDIT: Found this in the logs now: status_services.php: The command '/usr/local/etc/rc.d/e2guardian.sh stop' returned exit code '1', the output was 'kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 20480 -> 20480 e2guardian not running? (check /var/run/e2guardian.pid)
-
Apr 11 13:32:07 check_reload_status Reloading filter
Apr 11 13:34:17 kernel pid 24878 (e2guardian), uid 106: exited on signal 11
Apr 11 13:37:50 kernel pid 14342 (e2guardian), uid 106: exited on signal 11
Apr 11 13:37:55 kernel pid 90156 (e2guardian), uid 106: exited on signal 11
Apr 11 13:38:04 kernel pid 5340 (e2guardian), uid 106: exited on signal 11
Apr 11 13:38:20 kernel pid 54590 (e2guardian), uid 106: exited on signal 11
Apr 11 13:38:39 kernel pid 84677 (e2guardian), uid 106: exited on signal 11
Apr 11 13:38:46 kernel pid 14612 (e2guardian), uid 106: exited on signal 11
Apr 11 13:39:07 kernel pid 36090 (e2guardian), uid 106: exited on signal 11
Apr 11 13:39:13 e2guardian 92621 I seem to be running already!
Apr 11 13:39:13 root /usr/local/etc/rc.d/e2guardian.sh: WARNING: failed to start e2guardian
Apr 11 13:44:19 kernel pid 95365 (e2guardian), uid 106: exited on signal 11Really unsure how to go about debugging this mess.. But eventually the watchdog wins the battle agains the E2Guardian crashing.
-
Are you using any authentication?
-
Are you using any authentication?
I'm just using IP Authentication, I tried DNS before but that would give me a seg fault instantly. So I'm sticking to IP for the moment.
-
Are you using any authentication?
I'm just using IP Authentication, I tried DNS before but that would give me a seg fault instantly. So I'm sticking to IP for the moment.
No suggestions Marcello? I've got the watch dog running so it does restart E2 Guardian but sometimes it's just a mess. And will crash 5-8x in a row reducing performance and causing disruption.
-
No suggestions Marcello? I've got the watch dog running so it does restart E2 Guardian but sometimes it's just a mess. And will crash 5-8x in a row reducing performance and causing disruption.
May be related to https://github.com/e2guardian/e2guardian/issues/375.
I'll compile a version with debug and include some instructions on how to use, so you can see if it's something already related or not.
-
No suggestions Marcello? I've got the watch dog running so it does restart E2 Guardian but sometimes it's just a mess. And will crash 5-8x in a row reducing performance and causing disruption.
May be related to https://github.com/e2guardian/e2guardian/issues/375.
I'll compile a version with debug and include some instructions on how to use, so you can see if it's something already related or not.
I just re-did my config as this was bothering me and other users a lot. It seems to be better, but I'll continue to monitor it. It's possible it could've been a config issue and without a meaningful error message it's hard to tell where the problem lies.
-
I just re-did my config as this was bothering me and other users a lot. It seems to be better, but I'll continue to monitor it. It's possible it could've been a config issue and without a meaningful error message it's hard to tell where the problem lies.
I've pushed a 5.0.2_3 binaries with some fixes from e2guardian team. check if you're on this latest binaries with pkg info under console.
-
pkg v 5.0.3 is out. Main changes on this version:
-
Apply firewall limiters to direct connect clients (wpad or proxy manual config).
-
New button to clear cert MITM cache data.(useful when you change MITM CA)
-
-
pkg v 5.0.3 is out. Main changes on this version:
-
Apply firewall limiters to direct connect clients (wpad or proxy manual config).
-
New button to clear cert MITM cache data.(useful when you change MITM CA)
Unfortunately re-doing the configs didn't fix the crashing issue. I've just upgraded to the latest 5.0.3 version, and checked with pkg info. I'll see if this fixes it, thanks!
Also, could we apply the limiter to specific groups?
-
