[Release] FreshJR Adaptive QOS (Improvements / Custom Rules / and Inner workings)

[FreshJR]

@everybody Dont worry about messages HTB: quantum of class .... etc.

@pattiri I'm glad it started working again. I haven't updated to the latest firmware yet.

I don't completely understand what your Script does after reading through the whole thread so I wanted one question:

You wrote that it changes the guaranteed minimum speeds of various categories, but that would mean setting the max for all the catogries at the same time if all minima add up to 100%. (if the sum of the minimum speeds is 100% of the bandwidth that would mean that minimum = max, as the bandwidth would be distributed over all the categories)
Am I misunderstanding that?

First off, thanks for reading the thread entire thread before asking. As user strangeluck has replied, the minimum per categories only apply IF you are out of the total bandwidth for QOS.

When you are out of bandwidth, each category will have will receive at least its minimum bandwidth IF it needs it. For categories that are using nothing or need less than the minimum guaranteed bandwidth, ALL excess bandwidth will be offered to categories from TOP to BOTTOM.

Example1:
Web Surfing, priority 1, has 10mbps minimum / 100 total, you are using 5mbps
Streaming, priority 2, has 20mbps minimum / 100 total, you are watching a 30mbps stream
Downloads, priority 3, has 40mbps minimum / 100 total, you are downloading from 1gbps server.

What would happen is as follows:

Web Surfing 5mbps used
Streaming 30 mbps used
Downloads 65 mbps used

Example2:
Looking, the numbers at the limits below, you can see they are very similar to the above, but the priorities are different.
Web Surfing, priority 1, has 10mbps minimum / 100 total, you are using 5mbps
Downloads, priority 2, has 40mbps minimum / 100 total, you are downloading from 1gbps server.
Streaming, priority 3, has 20mbps minimum / 100 total, you are watching a 30mbps stream

What would happen is as follows:

Web Surfing 5mbps used
Downloads 75mbps used
Streaming 20mbps used

So dont worry nothing is wasted.

Example3:
Now very important, if each catagory had a minimum bandwidth of 0.125 mbps as out of the box, the original qos feature would do as follows.

Web Surfing, priority 1, has 0.125 mbps minimum / 100 total, you are using 5mbps
Streaming, priority 2, has 0.125 mbps minimum / 100 total, you are watching a 30mbps stream
Downloads, priority 3, has 0.125 mbps minimum / 100 total, you are downloading from 1gbps server.

Web Surfing 5 mbps used
Downloads 94.875 mbps used
Streaming 0.125 mbps used



This is why I wanted to get unclassified traffic away from the last catagory SINCE my VOIP was unclassfied and would get 0.125mbps while netflix/youtube ate my internet. With minimums it is not required to move unclassified traffic higher, but I like it, because it then gets offered bandwidth first which equals less latency.

how does this affect qos over all, does just provide better bandwith divison for all categories of traffic?

This is kind of disrespectful. In the original post I directed you to check out post 23/24 for very in depth information.

https://www.snbforums.com/threads/s...ied-traffic-priority.36836/page-2#post-305353

Provided examples of how adaptive QOS works out of the box. So what my script does is changes the terrible minimum bandwidths, and allows to you reroute all unclassified traffic that normally goes into the "Default" container into the "Others" container which then has a modifiable priority in the web browser UI.

 

[Vexira]

@everybody Dont worry about messages HTB: quantum of class .... etc.

@pattiri I'm glad it started working again. I haven't updated to the latest firmware yet.



First off, thanks for reading the thread entire thread before asking. As user strangeluck has replied, the minimum per categories only apply IF you are out of the total bandwidth for QOS.

When you are out of bandwidth, each category will have will receive at least its minimum bandwidth IF it needs it. For categories that are using nothing or need less than the minimum guaranteed bandwidth, ALL excess bandwidth will be offered to categories from TOP to BOTTOM.

Example1:
Web Surfing, priority 1, has 10mbps minimum / 100 total, you are using 5mbps
Streaming, priority 2, has 20mbps minimum / 100 total, you are watching a 30mbps stream
Downloads, priority 3, has 40mbps minimum / 100 total, you are downloading from 1gbps server.

What would happen is as follows:

Web Surfing 5mbps used
Streaming 30 mbps used
Downloads 65 mbps used

Example2:
Looking, the numbers at the limits below, you can see they are very similar to the above, but the priorities are different.
Web Surfing, priority 1, has 10mbps minimum / 100 total, you are using 5mbps
Downloads, priority 2, has 40mbps minimum / 100 total, you are downloading from 1gbps server.
Streaming, priority 3, has 20mbps minimum / 100 total, you are watching a 30mbps stream

What would happen is as follows:

Web Surfing 5mbps used
Downloads 75mbps used
Streaming 20mbps used

So dont worry nothing is wasted.

Example3:
Now very important, if each catagory had a minimum bandwidth of 0.125 mbps as out of the box, the original qos feature would do as follows.

Web Surfing, priority 1, has 0.125 mbps minimum / 100 total, you are using 5mbps
Streaming, priority 2, has 0.125 mbps minimum / 100 total, you are watching a 30mbps stream
Downloads, priority 3, has 0.125 mbps minimum / 100 total, you are downloading from 1gbps server.

Web Surfing 5 mbps used
Downloads 94.875 mbps used
Streaming 0.125 mbps used



This is why I wanted to get unclassified traffic away from the last catagory SINCE my VOIP was unclassfied and would get 0.125mbps while netflix/youtube ate my internet. With minimums it is not required to move unclassified traffic higher, but I like it, because it then gets offered bandwidth first which equals less latency.



This is kind of disrespectful. In the original post I directed you to check out post 23/24 for very in depth information.

https://www.snbforums.com/threads/s...ied-traffic-priority.36836/page-2#post-305353

Provided examples of how adaptive QOS works out of the box. So what my script does is changes the terrible minimum bandwidths, and allows to you reroute all unclassified traffic that normally goes into the "Default" container into the "Others" container which then has a modifiable priority in the web browser UI.

How is it disrespectful, I never insulted anyone plus that's a false accusation, also Im trying to full understand how this works exactly that's all, since I've been debating someone about qos, and it's uses. Also kudos to you for creating the script I hope it ends up in the official firmware. By no means am I an expert that's why I asked, I apologise if I missed your explanation in a prior post, I meant to ask in the situations if you were to start an online game how would the script handle the band with, since every game is different or is that handled by default qos, settings since in your examples their is little mention of such things I'm just wondering, cause I've noticed that steam downloads, and xbox one game downloads seem to drain my bandwidth, I just wanted to know, cause I'm really thinking about using your script, to see if it helps my case, especially when my network is somewhat congested.

 

[FreshJR]

How is it disrespectful, I never insulted anyone plus that's a false accusation, also Im trying to full understand how this works exactly that's all, since I've been debating someone about qos, and it's uses. Also kudos to you for creating the script I hope it ends up in the official firmware. By no means am I an expert that's why I asked, I apologise if I missed your explanation in a prior post, I meant to ask in the situations if you were to start an online game how would the script handle the band with, since every game is different or is that handled by default qos, settings since in your examples their is little mention of such things I'm just wondering, cause I've noticed that steam downloads, and xbox one game downloads seem to drain my bandwidth, I just wanted to know, cause I'm really thinking about using your script, to see if it helps my case, especially when my network is somewhat congested.

So the adaptive QOS built into the router does the actual packet identifying. To be more specific it is done by Trend Micro, a company ASUS reached an agreement with, instead of ASUS. My script just tweaks the sorted packets priorities to behave a little more reasonably.

With the adaptive QOS implementation, all traffic packets get be prioritized from top to bottom catagories. The top catagory packets get first priority to get processed (meaning lower latency) while bottom category packets get process last priority, even get dropped and have to be resubmitted again if you are out of bandwidth (meaning higher latency). QOS will not magically give you more bandwidth.

For gaming priority, you are at the mercy of the trend micro definitions to identify your traffic correctly. So two scenarios:

1) Gaming traffic is identified correctly and follows its priority order
2) Gaming traffic is unclassified and sent into last catagory and getting worst priority *TERRIBLE*.

Albeit with my script, in example 2 instead of having unclassified traffic always going to last priority, it will go to the others catagory priority, which is user definable, so you can modify that to your liking.

Looking at my post post you quoted above, you can see the difference between my scripts modifications in examples 1&2, vs's ASUS default's implementation behavior in example3. With my adjusted minimum guarenteed bandwidths, even packets in the last categories will not be treated too roughly. Cmon 0.125mbps max implemented limit for all unclassied traffic if youtube can eat all available bandwidth to stream 4k?!?!?!?

With that logic, Asus's implementation would KILL your gaming experience if that gaming traffic was unidentified during moments of constrained bandwidth.

I cannot explain this in any other words. Someone else is free to write up more.

 

[Vexira]

Wow, thnx for the explantion it makes a hell of alot more sense now, ill see about loading your script might fix my net work weirdness.

 

[MarioCaires]

Thanks FreshJR, you've made an awesome script! Started using it today and QoS is now perfect on my side...
With the original adaptive QoS I used to have buffering issues with my IPTV service when downloading torrents, I have already tried to download some torrents and no buffering until now!

 

[Vexira]

Loaded your script last night its worling well, pretty solid wish is was a part of the firmware, keep up the good work, had the htb: quantom thing show up in the log, but its dissapeard so it msut of fixed its self, read the posts on it, so i guess its just hapens the first time, then corrects its self.

 

[Vexira]

i wish the script was included as part of the 88u firmware, had a werid error after flashing 380.67 aplha 1 so i reset the router to default, then relaoded the script.

 

[MarioCaires]

Thanks for the awesome script, it is an upgrade over the native QoS! However can't make it work as intended when downloading torrents...
I haven't touched the script so I'm using default parameters and in the GUI I have configured manual download/upload speeds with "Video Audio streaming" category with highest priority as I am using an IPTV service. I have also configured "Others" and "File transferring" with lowest priority so when I'm downloading torrents I have enough bandwidth for the IPTV. The IPTV is correctly identified as "Video and audio streaming" and torrents are identified partially correct with around 50% of the traffic as "Others" and the other 50% as "File transferring", however that's fine as I have both categories in the lowest priority anyway.
The problem rises when I start downloading a torrent and the IPTV starts freezing/buffering... I already tried to limit number of connections in the torrent client but looks like nothing makes a difference, other than limiting the download speed which defeats the reason to be using QoS in the first place!

Anyone else with same issue? Is there a solution for this other than stopping the torrents or limiting the download speed manually?
Would appreciate any insight over this.
Thanks in advance

 

[Vexira]

Thanks for the awesome script, it is an upgrade over the native QoS! However can't make it work as intended when downloading torrents...
I haven't touched the script so I'm using default parameters and in the GUI I have configured manual download/upload speeds with "Video Audio streaming" category with highest priority as I am using an IPTV service. I have also configured "Others" and "File transferring" with lowest priority so when I'm downloading torrents I have enough bandwidth for the IPTV. The IPTV is correctly identified as "Video and audio streaming" and torrents are identified partially correct with around 50% of the traffic as "Others" and the other 50% as "File transferring", however that's fine as I have both categories in the lowest priority anyway.
The problem rises when I start downloading a torrent and the IPTV starts freezing/buffering... I already tried to limit number of connections in the torrent client but looks like nothing makes a difference, other than limiting the download speed which defeats the reason to be using QoS in the first place!

Anyone else with same issue? Is there a solution for this other than stopping the torrents or limiting the download speed manually?
Would appreciate any insight over this.
Thanks in advance

which router are you using and is your signature database the latest version. You could try custom priroties and put torrents at the lowest priotity

 

[MarioCaires]

I'm using an AC87 and my signature is updated! Looks like my issue is quite intermittent, sometimes works perfectly and then sometimes just doesn't and when downloading torrents, doesn't give enough bandwidth to IPTV.

However today just found another issue, not sure if it is just me but everytime I press "check" for update signature (even w/o new signature) some traffic starts being counted as "Default" when was supposed to be on "Other"...
Anyone else with same issue?

 

