Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Unofficial E2guardian package for pfSense

    Scheduled Pinned Locked Moved
    Cache/Proxy
    70
    1.2k
    1.2m
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      amorimpermissus @La6er
      last edited by

      @La6er how are you configuring them? Are you adding them in exactly how you typed?

      If so, you need to change the way you've added them. There should be just one IP or subnet per line, but you can't do a 'range' typed in the way you did. So if you wanted those 6 IPs only, the simplest way would be to do one per line, like this:

      10.16.0.10
      10.16.0.11
      10.16.0.12
      10.16.0.13
      10.16.0.14
      10.16.0.15

      If you already added them this way and it's still not working, you should also check under:
      General -> Auth plugins, and ensure that "Ip Address" is selected.

      1 Reply Last reply Reply Quote 0
      • A
        amorimpermissus @amorimpermissus
        last edited by

        @amorimpermissus To anyone having this issue as I did, I solved my own problem (yay!). I determined the cause was in the "Groups" settings tab. Even though I had Transparent Proxy and SSL support enabled under the Daemon section, I didn't have MITM properly enabled for the ACL group.

        By going to Groups -> <name of the ACL group> -> Group Options, I ensured these were selected:
        "Scan clean cache"
        "Hex decode content" (this shouldn't be necessary, but I have it enabled anyway)
        "Infection/Scan Error Bypass on Scan Errors Only"
        "Filter SSL sites forging SSL certificates" (previously not selected)
        "Auto-switch to MITM to deliver block page"

        After this, I needed to simply install the CA cert in the proper locations on my client machines, and all phrase filtering and greylisting worked as designed.

        1 Reply Last reply Reply Quote 0
        • J
          jok
          last edited by

          Hello. Thanks for this fork.
          I want to configure e2guardian with antivirus scanning functionality, but I don't know how to do it without installing squid and enable squid antivirus. If I don't do this, I have not clamav daemon and e2guardian give me error of connection to clamv daemon.
          There are the possibility to install clamd service without installing squid?
          Thanks a lot

          1 Reply Last reply Reply Quote 0
          • K
            kenrutt
            last edited by

            Does anyone use the bypass feature in E2guardian? It does not seem to work for me. What am I doing wrong?

            P 1 Reply Last reply Reply Quote 0
            • P
              pfsensation @kenrutt
              last edited by

              @kenrutt said in Unofficial E2guardian package for pfSense:

              Does anyone use the bypass feature in E2guardian? It does not seem to work for me. What am I doing wrong?

              I use both source and destination bypass. All work perfectly fine for me. I'm using it through Alias to keep things clean.

              1 Reply Last reply Reply Quote 0
              • K
                kenrutt
                last edited by

                @pfsensation said in Unofficial E2guardian package for pfSense:

                I use both source and destination bypass. All work perfectly fine for me. I'm using it through Alias to keep things clean.

                I guess I am not not sure how to use through Alias.

                1 Reply Last reply Reply Quote 0
                • K
                  kenrutt
                  last edited by

                  @pfsensation said in Unofficial E2guardian package for pfSense:

                  I use both source and destination bypass. All work perfectly fine for me. I'm using it through Alias to keep things clean.

                  Do are you talking about the bypass ip's? I was asking about the bypass on the block page when pressing the "Acknowledge".

                  P 1 Reply Last reply Reply Quote 1
                  • P
                    pfsensation @kenrutt
                    last edited by pfsensation

                    @kenrutt said in Unofficial E2guardian package for pfSense:

                    @pfsensation said in Unofficial E2guardian package for pfSense:

                    I use both source and destination bypass. All work perfectly fine for me. I'm using it through Alias to keep things clean.

                    Do are you talking about the bypass ip's? I was asking about the bypass on the block page when pressing the "Acknowledge".

                    Ohh, I was referring to the IP's bit. I couldn't get that working either and didn't have time to investigate. Naturally, forgot. :(

                    I did go as far as to debugging my own code on the block page and making sure that the "Acknowledge" does generate a bypass key. But the key doesn't appear to work when used. Strange. It will need more digging.

                    Definitely an issue with the back end bypass code.

                    1 Reply Last reply Reply Quote 0
                    • K
                      kenrutt
                      last edited by

                      @pfsensation said in Unofficial E2guardian package for pfSense:

                      Ohh, I was referring to the IP's bit. I couldn't get that working either and didn't have time to investigate. Naturally, forgot. :(
                      I did go as far as to debugging my own code on the block page and making sure that the "Acknowledge" does generate a bypass key. But the key doesn't appear to work when used. Strange. It will need more digging.
                      Definitely an issue with the back end bypass code.

                      Ok. Hey if you figure something out keep me posted.
                      Thanks a bunch.

                      1 Reply Last reply Reply Quote 0
                      • A
                        abhijitmore007
                        last edited by

                        How to configure mitm with pfsense please help me

                        K 1 Reply Last reply Reply Quote 0
                        • K
                          kenrutt @abhijitmore007
                          last edited by

                          @abhijitmore007 Under "Daemon" tab make sure "Check to enable E2guardian SSL interception" is checked and make sure Cert is selected. Then under the groups tab in group options select and highlight "Filter ssl sites forging SSL Certificates (off)".

                          A 3 Replies Last reply Reply Quote 0
                          • A
                            abhijitmore007
                            last edited by

                            Can you provide step by step configuration

                            1 Reply Last reply Reply Quote 0
                            • A
                              abhijitmore007 @kenrutt
                              last edited by

                              @kenrutt I am using pfsens 2.4.4 and squid with e2d for filtering but squid not integrated with e2d for ssl cert. there is no need of squid for ssl filtering

                              1 Reply Last reply Reply Quote 0
                              • H
                                heloplus
                                last edited by

                                I've updated the install code to use version 3.5.1 and ssl interception.
                                Motivational Quotes in Hindi

                                1 Reply Last reply Reply Quote 0
                                • A
                                  abhijitmore007 @kenrutt
                                  last edited by

                                  @kenrutt thank you problem resloved
                                  now https filter is working

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    abhijitmore007 @kenrutt
                                    last edited by

                                    @kenrutt some site get error
                                    3e27802d-5e7f-4ac2-92dc-2037bbd5a4c0-image.png

                                    J P 2 Replies Last reply Reply Quote 0
                                    • J
                                      jetberrocal @abhijitmore007
                                      last edited by

                                      @abhijitmore007
                                      The error maybe this site requires a secure connection. mitm is a man in the middle attack and will fail with such sites. Yo may need to create an exception rule with a list for those sites to not use mitm. You still can filter the sites but not filter/read the content.

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        pfsensation @abhijitmore007
                                        last edited by pfsensation

                                        @abhijitmore007 said in Unofficial E2guardian package for pfSense:

                                        @kenrutt some site get error
                                        3e27802d-5e7f-4ac2-92dc-2037bbd5a4c0-image.png

                                        I stopped using squid due to problems, try with direct mode without squid. I pretty much have no problems with any site via the browser. The apps I have issues with I have made exceptions for.

                                        K 1 Reply Last reply Reply Quote 0
                                        • K
                                          kenrutt @pfsensation
                                          last edited by

                                          @pfsensation My experience has been the same. With e2guardian in direct mode things work fairly well. Only a few things I needed to bypass.

                                          P 1 Reply Last reply Reply Quote 1
                                          • P
                                            pfsensation @kenrutt
                                            last edited by

                                            @kenrutt said in Unofficial E2guardian package for pfSense:

                                            @pfsensation My experience has been the same. With e2guardian in direct mode things work fairly well. Only a few things I needed to bypass.

                                            Yeah, I gave up trying to use Squid. The current implementation wasn't worth my time anyways, since HTTPS content that E2 Guardian decrypts and sees wasn't being added to Squid cache. Furthermore, I noticed a speed improvement when bypassing squid in the setup, the Squid in pfsense is an older version (although I think Marcelloc has a newer one in his repo).

                                            I also had other issues with Squid, such as not generating fake certs properly (when using the SSL intercept feature). The certs didn't have a Subject alternative name which caused a tonne of sites and stuff to fail.

                                            On top of that, nowadays browsers do a really good job of caching things locally. The benefits have become quite minimal, unless your bandwidth is completely trash and you have users visiting the same content over and over.

                                            If @marcelloc has a newer version of Squid, that doesn't have the certs issue and slow down issue. I may give it a shot when I have time. But so far I'm pretty content with E2 Guardian, I'm using it at home with no issues. Only thing missing is an updated word list and a good blacklist that's maintained well.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post