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

    Match rule - pass or drop?

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 327 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.
    • R
      RadOD
      last edited by

      Docs say:

      "Firewall rules on Interface and Group tabs process traffic in the Inbound direction and are processed from the top down, stopping at the first match."
      "Floating rules without quick set process as “last match wins” instead of “first match wins”
      "Apply traffic shaping to match traffic but not affect it’s pass/block action"

      Now generally rule processing stops when a match is found. I see that floating rules are different and can be either first or last match is the rule that goes into effect depending on whether 'quick' is on or off. I understand that floating rules work differently.

      What I can't seem to find the answer to is what happens when a 'match' rule is matched? If it is not blocked/rejected/allowed does it just get attributes added to it and go on to match a second rule? Breaking the concept of 'rule processing stops at the first rule that matches?

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

        Traffic is neither passed nor blocked. It is matched. You can do things like assign a queue or a tag or log it but it does not change the pass or drop status of the traffic.

        quick has no bearing on match rules. They always flow though and rule processing continues.

        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
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.