[FreshJR]

I'm using an AC87 and my signature is updated! Looks like my issue is quite intermittent, sometimes works perfectly and then sometimes just doesn't and when downloading torrents, doesn't give enough bandwidth to IPTV.

However today just found another issue, not sure if it is just me but everytime I press "check" for update signature (even w/o new signature) some traffic starts being counted as "Default" when was supposed to be on "Other"...
Anyone else with same issue?

Yes when upgrading or checking the definations, the script rules are overwritten. That being said, the script does check if its persistent once every 24hrs for uncaught changes, such as that one.

So there will be small holes in coverage when that check is executed, upto 24hrs worst case scenario. These definition updates/checks are so infrequent at the present moment that I feel like adding the additional complexity to catch the definition update and restart the script immediately is not worth it. If it becomes a problem I will look into it.

Are your QOS limit are set correctly? They should ideally be 80-90% of your max speeds. Check your buffer bloat (ping difference between unsaturated and saturated internet usuage).

Start a ping test from router GUI, then run a speedtest on the computer, and observe the changes.

If you get bufferbloat, your QOS limits are too high.

Example1: Proper QOS Limits

PING www.google.com (172.217.6.4): 56 data bytes
--DOWNLOAD
64 bytes from 172.217.6.4: seq=0 ttl=55 time=9.689 ms
64 bytes from 172.217.6.4: seq=1 ttl=55 time=11.491 ms
64 bytes from 172.217.6.4: seq=2 ttl=55 time=17.030 ms
--UPLOAD
64 bytes from 172.217.6.4: seq=3 ttl=55 time=65.780 ms
64 bytes from 172.217.6.4: seq=4 ttl=55 time=64.809 ms
64 bytes from 172.217.6.4: seq=5 ttl=55 time=40.545 ms
64 bytes from 172.217.6.4: seq=6 ttl=55 time=17.518 ms
64 bytes from 172.217.6.4: seq=7 ttl=55 time=31.090 ms
64 bytes from 172.217.6.4: seq=8 ttl=55 time=15.912 ms
64 bytes from 172.217.6.4: seq=9 ttl=55 time=13.178 ms
64 bytes from 172.217.6.4: seq=10 ttl=55 time=17.918 ms
64 bytes from 172.217.6.4: seq=11 ttl=55 time=16.730 ms
64 bytes from 172.217.6.4: seq=12 ttl=55 time=28.671 ms
64 bytes from 172.217.6.4: seq=13 ttl=55 time=14.431 ms
--IDLE
64 bytes from 172.217.6.4: seq=14 ttl=55 time=18.044 ms
64 bytes from 172.217.6.4: seq=15 ttl=55 time=18.633 ms
64 bytes from 172.217.6.4: seq=16 ttl=55 time=15.667 ms
64 bytes from 172.217.6.4: seq=17 ttl=55 time=11.422 ms
64 bytes from 172.217.6.4: seq=18 ttl=55 time=14.877 ms
64 bytes from 172.217.6.4: seq=19 ttl=55 time=13.132 ms
64 bytes from 172.217.6.4: seq=20 ttl=55 time=13.748 ms
64 bytes from 172.217.6.4: seq=21 ttl=55 time=17.435 ms

Example2: QOS Upload Limit too high

PING www.google.com (172.217.8.196): 56 data bytes

