Unofficial E2guardian package for pfSense
-
Pfsensation:
Where do you set the exclusions? At exceptionsitelist?
Have you tried using Logmein through the proxy? -
another thing, how do you disallow using ip address in the browser like done in squid.
-
Pfsensation:
Where do you set the exclusions? At exceptionsitelist?
Have you tried using Logmein through the proxy?Yeah, its under the sites list tab under exceptions. That's where you can throw in all the domain names. It's paramount we start creating a small list of exceptions. I don't want E2Guardian to become something which causes more problems down the line than benefits.
what about the wpad you mentioned that is part of e2guardian package. where can i find it?
If you've installed the unofficial repository, via the instructions in the OP. Just go to the package manager and search for it.
another thing, how do you disallow using ip address in the browser like done in squid.
I'm not 100% sure but I believe that it maybe blocked by default. I just tried going to "http://8.8.8.8" and it gave me a 504 gateway timeout instead. I don't even see how using the IP would make a different when you use E2Guardian. E2Guardian is designed in a way in which it can scan websites on the fly, whether you connect to them via IP or domain. This is the biggest reasons why I recommend it over any other kind of filtering system, because it doesn't just rely on the website link, it can scan the contents of the page too!
-
Ah nope. It should not block by default browsing by ip address because some programs here in us uses ip address, therefore, i should be able to allow it or disable it.
The OP gave two ways to install, thru package and installing using commandline, which one is it.
-
Pfsensation
Have you used logmein behind the e2g using mitm?
-
Pfsensation
Have you used logmein behind the e2g using mitm?
Nope, however I have used TeamViewer etc, no issues. If you have problems with logmein, just add it to the exceptions.
@Marcelloc, which one is the correct E2Guardian config that we use now? I see a tonne of them in "/usr/local/etc/e2guardian"
I'm asking because FredB, over at GitHub recons that the blacklist categories not showing maybe due to not having the following :
# List categorisation #listcategory: "Banned Sites"Check it here: https://github.com/e2guardian/e2guardian/issues/244
-
Pfsensation
Have you used logmein behind the e2g using mitm?
Nope, however I have used TeamViewer etc, no issues. If you have problems with logmein, just add it to the exceptions.
Next week I am going to test with version 4. With v3 I add it to the exceptions but Logmein did not work. Teamviewer did worked. It seems some apps are more strict with MITM.
-
@Marcelloc, which one is the correct E2Guardian config that we use now? I see a tonne of them in "/usr/local/etc/e2guardian"
All of them. E2guardian.conf is the main conf and there is a fx.conf for each group conf
-
It seems some apps are more strict with MITM.
Sure they are. Some like skype are not http.
-
Pfsensation
Have you used logmein behind the e2g using mitm?
Nope, however I have used TeamViewer etc, no issues. If you have problems with logmein, just add it to the exceptions.
Next week I am going to test with version 4. With v3 I add it to the exceptions but Logmein did not work. Teamviewer did worked. It seems some apps are more strict with MITM.
Use pfSense packet capture under diagnostics in order to log where the traffic is trying to connect to, then use that info in order to add exceptions to it being MITM'd.
It seems some apps are more strict with MITM.
Sure they are. Some like skype are not http.
Could you test out getting the blocked categories to work with ShallaList? Based on what Fred suggested on GitHub.
-
Use pfSense packet capture under diagnostics in order to log where the traffic is trying to connect to, then use that info in order to add exceptions to it being MITM'd.
That is an idea.
What I do is set the Device to connect directly to Squid instead of going through E2g, then I look the Real Time log of Squid to see the sites that are needed by the connection. Then I can add those sites to the E2g exceptions, and return the Device to the normal connection through E2g.
But Logmein is really strict with MITM and for some reason adding the sites to the exceptions on v3 was not enough. The sites are connected but then are dropped. It seems that having the sites in the exceptionsitelist still are processed for MITM then the sites get the forged SSL certificate which the App does not like.
If I could find a way to say to the E2g to use MITM by default on most sites and not use it for some specific sites then those strict sites or Apps will not break.
-
If I could find a way to say to the E2g to use MITM by default on most sites and not use it for some specific sites then those strict sites or Apps will not break.
Did you tried to add this site on exceptionsitelist?
-
I'm asking because FredB, over at GitHub recons that the blacklist categories not showing maybe due to not having the following :
# List categorisation #listcategory: "Banned Sites"Check it here: https://github.com/e2guardian/e2guardian/issues/244
try pkg 0.4.1.2
https://github.com/marcelloc/Unofficial-pfSense-packages/commit/113159cbac10e68568b77b8a0a22c65fdf4607ec
-
pkg 0.4.2 is almost done too with realtime tab.
-
If I could find a way to say to the E2g to use MITM by default on most sites and not use it for some specific sites then those strict sites or Apps will not break.
Did you tried to add this site on exceptionsitelist?
Yes I tried on v3 but still did not work.
-
pkg 0.4.2 is almost done too with realtime tab.
The squidanalyser, provide the information like that?
SARG could do it except the reason.
-
pkg 0.4.2 is almost done too with realtime tab.
The log is showing the data from access.log?
In what format? Dans format os squid format or squid extended format or other? -
The log is showing the data from access.log?
yes. original e2guardian format. If you want to see or grep the log, it's in /var/log/e2guardian/access.log
-
-
The log is showing the data from access.log?
yes. original e2guardian format. If you want to see or grep the log, it's in /var/log/e2guardian/access.log
This can represent a problem. If the access.log file has to be in e2g format, then squidanalyser and SARG can not use it.
So using the real time gui will bring conflict with permanent reports.
