-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Min upload/downlaod rate in custom network #401
Comments
We did try that at one point. The problem is that using "rate" for HTBs (nodes) in that way results in the burst never being used for any leafs of that HTB. That becomes a tremendous hassle to troubleshoot. For HTBs, we set Ceil as the upper limit, and set Rate very close to the Ceil amount (98%, but it could be 100% too I think) so that every deeply nested node still has some chance of providing bandwidth up to or near its Ceil rate. Doing it this way allows HTB to handle cases where there is some small level of over-subscription or over-provisioning at some choke-point along the hierarchy (applicable to 99% of modern networks). Adding a rate/ceil for the nodes/network.json would lead to major network issues for anyone who tries to use it that way. |
Thank you for explanation.
|
Hi,
When defining network in custom mode (not using UISP/Splynx), we can only set the max upload download rate. Then, when creating shaped devices in line , we consider 98% of max upload/download as the min upload/download.
The min bandwidth determines the rate of the HTB and the max bandwidth determines the ceiling(burst size)
Since I need this feature, I can go ahead and implement it and add it as a feature to LibreQoS
The text was updated successfully, but these errors were encountered: