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

    Traffic Shapper - P2P greater than 30% not allowed.

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    6 Posts 3 Posters 4.7k 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
      Cjaiceman
      last edited by

      "Custom Bandwidths are greater than 30%. Please lower them for the wizard to continue."

      This problem still exists in 2.0-RC3 Mon Aug 8 18:47:42 EDT 2011

      I am using the Multi WAN/LAN wizard "traffic_shaper_wizard_multi_all.xml"

      Also, I get an error when trying to use anything other than percentage, but in the drop down menu we have many other options. My question is, if percentage is only allowed, why put the other options in there? (This is much less of a problem than above, I just wanted to point it out).

      Thank you in advance your help  ;)

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

        Yah, it is still there.  The wizard currently uses the bandwidth specified as both the LINK Share bandwidth and the Upper Limit bandwidth, if we are talking about HFSQ queuing.  All the LINK share percentages have to add up to less than 100%, and certain amounts are already put aside for the other queues, thus the 30% limit.  The upperlimit can be set to %100 though, to allow p2p traffic full bandwidth when the link isn't full.  When there are multiple streams of traffic the amount that each queue uses will tend towards the LINK share amount.  You can try setting the LINK Share to lower, like 10%, and the upper limit to %80, and get pretty good performance.

        The wizards try to handle the 3 different queuing disciplines with the same input data, but it doesn't work quite right because of how each uses slightly different methods to solve the problem.

        Ermal(the traffic shaping wizard wizard) is really busy, so just don't think this is important enough for him to work on, unless someone sponsors the work.
        Josh

        Hardware used: Alix 2D13 X 10, APU2D4 X 10, SG-2200 X 10, SG-2440 X 4

        1 Reply Last reply Reply Quote 0
        • E
          eri--
          last edited by

          Try new snapshots of tomorrow.

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

            Classic example of reverse psychology in action. :)

            Hardware used: Alix 2D13 X 10, APU2D4 X 10, SG-2200 X 10, SG-2440 X 4

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

              I think this is the change Ermal made that could be related to this issue.

              https://github.com/bsdperimeter/pfsense/commit/577c402dc7cd6de55017967847053206ad356990
              Make the checks during step4 and step5 actually work.

              Is this the fix?  It looks like it is correcting a check to see if the bandwidth is greater than 15% or less than 2%…. but even when I do put in a bandwidth > 15% I don't get the error, and the bandwidth that I enter isn't used, the p2p bandwidth is just set to 5%?

              Hmmm
              Josh

              Hardware used: Alix 2D13 X 10, APU2D4 X 10, SG-2200 X 10, SG-2440 X 4

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

                Also, I have another question, why do speed tests get put in the p2p queue? I thought they were http traffic…  :o

                Also, as a feature request, could we get a section for FTP transfers?  ;D

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