HSFC Traffic Shapping not Artifically Capping my Bandwidth
-
I used the wizard to set up traffic shaping with HSFC but when I run a speed test, I get speeds a lot higher then the limit I set. Any ideas what is going on? I am on Pfsense 2.2.4 .
-
I get speeds a lot higher then the limit I set.
HFSC is all about providing guaranteed service levels. You don't limit HFSC, you establish minimums. HFSC will provide full bandwidth if nothing else is in contention.
-
What I am aiming for is guaranteeing bandwidth and low ping to certain applications. I also want to set some applications at a lower priority then default. I want different internet uses to not have set bandwidth. If one application is not using the bandwidth, it should share to another. Should I use a hybrid of hfsc and something else?
-
If you need to provide realtime guarantees than HFSC is what you need. It's not for the faint of heart though.
-
Do I need to have hsfc inside another technique so I can cap max internet speed? If so what technique?
-
HFSC does shaping. Limiters do limiting. You can use both at the same time.
-
Did you set the rate limit on your LAN and WAN interfaces? The bandwidth option in HFSC is not how much bandwidth the queue can use, but how much it will get when all other queues are contenting for bandwidth. Of course HFSC will allow you to use up to the full rate of your interface, which is why you need to rate limit your interface.
You can only shape egress, so to shape download you need to shape your LAN and upload you shape your WAN.
See the "99"
-
If you want to limit an HFSC queue, use upper-limit. It can limit bandwidth (or latency).
Real-time sets minimum (guaranteed) BW/latency, if used properly.
Link-share does the same but with no guarantees. (Real-time has priority, and during that time, the non-real-time BW is split among all the link-shares proportionally.)
Upper-limit sets … an upper-limit. ;)Interfaces/devices are usually controlled by ALTQ's Token Bucket Regulator, not HFSC.See https://www.sonycsl.co.jp/person/kjc/software/TIPS.txt (author of ALTQ). If you get the interface bandwidth wrong, HFSC will not work properly.I would use CBQ (or HFSC with m2 params exclusively) until I had mastered it. HFSC is a mind-fuck.
-
If you want to limit an HFSC queue, use upper-limit. It can limit bandwidth (or latency).
Upperlimit has no effect when I apply it to the qinternet folder.
-
Is your internet traffic going into the qInternet queue or its sub-queues? On your WAN interface, all of your traffic should be under qInternet.
-
Make sure your WAN interface is properly throttled. Take your real-world, average maximum throughput/goodput value and set the interface ~3-10% less than said value.
Until your interface is properly rate-limited, HFSC (or any pfSense/ALTQ sched algo) has no queue to manipulate. The interface needs to receive traffic slightly faster than it can send, otherwise there's no traffic in the buffer/queue for HFSC to intelligently (re)schedule.
PS - Are you resetting states?
