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

    Firewall rules sorting

    Scheduled Pinned Locked Moved pfBlockerNG
    5 Posts 2 Posters 682 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
      DraNick
      last edited by

      Hello,

      I have a set of rules for both WAN and LAN. I have noticed that if I have a set of allow traffic and have specific block rules for certain IPs for the same traffic, the traffic is not blocked if the block rules are below the allow ones however, if I move the block ones above the allowing rules they get automatically moved at the bottom of the rules set for each interface.
      Is there a way to "pin" rules to a certain position?
      I am running a Super Micro XG-1537.

      Thank you in advance,

      Nick

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Rules don't move by themselves. Are you using pfBlockerNG?

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

          Yes I also have pfBlockerNG installed and active.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            pfBlocker is rearranging your rules. You can set pfBlocker to only maintain the aliases you use so you can manually set the rules and their locations.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            D 1 Reply Last reply Reply Quote 1
            • D
              DraNick @Derelict
              last edited by

              @Derelict thank you!

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