Unofficial E2guardian package for pfSense

kenrutt

@la6er
It seems when making changes to an IP in a group. I need to stop E2G and restart under Status\Services. I have very little trouble with E2G stopping on me. In fact I do not even enable the watchdog feature. It just runs. It does take some tweeking when first setting up E2G. Make sure to go through the various lists and turn off or delete entries that reference any file that does not exist. I found it very helpful to SSH into router with WinSCP and modify some config files directly.

drmwndr

Hi all,
I'm using E2Guardian 5 from Unofficial Repository, not as transparent proxy and I'm getting some "The site requested does not exist" for simple local websites.
All filters were disabled, for tests.
Log error shows "2021.07.05 08:21:04 192.168.0.2 http://portal.mydomain.local 403 192.168.0.2 Default NETERROR Exceção do sítio confere. (Site on Exception list)"

The local site is working when accessed by Squid, or directly, does someone here have some idea of how to fix it? I was wondering if the problem is something DNS related but I can't find a way of how to force DNS servers on E2Guardian and taking a look at DNS logs, everything appears to be Ok.

Can someone help?

Thanks in advance.

pfsensation

@drmwndr said in Unofficial E2guardian package for pfSense:

Hi all,
I'm using E2Guardian 5 from Unofficial Repository, not as transparent proxy and I'm getting some "The site requested does not exist" for simple local websites.
All filters were disabled, for tests.
Log error shows "2021.07.05 08:21:04 192.168.0.2 http://portal.mydomain.local 403 192.168.0.2 Default NETERROR Exceção do sítio confere. (Site on Exception list)"

The local site is working when accessed by Squid, or directly, does someone here have some idea of how to fix it? I was wondering if the problem is something DNS related but I can't find a way of how to force DNS servers on E2Guardian and taking a look at DNS logs, everything appears to be Ok.

Can someone help?

Thanks in advance.

Definitely something to do with your DNS setup, are you using DNS resolver? I've got internal sites too and haven't run into any issues although I'm no longer using squid.

drmwndr

@pfsensation said in Unofficial E2guardian package for pfSense:

Definitely something to do with your DNS setup, are you using DNS resolver? I've got internal sites too and haven't run into any issues although I'm no longer using squid.

Hi @pfsensation. I have Bind installed on my pfsense box as DNS Server. I also have a NAT and a Firewall Rule redirecting all LAN1 Interface Traffic to port 53 to my pfSense box.
Is it necessary to enable and set pfSense DNS Resolver? Looks like e2guardian is bypassing this rule and looking directly on outside DNSs.

pfsensation

@drmwndr said in Unofficial E2guardian package for pfSense:

@pfsensation said in Unofficial E2guardian package for pfSense:

Definitely something to do with your DNS setup, are you using DNS resolver? I've got internal sites too and haven't run into any issues although I'm no longer using squid.

Hi @pfsensation. I have Bind installed on my pfsense box as DNS Server. I also have a NAT and a Firewall Rule redirecting all LAN1 Interface Traffic to port 53 to my pfSense box.
Is it necessary to enable and set pfSense DNS Resolver? Looks like e2guardian is bypassing this rule and looking directly on outside DNSs.

Unfortunately I don't use BIND either, but when you run nslookup on the client device, can it resolve your internal domains? Another gotcha is DNS over HTTPS/TLS, make sure that's disabled in the browser and lock down port 853 from LAN1.

drmwndr

@pfsensation said in Unofficial E2guardian package for pfSense:

@drmwndr said in Unofficial E2guardian package for pfSense:

@pfsensation said in Unofficial E2guardian package for pfSense:

Definitely something to do with your DNS setup, are you using DNS resolver? I've got internal sites too and haven't run into any issues although I'm no longer using squid.

Hi @pfsensation. I have Bind installed on my pfsense box as DNS Server. I also have a NAT and a Firewall Rule redirecting all LAN1 Interface Traffic to port 53 to my pfSense box.
Is it necessary to enable and set pfSense DNS Resolver? Looks like e2guardian is bypassing this rule and looking directly on outside DNSs.

