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

    Traffic Shaping acts as Limiter???

    Scheduled Pinned Locked Moved Traffic Shaping
    9 Posts 4 Posters 5.0k 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.
    • D
      danbutter
      last edited by

      What I am seeing is this…
      when I use the shaping wizard and put in the available bandwidth...whatever I put in there is the maximum I can see from any one computer....as if the traffic shaper is now acting as a limiter when it didn't before.

      I just tonight upgraded to 1.0.1 from 1.0 RC3 and this just started after doing so.

      Prior to this when doing the wizard, I put a little less than my line is advertised and could see more on downloads and uploads.
      Now that I have upgraded, whatever I put in the wizard is the maximum I can get.

      This is rather annoying and now since my ISP has enabled a type of bursting on my line I have to set my download to 30000k to be able to use it.  I do believe this makes the queues worthless as my available bandwidth is not always 30000k.

      I tried to read around, but didn't see anyone else with this problem.

      Anyone have any ideas?

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

        1.0 RC3 is older than 1.0.1.

        Otherwise check out http://forum.pfsense.org/index.php/topic,1384.0.html

        1 Reply Last reply Reply Quote 0
        • D
          danbutter
          last edited by

          yes, I am aware of the ages of the versions. 
          How is that supposed to help me? 
          Not trying to be a smartass here, but I really don't understand.

          What I am wondering is that if this behavior is supposed to happen or not.
          Doesn't make much sense to me that it would.

          I have to do some more testing to see if my voip is prioritized as it should be with having to set my download to 30000k to be able to use my bursting.

          If so I guess I won't worry about it, but if not then I may just have to revert back to 1.0 RC3 unless someone can help me figure out what to do about this.

          thanks

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

            1.0 RC3 was 1.0 release candiate 3, 2 version before 1.0 came out.

            1.0.1 is the latest release version.

            1.0.1 snapshots are the latest testing version with only bug fixes + freebsd 6.2 - RC1.

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

              @danbutter:

              What I am seeing is this…
              when I use the shaping wizard and put in the available bandwidth...whatever I put in there is the maximum I can see from any one computer....as if the traffic shaper is now acting as a limiter when it didn't before.

              I just tonight upgraded to 1.0.1 from 1.0 RC3 and this just started after doing so.

              Prior to this when doing the wizard, I put a little less than my line is advertised and could see more on downloads and uploads.
              Now that I have upgraded, whatever I put in the wizard is the maximum I can get.

              This is rather annoying and now since my ISP has enabled a type of bursting on my line I have to set my download to 30000k to be able to use it.  I do believe this makes the queues worthless as my available bandwidth is not always 30000k.

              I tried to read around, but didn't see anyone else with this problem.

              Anyone have any ideas?

              If you have burstable bandwidth, traffic shaping will be of zero use for you.  In theory if you knew how long the ISP would burst for you could configure HFSC to allow a burst amount and scale back to your guaranteed bandwidth.  Burstable bandwidth isn't something I plan on ever having the wizard support, it's an advanced setup and anyone completely understanding what needs to be done for it would likely be better off writing their pf.conf by hand.

              –Bill

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

              1 Reply Last reply Reply Quote 0
              • D
                danbutter
                last edited by

                I understand that the shaper isn't meant for bursting, however the only question I am looking for an answer to right now is this:

                Is the traffic shaper supposed to act as a limiter?

                It is in fact doing so as of 1.0.1 for me when it did not when I was using 1.0 RC3.

                I am asking because I don't know if I did something wrong or my upgrading botched something.

                Put it this way… If you have a 5Mb line and you use the shaper wizard and put in 3500 for your downstream link, will you see ~3500kbps on a speed test or using some monitoring software on your computer?

                This is what is happening to me. I put in 7500 out of 8000 back when I was using 1.0 RC3 and I could still see 8300 on downloads.  Right after upgrading to 1.0.1 all speed tests and monitoring show 7.49 - 7.5 Mb while shaper is enabled.  If I disable the shaper then I fly up to 25000kbps for a short time and then see the normal 8300 after that.  Enable the shaper...7500 on the nose.

                The only thing I really want shaped/prioritized is the upload for my voip as I have no issues with it unless there is a computer on my network uploading when trying to make a phone call.

                Right now I am just trying to figure out if my setup is broken and I need to do a clean install or what.

                thanks

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

                  It is acting as a limiter to not overload your line. How else should it know that it has to drop some packets that are low priority as your link is saturated?

                  1 Reply Last reply Reply Quote 0
                  • D
                    danbutter
                    last edited by

                    Thanks for the answer.

                    I guess it was just broken in 1.0 RC3 since it wasn't doing this.
                    It would make sense now that I think about it/you explain it.

                    So I guess there is no way to make sure my voip traffic gets prioritized without sacrificing my lines bursting capabilities huh?
                    Oh Well, that is life for you. Full of sacrifice.

                    thanks again for the clear cut answer hoba.

                    Oh and the bursting is from the cable ISP Comcast.  They call it "powerboost" and it is supposed to be rolled out nationwide.  Since they are the US's largest cable ISP you may see more questions about this in the future.
                    Here is the official FAQ on it: http://www.comcast.net/help/faq/index.jsp?cat=Services#PowerBoost

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

                      Things like that will never be controllable I think as you never know the current limit of the line.

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