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

    [FIXED] Traffic Shaping Issues

    Scheduled Pinned Locked Moved Traffic Shaping
    4 Posts 2 Posters 781 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.
    • M
      MrJonny
      last edited by

      Hi All,

      I've setup traffic shaping but, I'm really not sure I've done it correctly.

      See my Rules.png attachment for the rules floating. There set to the interface(LAN & WAN) in each rule.
      But when I look at the queue status, only the lan queue qOthersHigh is getting use and I know for sure that TeamSpeak will have inbound traffic too.

      Have I get this setup correctly?

      Also when using a Static NAT, the state looks the wrong way round? Should the top state, Dest and Source be the other way round? (See screenshot states.PNG)

      I have the same queues on LAN as I do on WAN.

      Should I scrap the queues and rules and rerun the wizard? I configured it way back in 2.3.2 or something like that and went to check it today, and thought "that doesn't look right".

      Hope you guys can help

      Jonny
      Rules.PNG
      Rules.PNG_thumb
      states.PNG
      states.PNG_thumb

      1 Reply Last reply Reply Quote 0
      • M
        MrJonny
        last edited by

        Gotten even weirder now.

        See screenshot. How's it gone over 1.4GBit?

        EDIT: Problem fixed with https://github.com/pfsense/pfsense/commit/6b54c8a4d39bbc32ea5c542c0ed9d2bcabbd1077

        Just the getting traffic in the right queues left.

        wierder.PNG
        wierder.PNG_thumb

        1 Reply Last reply Reply Quote 0
        • M
          MrJonny
          last edited by

          Problem has been solved. Issue was with the catch rule at the bottom.
          Removed it, set the default queue in the shaper and boom working correctly.

          1 Reply Last reply Reply Quote 0
          • H
            Harvy66
            last edited by

            For floating rules, catch all should be at the top. For normal rules, catch all should be at the bottom.

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