---IDLE NETOWRK
64 bytes from 172.217.8.196: seq=0 ttl=55 time=14.557 ms
64 bytes from 172.217.8.196: seq=1 ttl=55 time=12.401 ms
64 bytes from 172.217.8.196: seq=2 ttl=55 time=11.730 ms
64 bytes from 172.217.8.196: seq=3 ttl=55 time=14.205 ms
64 bytes from 172.217.8.196: seq=4 ttl=55 time=16.749 ms
64 bytes from 172.217.8.196: seq=5 ttl=55 time=11.066 ms
---DOWNLOAD 
64 bytes from 172.217.8.196: seq=6 ttl=55 time=12.373 ms
64 bytes from 172.217.8.196: seq=7 ttl=55 time=12.082 ms
64 bytes from 172.217.8.196: seq=8 ttl=55 time=16.914 ms
64 bytes from 172.217.8.196: seq=9 ttl=55 time=15.925 ms
64 bytes from 172.217.8.196: seq=10 ttl=55 time=14.089 ms
64 bytes from 172.217.8.196: seq=11 ttl=55 time=12.822 ms
64 bytes from 172.217.8.196: seq=12 ttl=55 time=15.826 ms
64 bytes from 172.217.8.196: seq=13 ttl=55 time=14.805 ms
64 bytes from 172.217.8.196: seq=14 ttl=55 time=16.958 ms
64 bytes from 172.217.8.196: seq=15 ttl=55 time=14.461 ms
64 bytes from 172.217.8.196: seq=16 ttl=55 time=18.036 ms
---UPLOAD 
64 bytes from 172.217.8.196: seq=17 ttl=55 time=558.061 ms
64 bytes from 172.217.8.196: seq=18 ttl=55 time=419.164 ms
64 bytes from 172.217.8.196: seq=19 ttl=55 time=455.794 ms
64 bytes from 172.217.8.196: seq=20 ttl=55 time=283.671 ms
64 bytes from 172.217.8.196: seq=21 ttl=55 time=299.310 ms
64 bytes from 172.217.8.196: seq=22 ttl=55 time=321.351 ms
64 bytes from 172.217.8.196: seq=23 ttl=55 time=405.454 ms
64 bytes from 172.217.8.196: seq=24 ttl=55 time=248.077 ms
64 bytes from 172.217.8.196: seq=25 ttl=55 time=317.145 ms
64 bytes from 172.217.8.196: seq=26 ttl=55 time=448.541 ms
64 bytes from 172.217.8.196: seq=27 ttl=55 time=363.089 ms
64 bytes from 172.217.8.196: seq=28 ttl=55 time=267.759 ms
64 bytes from 172.217.8.196: seq=29 ttl=55 time=395.498 ms
64 bytes from 172.217.8.196: seq=30 ttl=55 time=316.250 ms
64 bytes from 172.217.8.196: seq=31 ttl=55 time=380.576 ms
---IDLE
64 bytes from 172.217.8.196: seq=32 ttl=55 time=12.621 ms
64 bytes from 172.217.8.196: seq=33 ttl=55 time=17.697 ms
64 bytes from 172.217.8.196: seq=34 ttl=55 time=15.036 ms
64 bytes from 172.217.8.196: seq=35 ttl=55 time=14.115 ms
64 bytes from 172.217.8.196: seq=36 ttl=55 time=17.082 ms
64 bytes from 172.217.8.196: seq=37 ttl=55 time=9.976 ms
64 bytes from 172.217.8.196: seq=38 ttl=55 time=13.063 ms
64 bytes from 172.217.8.196: seq=39 ttl=55 time=13.915 ms
64 bytes from 172.217.8.196: seq=60 ttl=55 time=18.812 ms
64 bytes from 172.217.8.196: seq=61 ttl=55 time=15.355 ms

Example 3: Download and Upload limit too high

