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

    Pfense 2.3.2 & CBQ : child bandwidth is higher than parent [ BUG ]

    Scheduled Pinned Locked Moved Traffic Shaping
    8 Posts 5 Posters 1.8k 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.
    • C
      craymore
      last edited by

      Hi all,

      I'm trying to modify a very simple traffic shaper on a pfs 2.3.2 appliance.

      Here are its specs :

      LAN ( CBQ ) / Total bandwith : 90Mbps

      queue    priority  bandwith %

      -    q_icmp    7        5%
      -    q_udp    6        10%
      -    q_ACK    5        15%
      -    q_high    4        20%
      -    q_default 3        35%
      -    q_low    2        10%
      -    q_lowest  1        5%

      When I try to change the bandwidth to 80Mbps, I get the follwowing error message :

      The following input errors were detected: The sum of child bandwidth is higher than parent.

      ???

      I don't understand why I'm being given such message ( considering the setup I have ).

      Any help would be appreciated  :)

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

        I have the same thing with HFSC. It's a bug with validation for percentages in pfSense. The problem is it translates the percentages into bandwidth values, so it sees the total being 90Mb when you attempt to set to 80Mb. It is not an issue if you use raw bandwidth values. Increasing your bandwidth works just fine.

        A simple work around, if you wan to continue to use percentages, is to take your 35% queue and set it to 1Mb, which will bring the total below 80Mb and allow the other percentages to get set when lowering your bandwidth, then change it back to 35% since it will validate against the new 80Mb, which will again add to 100%.

        1 Reply Last reply Reply Quote 0
        • C
          craymore
          last edited by

          @Harvy66:

          I have the same thing with HFSC. It's a bug with validation for percentages in pfSense. The problem is it translates the percentages into bandwidth values, so it sees the total being 90Mb when you attempt to set to 80Mb. It is not an issue if you use raw bandwidth values. Increasing your bandwidth works just fine.

          A simple work around, if you wan to continue to use percentages, is to take your 35% queue and set it to 1Mb, which will bring the total below 80Mb and allow the other percentages to get set when lowering your bandwidth, then change it back to 35% since it will validate against the new 80Mb, which will again add to 100%.

          Thank you for your answer

          I managed to modify the overall bandwidth following your advice, and it worked indeed :)

          I suspected that it was a bug but was not entirely sure ( tought that there was maybe a tricky setting for a queue that was messing the entire shaper )

          Has this bug been filed yet or does it need to be officially reported ?  ???

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

            I have not reported it. I did discus it with some of the more influential people, but that doesn't mean anything in the end.

            1 Reply Last reply Reply Quote 0
            • N
              Nullity
              last edited by

              I think that ALTQ's CBQ supports percentages (pbandwidth), so I wonder why pfSense changes the percentage values to absolute bandwidth values

              Please correct any obvious misinformation in my posts.
              -Not a professional; an arrogant ignoramous.

              1 Reply Last reply Reply Quote 0
              • KOMK
                KOM
                last edited by

                So you can end up with wonky values with a precision of three decimal places?  ;D

                1 Reply Last reply Reply Quote 0
                • w0wW
                  w0w
                  last edited by

                  I think it's related to https://redmine.pfsense.org/issues/6779 and must be fixed with 2.4
                  I can test it later.

                  1 Reply Last reply Reply Quote 0
                  • w0wW
                    w0w
                    last edited by

                    No it's not. I got same error message.
                    Please create ticket on redmine if you want it to be fixed.

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