Unofficial E2guardian package for pfSense
-
Still crashes for me using the attached file. I took out the image too, and that didn't help. I'll have to revisit it later today or tomorrow.
-
Still crashes for me using the attached file. I took out the image too, and that didn't help. I'll have to revisit it later today or tomorrow.
I've been very busy today so I didn't get a chance to play around anymore. But if it really is to do with my block page causing the crash. Look at what is different from the official, namely, my block page shows client Group and Host name. Remove those and see if it crashes, if it doesn't that could be it. Something wrong with "-Filtergroup-" or "-Host-".
Edit: My page has a bypass link too. So it may be any of those tbh, bypass link creates a code. Judging by what Marcelloc was facing with illegal chars etc. That could somehow be related.
-
Not able to go on my pc right now but from my phone. I removed the code below.
#### Your details are below: _-USER- -HOST-_ _-FILTERGROUP-_ _-IP-_ [Acknowledge](-BYPASS-)It doesn't seem to be crashing anymore. I'll test a little more when possible. Not sure exactly which place holder is causing the issue, but it most likely maybe the filter group. Since the filter group doesn't show.
-
Not able to go on my pc right now but from my phone. I removed the code below.
#### Your details are below: _-USER- -HOST-_ _-FILTERGROUP-_ _-IP-_ [Acknowledge](-BYPASS-)It doesn't seem to be crashing anymore. I'll test a little more when possible. Not sure exactly which place holder is causing the issue, but it most likely maybe the filter group. Since the filter group doesn't show.
As I don't use bypass key, try just removing it from page. Maybe this is the difference from our config.
-
Also I identified why the apply button was not reloading completely the daemon. E2guardian has 3 ways to reload it without killing the process and the option I was using was the lightest one. Next gui version will have this fix.
If we can confirm that the -BYPASS- is crashing the daemon, I can open another ticket on e2guardian repo.
-
Its not -BYPASS- (it's working pretty good). So far I've found -FILTERGROUP- and -REASONLOGGED- will crash the daemon. And possibly the combo of using -USER- -HOST- -IP-.
-REASONGIVEN-, -CATEGORIES-, -USER- so far seem to working for me using the attach page with -BYPASS-.
I am using IP Address as my only Auth plugin if makes a difference.
-
Its not -BYPASS- (it's working pretty good). So far I've found -FILTERGROUP- and -REASONLOGGED- will crash the daemon. And possibly the combo of using -USER- -HOST- -IP-.
-REASONGIVEN-, -CATEGORIES-, -USER- so far seem to working for me using the attach page with -BYPASS-.
I am using IP Address as my only Auth plugin if makes a difference.
Confirmed! I can get -bypass- working fine without crashes, adding any of those place holders above causes E2Guardian to quit. xD
I am also using IP address as my only auth, just to confirm. This is a weird bug, because it did work for couple authenticated users, if they had certain IP's it seemed. But I really don't know for sure why it was behaving so weird before, but now we know those particular place holders are causing the crashes. This is just a heads up if you have trouble re-creating the crashes Marcello. Also try to use my exact same block page source code, with everything intact, including -bypass-.
-
Also try to use my exact same block page source code, with everything intact, including -bypass-.
That's the way I use, just included htl tags before and after.
I'll start testing the 720 hosts network tomorrow. I'll use your template changing the image and will test it with and without those problematic fields.
-
Also try to use my exact same block page source code, with everything intact, including -bypass-.
That's the way I use, just included htl tags before and after.
I'll start testing the 720 hosts network tomorrow. I'll use your template changing the image and will test it with and without those problematic fields.
Alrighty, let us know how it goes. Where will you test this by the way? In a business?
-
Alrighty, let us know how it goes. Where will you test this by the way? In a business?
Yes, on a network I'll help to migrate.
I've also pushed to 2.3 and 2.4 repo a 0.2 pkg version without tinyproxy(it has it's own pkg on Unofficial repo now) and with an apply action to daemon. This fixes the save apply restart issue.
About the http workers. With more then 4000 it aborts. It should accept 20k. I'll build a debug version to see if it's a big or a limitation with current 4.1.1 code and BSD.
-
Alrighty, let us know how it goes. Where will you test this by the way? In a business?
Yes, on a network I'll help to migrate.
I've also pushed to 2.3 and 2.4 repo a 0.2 pkg version without tinyproxy(it has it's own pkg on Unofficial repo now) and with an apply action to daemon. This fixes the save apply restart issue.
About the http workers. With more then 4000 it aborts. It should accept 20k. I'll build a debug version to see if it's a big or a limitation with current 4.1.1 code and BSD.
Just a heads up. Updating didn't remove Tiny Proxy automatically. I had to install Tiny Proxy from the repository and then uninstall to get it off my box.
Hmm the http workers issue could be a big issue in bigger environments. I'm lucky I'm not noticing any degradation at home yet.
-
Hmm the http workers issue could be a big issue in bigger environments. I'm lucky I'm not noticing any degradation at home yet.
yes. I'll have a chance to test it this week and try to identify what needs a fix.
-
I'll have a change to test it this week and try to identify what needs a fix.
'change' I've come to really dislike that word (and RFC, MOP, CAB) the past few months. Our entire Change/RFC process has changed at work and not for the better
-
I'll have a change to test it this week and try to identify what needs a fix.
'change' I've come to really dislike that word (and RFC, MOP, CAB) the past few months. Our entire Change/RFC process has changed at work and not for the better
Sorry, typo :) I'll have a chance test
-
;D I figured, I was just being funny
-
Hi Marcello,
I pkg delete c-icap, and that removed some other files.
I also deleted everything e2guardian and tinyproxy in /usr/local/pkg
However, in Status/Services, I still have both tinyproxy and e2guardian, as stopped. They are not listed in pkg info, they seem not to exist there.
As you wrote on page 3:
@Mr.:
tinyproxy and e2guardian both refuse to start.
As the pkg process failed on your box, there is no e2guardian or tinyproxy binaires installed.
That is probably the cause, so how can I now remove these 2 orphans from Status/Services?
Thank you :)
-
To remove tinyproxy, install it from Unofficial repo and then uninstall. The same with e2guardian.
The c-icap is a package from squid
-
Tiny Proxy that pesky thing seems to keep coming back even through I installed it from the repo again and uninstalled it. D:
Any news on the tests Marcello? Did you manage to reproduce the crashes using those filter group, and hostname place holders/tags ?
-
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(?)
-
@Mr.:
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(?)
Well the method described above stops Tiny Proxy from starting but it still appears in service status / dash board.
