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

    Traffic not matching floating rule

    Firewalling
    traffic shaping
    2
    3
    724
    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.
    • gnitingG
      gniting
      last edited by

      I am sure it is an obvious error, but for the life of me I can't figure out why no traffic is matching the floating rule highligted in red. I am trying to push traffic from low priority hosts on my network to a low priority queue. Everything else seems to be working fine.
      alt text

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @gniting
        last edited by

        Check Status/Queues to make sure the traffic isn't actually in the queue and the state counter just isn't counting up.

        Check Diagnostics/States and see if the state is matching your source. For instance in order to lower priority on a download the state may be to the webserver:443 and the return traffic matches the state but not the rule. (so, doesn't seem to count up the counter...)

        Is low_priority_src a LAN IP behind NAT? If so it can't match, see https://docs.netgate.com/pfsense/en/latest/trafficshaper/advanced.html#shaper-rule-matching-tips for info on tagging it.

        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!

        gnitingG 1 Reply Last reply Reply Quote 1
        • gnitingG
          gniting @SteveITS
          last edited by

          @steveits said in Traffic not matching floating rule:

          Check Status/Queues to make sure the traffic isn't actually in the queue and the state counter just isn't counting up.

          Check Diagnostics/States and see if the state is matching your source. For instance in order to lower priority on a download the state may be to the webserver:443 and the return traffic matches the state but not the rule. (so, doesn't seem to count up the counter...)

          Is low_priority_src a LAN IP behind NAT? If so it can't match, see https://docs.netgate.com/pfsense/en/latest/trafficshaper/advanced.html#shaper-rule-matching-tips for info on tagging it.

          Brilliant, thanks so much for the hint/info on tagging!

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