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

    Shaping after failover

    Scheduled Pinned Locked Moved Traffic Shaping
    4 Posts 4 Posters 2.6k 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.
    • N
      NAmorim
      last edited by

      I have a queue configured that is limiting traffic from and to an IP. All is fine and working until I make a failover to the other node. Then, all the connected clients go to the default queue, and  new connections go to the right queue.

      Why is that? Why does not all the failed over traffic go to the right queues?

      Thank you for the help…

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

        This is quite interesting. Connections are assigned to a queue on opening new connections. That's why you have to reset the states if you made changes to the shaper and want already established connections to be reassigned. I guess due to the syncing of the states everything ends up in the default queue as altq information is not synced over but just the plain states. I wonder if it's doable to sync the states to the correct queues. Maybe Bill or Scott can comment on this in a more "technical" way.

        1 Reply Last reply Reply Quote 0
        • S
          sullrich
          last edited by

          This is to be expected.    CARP/pfSync does not sync the ALTQ assignments.  When a new connection (state) is created then the queue is reassigned.

          This will change in the future with our Layer 7 shaper detection work that is ongoing.

          1 Reply Last reply Reply Quote 0
          • B
            billm
            last edited by

            @sullrich:

            This is to be expected.    CARP/pfSync does not sync the ALTQ assignments.  When a new connection (state) is created then the queue is reassigned.

            This will change in the future with our Layer 7 shaper detection work that is ongoing.

            I think this is also "fixed" in the kernel patches that I made not too long ago (not in 1.0).

            –Bill

            pfSense core developer
            blog - http://www.ucsecurity.com/
            twitter - billmarquette

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