   Setting up QoS properly on my router. Any tips?
  I'm currently setting up QoS on my router because I recently started hosting a server that should require the highest priority over all traffic. I am using a Draytek Vigor 2800G router which has support for QoS.I enabled QoS and set it to 'Both directions', created a new entry with 5% bandwidth reservation(It doesn't eat a lot of bandwidth, it just needs to be routed FAST). I then created the 2 entries for it like:NOStatusLocal AddressRemote AddressDiffServ CodePointService Type1.  Active 192.168.3.3 Any EF Class OTHER_PORT(TCP:1337)2.  Active 192.168.3.3 Any EF Class TELNET(TCP:23)However, even with the EF Class(highest priority), I sometimes get massive slowdowns in traffic. People with a normal ping of 50 to 60, sometimes have pings of up to 450ms.Toolmaker   
  I'm not familiar with this model of router, but I can give some pointersPoint 1. You mention pings are slow, that could be because you aren't prioritising ping traffic. If you want to do this, add in a rule for ICMP traffic to the serverPoint 2. The next bit depends on your router. With QoS, there are two steps. The first is to classify and mark packets - this is what you seem to have done for telnet and port 1337, marking them as EF. Once you have done that, you need to tell the router what to do with packets marked as EF - in this case you say you've given them a 5% bandwidth reservation. Now the next part assumes that on your router traffic marked as EF is placed in the priority queue, and this is not configurable. On some routers you can configure which marking means what, so for example I could have EF traffic as the worst class which gets hardly any bandwidth. Having EF as the priority class is just a recommendation for interoperability between organisations and isn't a hard and fast rule.Bear in mind that in most modern implementations there are two kinds of queues, priority and reserved bandwidth. It sounds like your router is using EF as the priority queue. The priority queue is like a queue jump - traffic entering it will jump ahead of any other packets already in the router waiting to be serialised. Reserved bandwidth queues just reserve the bandwidth without the queue jumpSo assuming that on your router EF is the priority queue, bear in mind that it could (and should) also be getting policed. Policing is when you limit a traffic flow to not go above a certain amount, in this case 5% of the bandwidth. If the amount of traffic does go above 5% any extra traffic gets dropped, and this is what could be happening in your case. This is so priority traffic isn't constantly jumping to the head of the queue and starving out other traffic flows. When you configure a bandwidth amount for a priority queue, you are also implicity policing the queue to that amountPoint 3 is that theres not much point having QoS in both directions, you should only enable it for packets heading outbound. Your router should be fast enough to deal with packets coming inbound from the internet without queueing anything (QoS only takes effect once your router starts having to queue traffic)Finally, bear in mind that you are still subject to what is going on out on the internet. Even if QoS is working perfectly at your end your traffic is still vulnerable to slowdown anywhere along the path to its destination, and that is completely out of your hands. Theres no real way around this for a home user   