FreshJR
Very Senior Member
Here is a crude version of bandwidth limiting & adaptive QOS simultaneously.
Follow this guide, with this version of the script.
https://www.snbforums.com/threads/t...ements-custom-rules-and-inner-workings.36836/
I still need to modify the script so it bandwidth limits everything except net control packets, but medwatt has been sending me a PM everyday for the last two weeks asking me if its ready, so this is a rushed version. During the pscp step, make sure you use this updated name.
Edit:
It isn't immediately clear without reading the script so I will explicitly state what it does.
While the script has adaptive QOS and bandwidth limiter working together, they are not working simultaneously, instead the bandwidth limited traffic is just limited but NOT prioritized by category.
Simply put all traffic from bandwidth limited clients will be put into the last adaptive QOS category, which itself is bandwidth limited. That last QOS category does not contain unidentified traffic anymore, so now in essence you have bandwidth limiting being done for clients but their traffic is not category prioritized the same as non-limited traffic. It's a hybrid system where you get EITHER/OR.
Now with RMerlin's TC interposer, it is possible to permanently change the TC class structure, something which was locked down before. If you modify his interposer, you can create a fully meshed adaptive QOS & bandwidth limited system. I am not going to be looking into that modification right now as a more pressing issue exists within the existing QOS system I would like to fix. I will attach a picture of what needs to be done if someone wants to purse it themselves.
Top is original QOS
Middle is the hybrid implemented in my script
Bottom is what now is possible with the TC interposer
Follow this guide, with this version of the script.
https://www.snbforums.com/threads/t...ements-custom-rules-and-inner-workings.36836/
I still need to modify the script so it bandwidth limits everything except net control packets, but medwatt has been sending me a PM everyday for the last two weeks asking me if its ready, so this is a rushed version. During the pscp step, make sure you use this updated name.
Edit:
It isn't immediately clear without reading the script so I will explicitly state what it does.
While the script has adaptive QOS and bandwidth limiter working together, they are not working simultaneously, instead the bandwidth limited traffic is just limited but NOT prioritized by category.
Simply put all traffic from bandwidth limited clients will be put into the last adaptive QOS category, which itself is bandwidth limited. That last QOS category does not contain unidentified traffic anymore, so now in essence you have bandwidth limiting being done for clients but their traffic is not category prioritized the same as non-limited traffic. It's a hybrid system where you get EITHER/OR.
Now with RMerlin's TC interposer, it is possible to permanently change the TC class structure, something which was locked down before. If you modify his interposer, you can create a fully meshed adaptive QOS & bandwidth limited system. I am not going to be looking into that modification right now as a more pressing issue exists within the existing QOS system I would like to fix. I will attach a picture of what needs to be done if someone wants to purse it themselves.
Top is original QOS
Middle is the hybrid implemented in my script
Bottom is what now is possible with the TC interposer
Attachments
Last edited: