Unofficial E2guardian package for pfSense

[ravegen]

@pfsensation, @marcelloc

attached is the error log.

I have provided that screenshot, months before.

System resource usage is fine, load average 0.14, 0.10, 0.04, cpu & swap usage is 0%, memorage usage is 28%.

I am able to ssh to my box.

Like I said, the content scanner (clamdscan) was perfectly running before the rotate log fix was created and updated to the package.

Respectfully, I think it does not matter if the content scanner is a feature for you or for Marcelloc but rather for the use of the community since it is a feature placed in the package. Such content scanner should have been already removed if it is that useless.

What I am saying is the content scanner was broken since their was a fix on rotate log. Perhaps, the developers who modified the package can differential what changes they have done before and after the rotate log fix and made changes accordingly.

[pfsensation]

@ravegen said in Unofficial E2guardian package for pfSense:

@pfsensation, @marcelloc

attached is the error log.

I have provided that screenshot, months before.

System resource usage is fine, load average 0.14, 0.10, 0.04, cpu & swap usage is 0%, memorage usage is 28%.

I am able to ssh to my box.

Like I said, the content scanner (clamdscan) was perfectly running before the rotate log fix was created and updated to the package.

Respectfully, I think it does not matter if the content scanner is a feature for you or for Marcelloc but rather for the use of the community since it is a feature placed in the package. Such content scanner should have been already removed if it is that useless.

What I am saying is the content scanner was broken since their was a fix on rotate log. Perhaps, the developers who modified the package can differential what changes they have done before and after the rotate log fix and made changes accordingly.

OK, those errors look config related. I'll have a chat with @marcelloc and then we'll see if we can send out another patch for it. Comparing the last build to your current, there doesn't seem to be any specific changes that would effect the content scanner.

[Sei Pine]

i switched to sarg to log e2guardian. lightsquid is totally not working after few hours.

[pfsensation]

@sei-pine said in Unofficial E2guardian package for pfSense:

i switched to sarg to log e2guardian. lightsquid is totally not working after few hours.

How long have you set E2 Guardian to keep logs for? And how often are you log rotating? I've not come across this issue so it maybe a config issue.

[Sei Pine]

@pfsensation i leave all lightsquid settings as default (should be fine i guess) but when i try to configure squid and turn off its transparent proxy and mitm (this is interfering with e2guardian so...) lightsquid doesn't log anything.

i dunno, maybe i need to make lightsquid listen to e2guardian ? anyways, i set my e2guardian to keep 20 log files.

[binkec]

@pfsensation
Hi, I was busy past two weeks and I tried to install 2.4.4 again and I can see real time traffic. E2g is working except "weighted phrases". I went trough working configuration(2.4.3) and non working(2.4.4) and I couldn't see any difference.
The only difference is in log,
2.4.4 I have this error:
Nov 25 20:47:12 e2guardian 97044 I seem to be running already!
Nov 25 20:54:23 e2guardian 75338 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 20:54:23 e2guardian 75338 listen0_proxy: 1: Error 53 on accept: errorcount 1
Nov 25 20:57:44 e2guardian 75338 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 21:00:13 e2guardian 15579 I seem to be running already!
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 1
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 2
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 3
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 21:14:32 e2guardian 62358 I seem to be running already!
Nov 25 21:17:16 e2guardian 3849 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 21:17:36 e2guardian 3849 listen0_proxy: 1: Error 53 on accept: errorcount 0

In working 2.4.3 system there is no error.
Regards

[ravegen]

@pfsensation ,

Is there a progress on the content scanner fix ?

[pfsensation]

@ravegen said in Unofficial E2guardian package for pfSense:

@pfsensation ,

Is there a progress on the content scanner fix ?

I've already asked @marcelloc to have a look into it. He believes it could be an ICAP issue, I'm not sure if he's had a chance yet to try implement a fix.

[pfsensation]

@sei-pine said in Unofficial E2guardian package for pfSense:

@pfsensation i leave all lightsquid settings as default (should be fine i guess) but when i try to configure squid and turn off its transparent proxy and mitm (this is interfering with e2guardian so...) lightsquid doesn't log anything.

