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

    PfBlockerNG v2.0 w/DNSBL

    Scheduled Pinned Locked Moved
    pfBlockerNG
    192
    1.1k
    1.4m
    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.
    • P
      pfBasic Banned
      last edited by

      Still looking for some guidance on this topic? Policy Based Routing to a VPN Gateway results in no pfblockerNG filtering. How can I fix this?

      It looks like I got one thing working on my setup but killed DNSBL in the process.

      I recently setup policy based routing where my pass firewall rules determine the Gateway to be used. I did this so that I could have one interface route all traffic through my VPN client and another interface not utilize the VPN at all. That works great, but ever since I set that up I have 0 hits on all of my DNSBL feeds and ads are coming through.

      Any ideas on how I can use pfBlockerNG DNSBL while still utilizing policy based routing for my purposes?

      1 Reply Last reply Reply Quote 0
      • C
        chrcoluk
        last edited by

        quick update since my post is now out of date as to what is going on with my device.

        unbound was not crashing but it was the restarts for the dhcp renewals which I now stopped by patching services.inc, I did enable the DGA list again but as I said before the DGA list is not live domains but a domain list generated from discovered seeds of malware domain generators, of course the domains could be made live at any given moment so its a way to preemt them.

        pfSense CE 2.7.2

        1 Reply Last reply Reply Quote 0
        • P
          pfBasic Banned
          last edited by

          I've got everything back up and running again. pfblockerng w/ DNSBL, openvpn client & server.

          But now all of my DNS requests go through my ISP. Not really a big deal, but is it possible to make my requests go through google or openvpn dns instead?

          I have googe and opendns ip's listed under general setup, and under dhcp. but i keep getting ISP dns.

          1 Reply Last reply Reply Quote 0
          • RonpfSR
            RonpfS
            last edited by

            @pfBasic:

            I've got everything back up and running again. pfblockerng w/ DNSBL, openvpn client & server.

            But now all of my DNS requests go through my ISP. Not really a big deal, but is it possible to make my requests go through google or openvpn dns instead?

            I have googe and opendns ip's listed under general setup, and under dhcp. but i keep getting ISP dns.

            In order for DNSBL to block domain name, all clients DNS requests must use the pfSense DNS resolver. https://forum.pfsense.org/index.php?topic=102470.msg572527#msg572527

            Normally, in General setup : you leave the DNS servers fields empty, you disable Allow DNS server list to be overridden by DHCP/PPP on WAN
            in DHCP / Server you leave the DNS Servers fields empty.

            2.4.5-RELEASE-p1 (amd64)
            Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
            Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

            1 Reply Last reply Reply Quote 0
            • P
              pfBasic Banned
              last edited by

              So my understanding with that setup is that all clients will use the pfsense default (ISP) DNS that will be filtered by pfbng w/ dnsbl since we haven't specified anything else for it to use.

              Is there a way present or future (maybe some advanced settings entry?) that allows us to tell pfbng w/ dnsbl directly to use a specific DNS or list of DNS?

              It seems like that should work (not that I'd know) but I don't see why it is necessary that pfbng w/ dnsbl uses an ISP's DNS. If it can filter requests going through the ISP couldn't it do the same with any public DNS?

              1 Reply Last reply Reply Quote 0
              • RonpfSR
                RonpfS
                last edited by

                Read again https://forum.pfsense.org/index.php?topic=102470.msg572527#msg572527
                about forwarding mode.

                2.4.5-RELEASE-p1 (amd64)
                Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                1 Reply Last reply Reply Quote 0
                • P
                  pfBasic Banned
                  last edited by

                  Im not sure what im supposed to be picking up from that? No DNS forwarder? I've never used DNS Forwarder so I really dont know what is implied by that? It also says that you can use the DNS forwarding mode of DNS Resolver, but implies that if I use forwarding mode then i'll use my ISP's DNS, whereas if i leave it in resolver mode i'll use the root DNS (don't know what that is?).

                  Im using DNS resolver, not forwarder, and not using forwarding mode, but my queries are still going through my ISP DNS.

                  1 Reply Last reply Reply Quote 0
                  • RonpfSR
                    RonpfS
                    last edited by

                    @pfBasic:

                    So my understanding with that setup is that all clients will use the pfsense default (ISP) DNS that will be filtered by pfbng w/ dnsbl since we haven't specified anything else for it to use.

                    All clients will use the pfsense DNS resolver, that you can configure in forwarding mode to use your ISP DNS server, but by default, why not use the pfsense DNS Resolver in Root mode without having to rely on an external DNS server.

                    @pfBasic:

                    Is there a way present or future (maybe some advanced settings entry?) that allows us to tell pfbng w/ dnsbl directly to use a specific DNS or list of DNS?

                    That what pfSense DNS Resolver forwarding mode is for.

                    2.4.5-RELEASE-p1 (amd64)
                    Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                    Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                    1 Reply Last reply Reply Quote 0
                    • RonpfSR
                      RonpfS
                      last edited by

                      @pfBasic:

                      Im not sure what im supposed to be picking up from that? No DNS forwarder? I've never used DNS Forwarder so I really dont know what is implied by that? It also says that you can use the DNS forwarding mode of DNS Resolver, but implies that if I use forwarding mode then i'll use my ISP's DNS, whereas if i leave it in resolver mode i'll use the root DNS (don't know what that is?).

                      Im using DNS resolver, not forwarder, and not using forwarding mode, but my queries are still going through my ISP DNS.

                      Check the hosts DNS configuration to see what DNS server they use.

                      2.4.5-RELEASE-p1 (amd64)
                      Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                      Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                      1 Reply Last reply Reply Quote 0
                      • P
                        pfBasic Banned
                        last edited by

                        All clients will use the pfsense DNS resolver, that you can configure in forwarding mode to use your ISP DNS server, but by default, why not use the pfsense DNS Resolver in Root mode without having to rely on an external DNS server.

                        OK, awesome, thank-you. This is what I must be doing wrong. As far as I thought, I am using the DNS resolver (not using forwarded, forwarding mode not turned on, and I've removed all entries in general setup & dhcp for alternative DNS servers).
                        But whenever I run dnsleaktest.com, I still get my ISP's DNS server?

                        What am I doing wrong? How can I run DNS off of pfsenses internal DNS?

                        I didn't even know pfsense did this natively, I thought if I wanted to use an internal DNS server then I had to set up and run the whole thing on a real or virtual machine, which I dont know how to do.

                        1 Reply Last reply Reply Quote 0
                        • RonpfSR
                          RonpfS
                          last edited by

                          yup pfsense has a DNS Resolver  ;)

                          So now you have to check your hosts/device DNS configuration.

                          If they get DNS server configuration from a DHCP server, then configure the DHCP server to send pfsense ip.

                          @ :

                          Leave blank to use the system default DNS servers: this interface's IP if DNS Forwarder or Resolver is enabled, otherwise the servers configured on the System / General Setup page.

                          2.4.5-RELEASE-p1 (amd64)
                          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                          1 Reply Last reply Reply Quote 0
                          • P
                            pfBasic Banned
                            last edited by

                            awesome, i got it working as its meant to be, thank you for sticking with my ignorant line of questioning!

                            One last question, how does the "root server" resolve the DNS lookups? as in what tells my pfsense box the ip address that google.com resolves to?

                            1 Reply Last reply Reply Quote 0
                            • RonpfSR
                              RonpfS
                              last edited by

                              https://en.wikipedia.org/wiki/Domain_Name_System
                              https://en.wikipedia.org/wiki/Root_name_server

                              2.4.5-RELEASE-p1 (amd64)
                              Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                              Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                              1 Reply Last reply Reply Quote 0
                              • BBcan177B
                                BBcan177 Moderator
                                last edited by

                                A PR has been merged for pfBlockerNG. v2.1.1_6
                                  https://github.com/pfsense/FreeBSD-ports/pull/253

                                Fixes:

                                • EasyList has recently changed the format of the feed. DNSBL parser has been updated.
                                • Fix XMLRPC Sync setting that handles the Sync of the General settings to remote hosts.
                                • Fix DNSBL Certificate creation for pfSense 2.4

                                "Experience is something you don't get until just after you need it."

                                Website: http://pfBlockerNG.com
                                Twitter: @BBcan177  #pfBlockerNG
                                Reddit: https://www.reddit.com/r/pfBlockerNG/new/

                                1 Reply Last reply Reply Quote 0
                                • M
                                  mk6032
                                  last edited by

                                  @BBcan177:

                                  A PR has been merged for pfBlockerNG. v2.1.1_6
                                    https://github.com/pfsense/FreeBSD-ports/pull/253

                                  Fixes:

                                  • EasyList has recently changed the format of the feed. DNSBL parser has been updated.
                                  • Fix XMLRPC Sync setting that handles the Sync of the General settings to remote hosts.
                                  • Fix DNSBL Certificate creation for pfSense 2.4

                                  Hello, thanks for all your work on this. I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.

                                  http://imgur.com/a/I3mep

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    doktornotor Banned
                                    last edited by

                                    @mk6032:

                                    I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.

                                    http://imgur.com/a/I3mep

                                    Yes. And the point of the report is exactly what?

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      mk6032
                                      last edited by

                                      @doktornotor:

                                      @mk6032:

                                      I just wanted to report that I'm seeing the following in system -> pkg manager -> installed, even after reinstalling the package.

                                      http://imgur.com/a/I3mep

                                      Yes. And the point of the report is exactly what?

                                      Please review the linked image. There are two points :

                                      1. "Package is configured but not (fully) installed" (even after reinstallation)
                                      2. "Newer version available" (without the update option)

                                      Regards,
                                      Matt

                                      1 Reply Last reply Reply Quote 0
                                      • RonpfSR
                                        RonpfS
                                        last edited by

                                        @mk6032:

                                        Please review the linked image. There are two points :

                                        1. "Package is configured but not (fully) installed" (even after reinstallation)
                                        2. "Newer version available" (without the update option)

                                        Regards,
                                        Matt

                                        That is the Legend for the Package Manager  ::)

                                        So now look a the pfBlockerNG line and interpreting the legend the status of the package is "Current"

                                        2.4.5-RELEASE-p1 (amd64)
                                        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                                        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          mk6032
                                          last edited by

                                          @RonpfS:

                                          That is the Legend for the Package Manager  ::)

                                          So now look a the pfBlockerNG line and interpreting the legend the status of the package is "Current"

                                          Ah, my bad! The lack of a separator there as opposed to the ones above it is a bit confusing ( http://imgur.com/a/lwSFx ).

                                          Regards,
                                          Matt

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            doktornotor Banned
                                            last edited by

                                            @mk6032:

                                            @RonpfS:

                                            That is the Legend for the Package Manager  ::)

                                            So now look a the pfBlockerNG line and interpreting the legend the status of the package is "Current"

                                            Ah, my bad! The lack of a separator there as opposed to the ones above it is a bit confusing ( http://imgur.com/a/lwSFx ).

                                            Regards,
                                            Matt

                                            LOL, ok… https://redmine.pfsense.org/issues/7203

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