PING www.google.com (172.217.6.100): 56 data bytes
--IDLE 
64 bytes from 172.217.6.100: seq=0 ttl=55 time=9.985 ms
64 bytes from 172.217.6.100: seq=1 ttl=55 time=10.773 ms
64 bytes from 172.217.6.100: seq=2 ttl=55 time=11.014 ms
64 bytes from 172.217.6.100: seq=3 ttl=55 time=12.617 ms
64 bytes from 172.217.6.100: seq=4 ttl=55 time=12.280 ms
64 bytes from 172.217.6.100: seq=5 ttl=55 time=10.144 ms
64 bytes from 172.217.6.100: seq=6 ttl=55 time=13.029 ms
64 bytes from 172.217.6.100: seq=7 ttl=55 time=9.914 ms
64 bytes from 172.217.6.100: seq=8 ttl=55 time=13.642 ms
64 bytes from 172.217.6.100: seq=9 ttl=55 time=16.701 ms
64 bytes from 172.217.6.100: seq=10 ttl=55 time=11.729 ms
64 bytes from 172.217.6.100: seq=11 ttl=55 time=36.493 ms
64 bytes from 172.217.6.100: seq=12 ttl=55 time=57.648 ms
64 bytes from 172.217.6.100: seq=13 ttl=55 time=57.926 ms
64 bytes from 172.217.6.100: seq=14 ttl=55 time=78.678 ms
--DOWNLOAD 
64 bytes from 172.217.6.100: seq=15 ttl=55 time=111.477 ms
64 bytes from 172.217.6.100: seq=16 ttl=55 time=147.228 ms
64 bytes from 172.217.6.100: seq=17 ttl=55 time=201.513 ms
64 bytes from 172.217.6.100: seq=18 ttl=55 time=260.241 ms
64 bytes from 172.217.6.100: seq=19 ttl=55 time=329.768 ms
64 bytes from 172.217.6.100: seq=20 ttl=55 time=400.403 ms
64 bytes from 172.217.6.100: seq=21 ttl=55 time=473.105 ms
64 bytes from 172.217.6.100: seq=22 ttl=55 time=553.243 ms
64 bytes from 172.217.6.100: seq=23 ttl=55 time=513.880 ms
64 bytes from 172.217.6.100: seq=24 ttl=55 time=464.485 ms
64 bytes from 172.217.6.100: seq=25 ttl=55 time=271.183 ms
64 bytes from 172.217.6.100: seq=26 ttl=55 time=166.159 ms
64 bytes from 172.217.6.100: seq=27 ttl=55 time=313.623 ms
--UPLOAD 
64 bytes from 172.217.6.100: seq=28 ttl=55 time=81.997 ms
64 bytes from 172.217.6.100: seq=29 ttl=55 time=356.329 ms
64 bytes from 172.217.6.100: seq=30 ttl=55 time=444.495 ms
64 bytes from 172.217.6.100: seq=31 ttl=55 time=493.655 ms
64 bytes from 172.217.6.100: seq=32 ttl=55 time=483.916 ms
64 bytes from 172.217.6.100: seq=33 ttl=55 time=183.735 ms
64 bytes from 172.217.6.100: seq=34 ttl=55 time=371.243 ms
64 bytes from 172.217.6.100: seq=35 ttl=55 time=276.262 ms
64 bytes from 172.217.6.100: seq=36 ttl=55 time=492.085 ms
64 bytes from 172.217.6.100: seq=37 ttl=55 time=460.454 ms
64 bytes from 172.217.6.100: seq=38 ttl=55 time=513.983 ms
64 bytes from 172.217.6.100: seq=39 ttl=55 time=574.377 ms
64 bytes from 172.217.6.100: seq=40 ttl=55 time=519.698 ms
64 bytes from 172.217.6.100: seq=41 ttl=55 time=363.752 ms
--IDLE 
64 bytes from 172.217.6.100: seq=42 ttl=55 time=11.036 ms
64 bytes from 172.217.6.100: seq=43 ttl=55 time=13.753 ms
64 bytes from 172.217.6.100: seq=44 ttl=55 time=17.516 ms
64 bytes from 172.217.6.100: seq=45 ttl=55 time=12.449 ms
64 bytes from 172.217.6.100: seq=46 ttl=55 time=14.458 ms
64 bytes from 172.217.6.100: seq=47 ttl=55 time=10.606 ms
64 bytes from 172.217.6.100: seq=48 ttl=55 time=15.288 ms
64 bytes from 172.217.6.100: seq=49 ttl=55 time=10.731 ms

If your pings are spiking, then you gotta fix your limits before QOS starts working properly.
If your limits are set low, and your pings are spiking, then I there is one other thing we can check.

 

[Vexira]

So adatpive qos needs to have bandwidth set that way to prevent buffer bloat? Would need to set it that way, since i have a 100/40 (95/37 actuall bandwidth) connection on vdsl2. So is it 80% download 90% up or both at 80% or 90%. i read a bit on it bu i could never understand the right way to do it since some guides had conflicting information or were just a bit vauge, i also was under the impresson that adaptive qos does it automatically though easily i could be wrong.
I just want to have every thing set up propperly, sorry if you've answered this else where, sincve all the things i read no one had an exact guide for adaptive qos, most of it was for traditional qos.

 

