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

pfBlockerNG-devel Not Blocking Malvertizing on LAN

Scheduled Pinned Locked Moved pfBlockerNG
54 Posts 7 Posters 3.5k Views
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.
  • O
    OpIT GmbH
    last edited by Nov 17, 2022, 7:36 AM

    Under pfBlockerNG>DNSBL>DNSBL SafeSearch

    Here you can Enable Block DoH and DoT, so that the User is forced to use the System DNS. This works for us pretty good.

    1 Reply Last reply Reply Quote 0
    • G
      Gertjan @newUser2pfSense
      last edited by Nov 17, 2022, 8:02 AM

      @newuser2pfsense said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

      I checked my Firefox Network Settings and the default was set to "Use system proxy settings.

      That's just one step to check.
      But it could inform you that traffic generated to show web pages uses the system settings.
      DNS could be handled differently.

      And then there is your "system", the PC.
      Open a cmd windows, and type nslookup.
      On the second line, it should show the DNS server being used by your PC.
      Typically, this is 192.168.1.1 (or the IPv6 of your pfSense LAN).

      Test also like this : visit a web site you have never visited before : example : www.knmi.nl

      Now have a look at the pfBlockerng-devel DNS Reply page, and look (serach, Ctrl-F) for the word "knmi" : it should be there.
      This is a solid proof that pfBlockerNG-devel handles your DNS request.

      You should also see the host names of the sites that gave you the images in the spam mails.

      If these host names do not show up on the Unified or Alerts page, this means the host names used were not found in any of the lists/dns feeeds.

      No "help me" PM's please. Use the forum, the community will thank you.
      Edit : and where are the logs ??

      1 Reply Last reply Reply Quote 0
      • B
        Bob.Dig LAYER 8 @newUser2pfSense
        last edited by Nov 17, 2022, 9:07 AM

        @newuser2pfsense said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

        @steveits I checked my Firefox Network Settings and the default was set to "Use system proxy settings." I changed this setting to "No proxy" and this seems to have worked. Thanks.

        Scroll further down to see the DNS option...

        N 1 Reply Last reply Nov 17, 2022, 1:52 PM Reply Quote 0
        • N
          newUser2pfSense @Bob.Dig
          last edited by Nov 17, 2022, 1:52 PM

          @OpIT-GmbH DoH/DoT Blocking is enabled and I've chosen every entry in the list; probably a little overboard but what the heck.

          @Bob-Dig The "Enable DNS over HTTPS" in the Firefox browser is not checkmarked.

          @Gertjan www.knmi.nl was found in the DNS Reply page and the Unified page. In my Linux terminal, when I typed nslookup and hit enter, the next line only showed a > symbol.

          S 1 Reply Last reply Nov 17, 2022, 3:35 PM Reply Quote 0
          • S
            SteveITS Galactic Empire @newUser2pfSense
            last edited by Nov 17, 2022, 3:35 PM

            @newuser2pfsense said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

            In my Linux terminal, when I typed nslookup and hit enter, the next line only showed a > symbol.

            If you just run "nslookup" it runs the program and acts like its own shell. Run "nslookup google.com" or some other hostname to do a lookup and exit.

            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
            Upvote 👍 helpful posts!

            G 1 Reply Last reply Nov 18, 2022, 11:32 AM Reply Quote 0
            • O
              OpIT GmbH
              last edited by Nov 18, 2022, 10:16 AM

              Did you also add a Portforward Rule to force all DNS (Port 53) Triffic to pfSense

              1 Reply Last reply Reply Quote 0
              • G
                Gertjan @SteveITS
                last edited by Nov 18, 2022, 11:32 AM

                @steveits said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

                If you just run "nslookup" it runs the program and acts

                Add to that, when you run nslookup without parameters, it shows the DNS 'source' to be used.
                And it it will wait with its own command line '>' so you can enter (example) knmi.nl.

                C:\Users\gwkro>nslookup
                Serveur par défaut :   pfSense.local.net
                Address:  192.168.1.1
                
                >
                

                So, for me, 192.168.1.1 is where every LAN device 'should' (could) addresses itself for DNS requests.
                192.168.1.1 is of course my pfSense.

                Type

                help
                

                or

                set all
                

                to see more info.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                N 1 Reply Last reply Nov 18, 2022, 7:54 PM Reply Quote 0
                • N
                  newUser2pfSense @Gertjan
                  last edited by newUser2pfSense Nov 18, 2022, 7:56 PM Nov 18, 2022, 7:54 PM

                  I'd like to start by saying that I'm NO network guru, so please allow a little Grace for the following -

                  With an nslookup with no options, I get the following:
                  nslookup - no result.png

                  With an nslookup for the google, I get the following:
                  nslookup google.com.png

                  With an nslookup for pfSense.local.net, I get the following:
                  nslookup pfsense local.png

                  I'm not sure if this means anything to anyone. Not sure why I got a 52. address which is nowhere near what my WAN IP address is.

                  N G 2 Replies Last reply Nov 22, 2022, 1:44 PM Reply Quote 0
                  • N
                    newUser2pfSense @newUser2pfSense
                    last edited by Nov 22, 2022, 1:44 PM

                    Now it seems like no matter what settings I choose in Firefox, what my WLAN iPhone does not display in emails, my LAN desktop does.

                    1 Reply Last reply Reply Quote 0
                    • G
                      Gertjan @newUser2pfSense
                      last edited by Nov 22, 2022, 1:56 PM

                      @newuser2pfsense said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

                      With an nslookup for pfSense.local.net, I get the following:

                      Image

                      I'm not sure if this means anything to anyone. Not sure why I got a 52. address which is nowhere near what my WAN IP address is.

                      Euh ..... pfSense.local.net was an example.
                      You should use your pfsense host name, and the network.

                      pfSense.local.net points to 52.128.23.153, that's ok.

                      No "help me" PM's please. Use the forum, the community will thank you.
                      Edit : and where are the logs ??

                      N 1 Reply Last reply Nov 22, 2022, 2:12 PM Reply Quote 0
                      • N
                        newUser2pfSense @Gertjan
                        last edited by Nov 22, 2022, 2:12 PM

                        @gertjan Ok. Tried with my pfSense host name and received the following:

                        Server: 127.0.0.53
                        Address: 127.0.0.53#53

                        Non-authoritative answer:
                        Address: 192.168.1.1

                        S 1 Reply Last reply Nov 22, 2022, 3:29 PM Reply Quote 0
                        • S
                          SteveITS Galactic Empire @newUser2pfSense
                          last edited by Nov 22, 2022, 3:29 PM

                          @newuser2pfsense said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

                          127.0.0.53

                          What is this IP? Usually anything 127.x.x.x is "localhost" or "myself" indicating your computer is asking itself. Especially if 192.168.1.1 is your pfSense LAN IP. Double check what DNS servers are configured on your computer, and only set 192.168.1.1.

                          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                          Upvote 👍 helpful posts!

                          G B 2 Replies Last reply Nov 22, 2022, 3:51 PM Reply Quote 0
                          • G
                            Gertjan @SteveITS
                            last edited by Gertjan Nov 22, 2022, 3:53 PM Nov 22, 2022, 3:51 PM

                            @steveits said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

                            What is this IP?

                            Dono.

                            It sad : non-authoritative answer: so not pfSense.

                            @newUser2pfSense You should know on what system you are running the nslookup command (right ?) :

                            [22.05-RELEASE][admin@pfSense.whatever.net]/root: nslookup
                            > pfsense
                            Server:         127.0.0.1
                            Address:        127.0.0.1#53
                            
                            Name:   pfsense.whatever.net
                            Address: 192.168.1.1
                            Name:   pfsense.whatever.net
                            Address: 2001:470:dead:beef:2::1
                            

                            No "help me" PM's please. Use the forum, the community will thank you.
                            Edit : and where are the logs ??

                            N 1 Reply Last reply Nov 22, 2022, 4:08 PM Reply Quote 0
                            • N
                              newUser2pfSense @Gertjan
                              last edited by Nov 22, 2022, 4:08 PM

                              @SteveITS I have always set 192.168.1.1 for all of my LAN computers DNS servers. I use Cloudflare DNS servers in pfSense.
                              pfSense DNS Servers Settings.png

                              @gertjan I do know which computer, and it's LAN IP address, that I'm using to run the nslookup command.

                              S 1 Reply Last reply Nov 22, 2022, 4:18 PM Reply Quote 0
                              • S
                                SteveITS Galactic Empire @newUser2pfSense
                                last edited by Nov 22, 2022, 4:18 PM

                                @newuser2pfsense said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

                                I have always set 192.168.1.1 for all of my LAN computers DNS servers

                                nslookup (and therefore your PC) doesn't seem to be using that...? Try giving it a specific server:

                                nslookup google.com 192.168.1.1

                                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                                Upvote 👍 helpful posts!

                                N 1 Reply Last reply Nov 22, 2022, 4:22 PM Reply Quote 0
                                • N
                                  newUser2pfSense @SteveITS
                                  last edited by Nov 22, 2022, 4:22 PM

                                  @steveits Here is the output to nslookup google.com 192.168.1.1

                                  nslookup google.com 192.168.1.1
                                  Server: 192.168.1.1
                                  Address: 192.168.1.1#53

                                  Non-authoritative answer:
                                  Name: google.com
                                  Address: 172.253.122.138
                                  Name: google.com
                                  Address: 172.253.122.102
                                  Name: google.com
                                  Address: 172.253.122.139
                                  Name: google.com
                                  Address: 172.253.122.101
                                  Name: google.com
                                  Address: 172.253.122.113
                                  Name: google.com
                                  Address: 172.253.122.100
                                  Name: google.com
                                  Address: 2607:f8b0:4004:c1b::8b
                                  Name: google.com
                                  Address: 2607:f8b0:4004:c1b::8a
                                  Name: google.com
                                  Address: 2607:f8b0:4004:c1b::71
                                  Name: google.com
                                  Address: 2607:f8b0:4004:c1b::65

                                  S 1 Reply Last reply Nov 22, 2022, 4:26 PM Reply Quote 0
                                  • S
                                    SteveITS Galactic Empire @newUser2pfSense
                                    last edited by Nov 22, 2022, 4:26 PM

                                    @newuser2pfsense OK. And if you try a hostname you think should be blocked what do you get?

                                    So far what we seem to have established is your test computer is using 127.0.0.53 for its DNS not the pfSense. Perhaps some sort of VPN or security software? Whatever it is, it is likely not using the pfSense DNS Resolver and hence you are not seeing sites be blocked.

                                    Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                                    When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                                    Upvote 👍 helpful posts!

                                    N 1 Reply Last reply Nov 22, 2022, 4:30 PM Reply Quote 0
                                    • N
                                      newUser2pfSense @SteveITS
                                      last edited by Nov 22, 2022, 4:30 PM

                                      @steveits pfBlockerNG-devel & Suricata are the only security packages I use on my pfSense box. I do not have any VPN software packages installed or configured in pfSense at present.

                                      I'm not sure what you might mean by trying a hostname that I think should be blocked. Could you please provide an example and I'll give it a go?

                                      S 1 Reply Last reply Nov 22, 2022, 4:34 PM Reply Quote 0
                                      • S
                                        SteveITS Galactic Empire @newUser2pfSense
                                        last edited by Nov 22, 2022, 4:34 PM

                                        @newuser2pfsense I meant, on your PC. Something is getting the PC to use 127.0.0.53. I'm only guessing as what it is.

                                        re: blocked, your subject line was "pfBlockerNG-devel Not Blocking..." and you referenced email images...can you find a URL for one of those?

                                        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                                        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                                        Upvote 👍 helpful posts!

                                        N 1 Reply Last reply Nov 22, 2022, 6:05 PM Reply Quote 0
                                        • B
                                          bingo600 @SteveITS
                                          last edited by bingo600 Nov 22, 2022, 6:06 PM Nov 22, 2022, 6:00 PM

                                          @steveits said in pfBlockerNG-devel Not Blocking Malvertizing on LAN:

                                          Server: 127.0.0.53
                                          What is this IP? Usually anything 127.x.x.x is "localhost" or "myself" indicating your computer is asking itself.

                                          Linux systemd "DNS Resolver daemon"
                                          It usually forwards to the "Real DNS received via DHCP", but it "annoyingly" caches "unresolved" names too.

                                          Ie. if you have a "local DNS server" , and try to ping server3 , and get unresolvable .... You then remember that you forgot to enter server3's A record in your DNS server , and does that now.

                                          When you now ping server3 on "whatever" it resolves , except on the machine you pinged it from , before making the A record .. It still uses the "cached unresolvable" 👎 - You have to restart the DNS Daemon or flush the cache.

                                          Or when hit enough times ... Kick that DNS daemon to He.. , and use settings from "good ole" resolv.conf

                                          /Bingo

                                          If you find my answer useful - Please give the post a 👍 - "thumbs up"

                                          pfSense+ 23.05.1 (ZFS)

                                          QOTOM-Q355G4 Quad Lan.
                                          CPU  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
                                          LAN  : 4 x Intel 211, Disk  : 240G SAMSUNG MZ7L3240HCHQ SSD

                                          S 1 Reply Last reply Nov 30, 2022, 11:03 PM Reply Quote 0
                                          23 out of 54
                                          • First post
                                            23/54
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received