Unfortunately I don't use BIND either, but when you run nslookup on the client device, can it resolve your internal domains? Another gotcha is DNS over HTTPS/TLS, make sure that's disabled in the browser and lock down port 853 from LAN1.

Yep, at client device it look up locally, but on pfSense box, it goes directly to External DNS.
Will take a better look at DNS Setup.

Thank you so much!

aGeekhere

With 2.5.2-RELEASE the 25_unofficial_packages_list.patch has issues
See
https://github.com/marcelloc/Unofficial-pfSense-packages/issues/94

aGeekhere

Update, even though the System Patches test shows a warning you can still apply it.

LilMonkey305

cant install on 2.5.2 ce. repo file wont load new packages with patch applied.

periko

Hello.

This is new for me, does e2guardian can work alone or need squid to work?

I had read that is a excellent replacement for SG.

But what is the advantage or disadvantage alone or with in conjunction with squid?

Thanks for your help.

kenrutt

Yes it can work alone. Does not need squid.

@marcelloc thanks

aGeekhere

Anyone else having issue with E2guardian and Rocket League? I am having difficulties trying to bypass the proxy for the Rocket League servers (as the servers do not connect by going through the proxy).
I have tried bypassing the following source address with out any luck
account-public-service-prod03.ol.epicgames.com
datarouter.ol.epicgames.com
global.koala.epicgames.com

I also get the following when I try and connect.
https://127.0.0.1

I have been using the E2guardian Monitor to see which servers it is trying to connect to however even though I have allowed all servers I still cannot connect and get a lot of https://127.0.0.1

Anyone else have this issue?

pfsensation

@ageekhere said in Unofficial E2guardian package for pfSense:

Anyone else having issue with E2guardian and Rocket League? I am having difficulties trying to bypass the proxy for the Rocket League servers (as the servers do not connect by going through the proxy).
I have tried bypassing the following source address with out any luck
account-public-service-prod03.ol.epicgames.com
datarouter.ol.epicgames.com
global.koala.epicgames.com

I also get the following when I try and connect.
https://127.0.0.1

I have been using the E2guardian Monitor to see which servers it is trying to connect to however even though I have allowed all servers I still cannot connect and get a lot of https://127.0.0.1

Anyone else have this issue?

Have you had a look at the logs? What I'd personally do is create an alias called E2G_DST_Bypass, put all those domains in there then in E2 Guardian configure that alias to bypass the transparent rule. This will bypass E2G completely for those domains.

aGeekhere

@pfsensation Yes this is what I do as well, however even bypassing the domains that show in E2guardian Monitor I am still not able to connect.

The logs show a lot of
https://127.0.0.1 0 - Default -
When starting Rocket League.

pfsensation

@ageekhere said in Unofficial E2guardian package for pfSense:

@pfsensation Yes this is what I do as well, however even bypassing the domains that show in E2guardian Monitor I am still not able to connect.

The logs show a lot of
https://127.0.0.1 0 - Default -
When starting Rocket League.

If you've done the bypass as I mentioned in the previous post, those domains won't even show up in E2 Guardian logs. Just to be clear, I'm talking about the bypass in transparent proxy located here: e2guardian > daemon > 'bypass proxy for these destination IPs'. Put your alias in there and it should bypass the proxy altogether.

aGeekhere

@pfsensation Yes this is correct, the bypass domains no longer show in E2 Guardian logs, however I still get the connection issue and a lot of https://127.0.0.1 0 - Default -

This is the first game I have come across where the normal bypass does not seems to be working correctly.

I guess the best way to see the issue is to install Rocket League and see if you have the same issue.

This game must be very picky about going through a proxy (if I fully bypass the proxy for the pc then I am able to connect).

periko

Hello marcelloc or other e2guardian users, does e2guardian is already support for pfsense 2.5.2?
Regards!!!

pfsensation

@periko said in Unofficial E2guardian package for pfSense:

Hello marcelloc or other e2guardian users, does e2guardian is already support for pfsense 2.5.2?
Regards!!!

I've been using it on 2.5.2 for months now, no issues.

Woundeddog

This post is deleted!