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

    PfBlockerNG rules is going downwards in the firewall rule everyday

    Scheduled Pinned Locked Moved pfBlockerNG
    45 Posts 11 Posters 14.3k 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.
    • D
      doktornotor Banned
      last edited by

      Since you didn't bother with posting the firewall rules screenshot, just a generic note. You cannot fiddle with the automatic rules ordering manually. If you need manual ordering, then use one of the aliases options in Rule Action and create the rules yourself.

      1 Reply Last reply Reply Quote 0
      • S
        souradip roy
        last edited by

        Sorry we missed that . Please have a look into the screenshot.

        ![pfblocker firewall rules.jpg](/public/imported_attachments/1/pfblocker firewall rules.jpg)
        ![pfblocker firewall rules.jpg_thumb](/public/imported_attachments/1/pfblocker firewall rules.jpg_thumb)

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

          This ain't firewall rules screenshot. Firewall rules are under Firewall - Rules. You already posted this.

          1 Reply Last reply Reply Quote 0
          • S
            souradip roy
            last edited by

            Ah sorry we misunderstood  that. Here is the attachment.Thanks.

            ![firewall rules.jpg](/public/imported_attachments/1/firewall rules.jpg)
            ![firewall rules.jpg_thumb](/public/imported_attachments/1/firewall rules.jpg_thumb)

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

              Wonderful. And - the problem is? I cannot see any problem there. It exactly matches pfBNG settings.

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

                @souradip:

                We have a pfBlockerNG rules , that is ordered as normal in the settings . The rule is automatically ordered downwards and we need to move it upwards in the firewall stack manually everyday at 12:00AM hours. Please help in this regards.

                Which rule(s) are you moving each day?

                "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
                • S
                  souradip roy
                  last edited by

                  We are moving the underlying rule in a daily basis at the top of firewall stack.

                  pfb_ip_rules.jpg
                  pfb_ip_rules.jpg_thumb

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

                    Yes. That is by design and as configured. Sigh.

                    1 Reply Last reply Reply Quote 0
                    • D
                      dsmithson
                      last edited by

                      What Souradip is saying is that he has to manually move the Block rule to the top after the automatic ordering routine fires.  The ordering routine actually does not  move the Block rule to the top.  It moves it down.  The screenshot he is presenting is to highlight the rule that has to be manually moved to the top ever night.

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

                        souradip roy,

                        Goto the IPv4 tab, and Click-Hold-Drag the Block rules to the Top so that they are first.  Save.

                        Repeat that for the IPv6 Tab.

                        Then execute a "Force update"

                        "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
                        • P
                          pfcode
                          last edited by

                          @BBcan177:

                          souradip roy,

                          Goto the IPv4 tab, and Click-Hold-Drag the Block rules to the Top so that they are first.  Save.

                          Repeat that for the IPv6 Tab.

                          Then execute a "Force update"

                          The issue was that a rule was created at Floating rule tab, and moved to the top, but once pfBlockerNG updates the rules. all the non-pfBlockerNG rules should be on the top were moved to the bottom, while all the pfBlockerNG rules were on the top, which shouldn't be.  Thats the major issue using  pfBlockerNG.

                          Release: pfSense 2.4.3(amd64)
                          M/B: Supermicro A1SRi-2558F
                          HDD: Intel X25-M 160G
                          RAM: 2x8Gb Kingston ECC ValueRAM
                          AP: Netgear R7000 (XWRT), Unifi AC Pro

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

                            @pfcode:

                            The issue was that a rule was created at Floating rule tab, and moved to the top, but once pfBlockerNG updates the rules. all the non-pfBlockerNG rules should be on the top were moved to the bottom, while all the pfBlockerNG rules were on the top, which shouldn't be.  Thats the major issue using  pfBlockerNG.

                            Dude. That is NOT how it works with what the OP configured. OMG… Select the proper option there. Not the one that puts pfBNG rules on the top by design. Really.

                            1 Reply Last reply Reply Quote 0
                            • S
                              souradip roy
                              last edited by

                              Hi ,

                              We are still in the same state of problem after following your advise. It would be very kind of yours if you can suggest any thing else to fix this.

                              Thank you in advance.

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

                                Yeah, you are in state of problem because you have selected the WRONG ORDER. Looks at the OTHER options there. Pick one that fits your needs. The one shown on your screenshots is NOT the one you want. Possibly you want this one instead:

                                1 Reply Last reply Reply Quote 0
                                • P
                                  pfcode
                                  last edited by

                                  @doktornotor:

                                  Yeah, you are in state of problem because you have selected the WRONG ORDER. Looks at the OTHER options there. Pick one that fits your needs. The one shown on your screenshots is NOT the one you want. Possibly you want this one instead:

                                  Don't know whether you have tested it or not before helping others.  I had exactly the same rule order setting as you mentioned, BUT after pfBlockerNG updates its rules. the rules order at Floating rule tab were not right.  All the non-pfBlockerNG rules supposedly on the top were moved to the bottom, all the pfBlockerNG rules were placed on the top.

                                  Release: pfSense 2.4.3(amd64)
                                  M/B: Supermicro A1SRi-2558F
                                  HDD: Intel X25-M 160G
                                  RAM: 2x8Gb Kingston ECC ValueRAM
                                  AP: Netgear R7000 (XWRT), Unifi AC Pro

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    dsmithson
                                    last edited by

                                    The current setting is the default.  Doesn't that option mean to keep the BLOCK/REJECT rules at the TOP?  It is not doing that.  It is MOVING THEM DOWN AUTOMATICALLY.

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

                                      @dsmithson:

                                      The current setting is the default.  Doesn't that option mean to keep the BLOCK/REJECT rules at the TOP?  It is not doing that.  It is MOVING THEM DOWN AUTOMATICALLY.

                                      Hopeless. Explained ~10 times by now.

                                      @pfcode: Need a translator, perhaps? Getting absolutely ridiculous. With what the OP configured, yes, it will ALWAYS get moved. Because he configured that this way. PEBKAC.  OSI Layer 8 error.  ::)

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        pfcode
                                        last edited by

                                        Hi, BB

                                        Got your file. It worked like a charm.  Thanks much for the fix, well done.

                                        Release: pfSense 2.4.3(amd64)
                                        M/B: Supermicro A1SRi-2558F
                                        HDD: Intel X25-M 160G
                                        RAM: 2x8Gb Kingston ECC ValueRAM
                                        AP: Netgear R7000 (XWRT), Unifi AC Pro

                                        1 Reply Last reply Reply Quote 0
                                        • D
                                          dsmithson
                                          last edited by

                                          @doktornotor:

                                          @dsmithson:

                                          The current setting is the default.  Doesn't that option mean to keep the BLOCK/REJECT rules at the TOP?  It is not doing that.  It is MOVING THEM DOWN AUTOMATICALLY.

                                          Hopeless. Explained ~10 times by now.

                                          @pfcode: Need a translator, perhaps? Getting absolutely ridiculous. With what the OP configured, yes, it will ALWAYS get moved. Because he configured that this way. PEBKAC.  OSI Layer 8 error.  ::)

                                          I don't think you've explained anything at all here.  The option selected is supposed to ensure that BLOCK/REJECT rules are at the TOP.  It does not do that.  The BLOCK/REJCET RULE IS BEING MOVED DOWN!!!!  What exactly do you think you have explained?

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

                                            OMG. No, the option will put whatever pfBNG rules to the top. There clearly is a whole lot of people who should never use this package, because it's way over they head and they have no clue what they are doing. Those "I've blocked the entire world minus my country" guys are another example.

                                            P.S. Need a replacement keyboard? Seems like you have a key stuck.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.