i dunno, maybe i need to make lightsquid listen to e2guardian ? anyways, i set my e2guardian to keep 20 log files.

You shouldn't have transparent proxy on Squid anyways. Set E2 Guardian log format to Squid and make sure you install the custom Inc file so that light squid listens to E2 Guardian. It's higher up in this thread.

[pfsensation]

@binkec said in Unofficial E2guardian package for pfSense:

@pfsensation
Hi, I was busy past two weeks and I tried to install 2.4.4 again and I can see real time traffic. E2g is working except "weighted phrases". I went trough working configuration(2.4.3) and non working(2.4.4) and I couldn't see any difference.
The only difference is in log,
2.4.4 I have this error:
Nov 25 20:47:12 e2guardian 97044 I seem to be running already!
Nov 25 20:54:23 e2guardian 75338 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 20:54:23 e2guardian 75338 listen0_proxy: 1: Error 53 on accept: errorcount 1
Nov 25 20:57:44 e2guardian 75338 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 21:00:13 e2guardian 15579 I seem to be running already!
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 1
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 2
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 3
Nov 25 21:04:37 e2guardian 20124 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 21:14:32 e2guardian 62358 I seem to be running already!
Nov 25 21:17:16 e2guardian 3849 listen0_proxy: 1: Error 53 on accept: errorcount 0
Nov 25 21:17:36 e2guardian 3849 listen0_proxy: 1: Error 53 on accept: errorcount 0

In working 2.4.3 system there is no error.
Regards

Which ports are you running E2 Guardian on? Are you using other packages like pfblockerng?

[binkec]

@pfsensation
Hi
I am using default port 8080 in direct connect widhout squid, no transparent mode and fresh install, only E2g and sarg on VMWARE. Like I sad I vent trough working config step by step several times and I didn't find any difference, it should be something in E2g.

Regards

[pfsensation]

@binkec said in Unofficial E2guardian package for pfSense:

@pfsensation
Hi
I am using default port 8080 in direct connect widhout squid, no transparent mode and fresh install, only E2g and sarg on VMWARE. Like I sad I vent trough working config step by step several times and I didn't find any difference, it should be something in E2g.

Regards

Which interfaces are you listening on? Make sure it's set to LAN and localhost. I run my system in VMWare ESXi without any issues.

[binkec]

@pfsensation
Hi
I have set to both, are you using "phase list" filtering.

[pfsensation]

@binkec said in Unofficial E2guardian package for pfSense:

@pfsensation
Hi
I have set to both, are you using "phase list" filtering.

Of course, I use black list and phrase list. Phrase based filtering is actually one of the core functions of E2 Guardian and what makes it vastly better than other systems like SquidGuard. I'm on 2.4.4 and haven't had those issues and doesn't look like anyone else has either. So I'd be interested to know why it would happen.

Are you running just vmware work station or ESXi?

Edit: put the HTTP workers up, I have mine at 3072.

[plusbil]

System working but e2guard access.log not working. I did port 8081, 8082; result same. Why?

[pfsensation]

@plusbil said in Unofficial E2guardian package for pfSense:

System working but e2guard access.log not working. I did port 8081, 8082; result same. Why?

Can you check var/log/e2guardian/access.log and see if it's updating there?

[plusbil]

Not update. New access.log zero byte. But when I restard pfsense system, e2guard log working.

[plusbil]

And 3-4 days later again stop.

[Sei Pine]

so far so good, the only problem i encounter is each day when sarg stops logging, i need to change time format to American or European then force refresh for sarg to continue logging. its a little hassle but still it works.

btw, till now i still can't figure out how to use the Users tab on E2Guardian or do i need to use LDAP?, need help with this one thanks.

what I've tried so far is to use PFSENSE\(Group name)
(Group Name)\(Account Name)
PFSENSE\(Group Name)\(Account Name)

^ Doesn't work

[pfsensation]

@plusbil said in Unofficial E2guardian package for pfSense:

Not update. New access.log zero byte. But when I restard pfsense system, e2guard log working.

Clear the logs file manually, restart E2 Guardian and let me know what you've got your log rotate settings set as. It's been brilliant for me and working without any issues.