Help with DumaOS traffic Prioritization

[Scrizzy]

Love the new DumaOS, router performance, and stability.  However, there seems to be a lot that is now automated and streamlined, which is great for the functionality of the average user.  However, for those that like to tinker, there are a number of things happening under the hood that are harder to decipher. 

 

For example, the traffic prioritization (formerly hyperlane on the R1) has both the "DumaOS classified games" option, as well as a number of additional common profiles (e.g., "skype", "game consoles", some popular games, etc.) already configured.  However, when you choose them, you can not see which actual ports are being configured for prioritization.  So 1) there is no way to tell if all of the correct ports are present and 2) everything contained int the profile is treated as equal traffic.

 

 

I would like to be able to perhaps give traffic from a single port higher priority, or just prioritize upload traffic, etc, rather than ALL traffic from my console (Xbox one in my case).

 

Can anyone give a quick tutorial of how to properly configure the manual prioritization settings under Traffic priority > Add device > Select Device > Advanced

 

 

There's Source (Start-End), and Destination (Start-End) and all fields need to be filled.  Does that mean that I can't prioritize just upload traffic?  Can someone just give an overview and example here, as there doesn't seem to be any instructions on this available.

 

Much appreciated 

[Netduma Iain]

Hi Scrizzy - thanks for purchasing the XR500. You're correct we put a lot of effort into make it much more user friendly. It seems to be working based on our massively reduce support demand but I understand the R1 veterans may need a little explanation.

 

So Traffic Priotisation uses what we call deep packet inspection (DPI). DPI analyses deep into the packets and determines what type of protocol is being run on them. So we can look at the packet exchange and say these first few packets are identical to what a CS:GO connection would do so we'll classify it as CS:GO.

 

DPI is superior to port matching because it has far less false positives. Ports can be used by any application and are often shared between many. When you use port classification like we did on the r1 for hyper-lane you run the risk of prioritising traffic that isn't gaming traffic (or what you were trying to prioritise).

 

So to answer your question is there a way to see if correct ports are present? You can see if we have classified a game by looking at the red LED on the traffic prioritisation feedback panel. It will turn red when it detects high priority traffic. Furthermore you'll see the high priority packets row increasing. If you don't want to use our DPI and pre-classified games you have two options:

1. You can add services based on ports and combine them with our DPI to catch a larger pool of connections
2. Disable DumaOS classified games and put ports in manually. This will behave similar to the R1. We do not recommend this option though. 

For only prioritising a single port on your console simply go for option 2 above. Select the console, then select the advanced menu and enter ports. 

 

It is slightly more flexible than the R1 because we let you set the source port. But in your scenario I would recommend settings source port range 1 - 65535. Then set the destination port in the manner you used to on the R1.

 

Hope that helps

[Scrizzy]

Thank you for the detailed response and insight.  I understand the logic behind these design decisions.  I'm just curious to tinker a bit and see the results

 

 

So to clarify, if for example I wanted to just prioritize outgoing (upload) traffic from port 9999 on the Xbox above all else, I would input

 

Source-

Start: 9999

End : 9999

 

Destination-

Start: 1

End:  65535

 

 

And lastly, does the order of the rules in the prioritization chart reflect the strict priority hierarchy, or are all entries given equal weight?

[Netduma Fraser]

Thank you for the detailed response and insight.  I understand the logic behind these design decisions.  I'm just curious to tinker a bit and see the results

 

So to clarify, if for example I wanted to just prioritize outgoing (upload) traffic from port 9999 on the Xbox above all else, I would input

 

Source-

Start: 9999

End : 9999

 

Destination-

Start: 1

End:  65535

 

And lastly, does the order of the rules in the prioritization chart reflect the strict priority hierarchy, or are all entries given equal weight?

 

Changing the source/destination will not allow you to just prioritise upload/download respectively since you would also be receiving packets from Xbox Live which is download. We fill in the source port as the whole range because change the source ports without being entirely sure of what you're doing will more than likely not have the effect you want to achieve. This is why Iain recommended just changing the destination ports not the source ports.

 

Furthermore consoles don't just use one port when they're online so you would be doing yourself a disservice trying to prioritise manually in this way. The console service has the range of 1024-65535

[Netduma Iain]

Just to add to Frasers post.

 

I'd highly recommended in nearly all scenarios to use source ports 1 - 65535. I believe it automatically fills this in. We only added source porta for ultimate configuration. However 0.1% of people should change default settings.

 

Finally the order of priority list is irrelevant. All have equal weighting.

 

Does that resolve all your queries? If not please don't hesitate to ask