[MarioCaires]

Thanks @FreshJR, I have changed my download limit to a lower value to around 93% and it seems to be enough not to interrupt my IPTV service when downloading! Finally working as is supposed to.

@Vexira the Download/Upload bandwidth limit may vary between different user and connection scenarios, in my situation I have found (at least for now) that 90% of 62Mbps (which is my current ISP Download) is too low so I have it set to 58Mbps atm and no issues so far!

 

[FreshJR]

Correct. The automatic setting does not work. Do not use it.

For working QOS you have to manually define your limits in the web interface.

It is 80-90% of actual speeds on both upload and download. It varies between ISPs. Experiment with values while checking your buffer bloat.

If your lazy set it to 80% and call it a day.

For me I got away with 93% on download but fell all the way to 80% on upload.

Just in case it is not apparent, DO NOT input percents into the interface. It takes values in mbps.

Thanks @FreshJR, I have changed my download limit to a lower value to around 93% and it seems to be enough not to interrupt my IPTV service when downloading! Finally working as is supposed to.

@Vexira the Download/Upload bandwidth limit may vary between different user and connection scenarios, in my situation I have found (at least for now) that 90% of 62Mbps (which is my current ISP Download) is too low so I have it set to 58Mbps atm and no issues so far!

Is your IPTV service operating on a specific port? I can give u a custom version that puts your IPTV into the video streaming catagory if it is not properly identified. If both your video and torrent traffic is being unclassified, that's a subpar situation (and the original reason) why i made this thread

 

[fearz]

Hi,

Would your script solve the issue when windows 10 updates start, i have video streaming set to #1 priority, however when windows update starts, it gets prioritized even above video streaming...this has really bothered me, would this fix it?






Sent from my iPhone using Tapatalk

 

[FreshJR]

Hi,

Would your script solve the issue when windows 10 updates start, i have video streaming set to #1 priority, however when windows update starts, it gets prioritized even above video streaming...this has really bothered me, would this fix it?






Sent from my iPhone using Tapatalk

Yes as long as windows update and video streaming are not identified into the same category.

 

[MarioCaires]

Is your IPTV service operating on a specific port? I can give u a custom version that puts your IPTV into the video streaming catagory if it is not properly identified. If both your video and torrent traffic is being unclassified, that's a subpar situation (and the original reason) why i made this thread

Yes FreshJR, my iptv operates on a specific port and it seems to be correctly identified, just not entirely sure if all the traffic generated is classified under same category "video streaming".
I have noticed that part of the traffic generated by torrents is correctly identified as "file transfer" and other part is unclassified going to "others", I believe that's due to having encryption enabled in the torrent client but if I could classify the traffic by the port that would be awesome and if doesn't hurt, would do the same for the IPTV. [emoji4]


Sent from my Nexus 6P using Tapatalk

 

[Vexira]

hi fresh will you be updating the script due to the 380.67 beta 3 qos changes?

 

[pattiri]

hi fresh will you be updating the script due to the 380.67 beta 3 qos changes?

As I checked his scipt is still working like a charm on 380.67 beta 3

http://prntscr.com/ft33b8

Well may be it need some editing or something I missed. We would be glad if you check it by yourself and be sure if all is OK, fresh

 

[Vexira]

As I checked his scipt is still working like a charm on 380.67 beta 3

http://prntscr.com/ft33b8

Well may be it need some editing or something I missed. We would be glad if you check it by yourself and be sure if all is OK, fresh

Theres a change in quing displine so, i guess it would be wise to make sure every thing is all good.

Also a possible fix for the quantum errors, i hope it helps.
https://community.ubnt.com/t5/EdgeMAX/question-about-smart-queue/td-p/1355738
http://www.linksysinfo.org/index.php?threads/tomato-mod-1-20-8000.26621/page-3#post-125507
http://www.linksysinfo.org/index.ph...is-consider-r2q-change6621/page-3#post-125480