Unofficial E2guardian package for pfSense

pfsensation

@pfsensation:

I'm getting NGINX errors, E2G seems to be forwarding the traffic to the NGINX server rather that directly to pfBlocker.

Does pfblockerNG package started redirecting or showing error pages on latest versions? The pfblocker versions I've used was just a deny rules creator, with any redirect.

Nope, this was an ongoing problem since I enabled transparent proxy. pfBlocker has an option for blocking hosts - I have adblocking hosts files. The way it works is, it redirects those domains to pfBlocker's own internal web server in order to block them. They are getting intercepted by the proxy.

EDIT:

I have made a discovery Marcello. On normal non-debug E2Guardian which is setup with Squid. If Squid restarts, or needs to log rotate etc, it crashes E2Guardian. This doesn't seem to be the case with the debug version of E2Guardian, I have tried to replicate the issue but have been unsuccessful. Have you got any ideas?

pfsensation

@marcelloc:

@pfsensation:

did you try clearing the cache?

Yes. After cleaning and restarting, few sites goes fine then all get mac error.

Weird, I haven't got it yet. What authentication method are you using?

marcelloc

@pfsensation:

Weird, I haven't got it yet. What authentication method are you using?

IP address

pfsensation

@marcelloc:

@pfsensation:

Weird, I haven't got it yet. What authentication method are you using?

IP address

Strange, no issues like the one you're describing on my end yet… Only issue I have is that when using it with Squid, from time to time E2Guardian crashes. And somehow... It doesn't crash when debug is enabled.

I'm also hoping you can help me out with the pfBlocker issue, am I doing something wrong?

pfsensation

Hi Marcello,

I just managed to re-produce the Mac Alert you've been getting by enabling SSL re-write and header re-write. I wonder if it is related to this: https://github.com/e2guardian/e2guardian/commit/c389e53b189e0d38108aca210dc217cb940bfec7

marcelloc

@pfsensation:

Hi Marcello,

I just managed to re-produce the Mac Alert you've been getting by enabling SSL re-write and header re-write. I wonder if it is related to this: https://github.com/e2guardian/e2guardian/commit/c389e53b189e0d38108aca210dc217cb940bfec7

I have this enabled too. Thanks for the test and report .

If you have time, do the same test with version 5.0.2_3

pfsensation

@marcelloc:

@pfsensation:

Hi Marcello,

I just managed to re-produce the Mac Alert you've been getting by enabling SSL re-write and header re-write. I wonder if it is related to this: https://github.com/e2guardian/e2guardian/commit/c389e53b189e0d38108aca210dc217cb940bfec7

I have this enabled too. Thanks for the test and report .

If you have time, do the same test with version 5.0.2_3

Have you got a compiled binary for it? I'll give it a shot for you, by the way I tested in both Chrome and Firefox. Both had the Mac error, where as IE complained about TLS. It does sound like a OpenSSL issue maybe but I am by no means an expert on E2Guardian's inner workings.

marcelloc

Yes, that debug version
pkg add -f https://e-sac.websiteseguro.com/e2g/e2guardian-5.0.2_3.txz

pfsensation

@marcelloc:

Yes, that debug version
pkg add -f https://e-sac.websiteseguro.com/e2g/e2guardian-5.0.2_3.txz

On 5.0.2_3 SSL Re-write works and no Mac Alert issue. I think it might be that dependency, causing issues.

marcelloc

I've pushed a comiled package with code until commit bc7890a.

Seems to be working without latest patches for ssl on http1.1

version on repo:
e2guardian-5.0.2_7.txz

pfsensation

@marcelloc:

I've pushed a comiled package with code until commit bc7890a.

Seems to be working without latest patches for ssl on http1.1

version on repo:
e2guardian-5.0.2_7.txz

I knew that would be the issue!!! Great work! Now to find out why the new OpenSSL is giving this rather odd problem.