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

    Incorrect state / traffic counters for floating match rules

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 3 Posters 506 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.
    • T
      t_k
      last edited by

      I maintain two different pfsense systems at different sites. At each site, I’m using a handful of floating match rules across a few VLANs for traffic shaping. These match rules just put traffic into various limiter child queues and this is working. I’ve performed a series of tests to confirm that traffic is being routed into the child queues as I expect.

      However, I always see very low numbers for the state and traffic counters in the UI. I'll see a few hundred active states and gigs of traffic in ntop, and be able to confirm that traffic is going into various limiter child-queues, the but match rules will show 0 states and only a few hundred megabytes of traffic.

      I’ve done some googling to try to see if this is just a bug or something I’ve misconfigured, and haven’t come up with anything. Can somebody please point me in the right direction?

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        The rules opening the firewall states for that traffic are the pass rules on the individual interfaces. Not the floating match rules.
        The traffic counters on match rules have always seemed suspect IMO.

        Steve

        1 Reply Last reply Reply Quote 1
        • T
          t_k
          last edited by

          @stephenw10

          Thanks for the context!

          Unless I hear otherwise, I'll assume the answer is "don't expect match rules to have accurate traffic counters" for the reason you specified.

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

            Might only be counting the SYNs at state creation.

            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 1
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Yes it's unclear exactly what they are counting or should be counting. To me at least.
              I would not rely on them for any accurate measure of traffic that is matched.

              Steve

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