D-Link QOS Setup

[kaspro]

Hello everyone, I'm trying to setup QOS on my D-LINK router but it seems there's no manual for it anywhere, every guide i find has different interface and different fields!

Here's image for my router qos interface, and i'm trying to set it up for gaming

 

[bill001g]

Almost everything on that screen is completely worthless. Anything related to DSCP or precedence is stripped off by the ISP. If you could give you data priority everyone would just set their traffic to the highest so all ISP completely remove it.

What are you trying to accomplish. This router like many can only apply QoS to UPLOAD bandwidth. Almost everyone problem is on the DOWNLOAD side.

You would need a router that can limit data rates both upload and download rates to fixed values.

You may be better off talking to the other users in your house about limiting their usage. QoS is not some magic bandwidth increase it purely decides who is not going to get to use the bandwidth you purchase. You may feel your game traffic is more important but someone watch netflix will feel the same. So it may be simpler to just get a agreement that other people do not do certain things when you are playing games. QoS is just a electronic enforcement of that agreement.

You will likely need a different router if you really want to do QoS.

 

[failboat]

This might be PRIQ if it has priority levels.

Queue based QoS is pretty bad for gaming. I wouldn't recommend it.

You're going to need to know the default for any. It's probably *.

If you want a specific device to have a queue you make the source ip specific and everything else * from the LAN port.
To make only certain traffic from a specific place do the same above but put a port on destination.
Source ports should always be any on the LAN.

I wouldn't recommend anything on the WAN side. Unless you are port forwarding you won't have any WAN connections really.

You can't control how UDP comes in really, but TCP relies on acknowledgement packets. So when it's slowed down new packets aren't sent until the acknowledgement is sent back for prior packets. In general you want UDP and Acknowledgement to be high priority. UDP will sit in queue if your backed up.

Pipes (throttling) allow you to make sure gaming has some bandwidth. It's inefficient, but effective. HFSC has better settings for low latency queue based applications than other queue based options, but it's very hard to setup. CODEL can be added to most queues which drops packets when the queue is backed up. It can backfire if it's on TCP. Because then they keep getting resent.

 

[failboat]

One thing I have been considering is putting all stream, web and DL based traffic into one pipe with most of the bandwidth and using queue based on that, and then a small portion for gaming starting around 5Mbs per user in another pipe.

This will make your downloads slower all the time, even when not gaming, but it will ensure that gaming always works. Queues for streaming and downloading work very well.
My current connection is a little too slow to partition out.