Tue Jun 07, 2011 4:33 pm
The p2p matcher in RouterOS is out of date and won't match a lot of the more modern protocols. If you try to keep up and match everything p2p, it is an endless battle and one that you will spend a ton of time, effort, and money on.
The easier solution is to just identify the "good" kinds of traffic, and once you have identified what you classify as good, assume everything else is bad and take appropriate steps. For example things that are easy to define, like an HTTP download less than 1MB is more than likely someone just browsing the internet, therefore that connection is good. Where as if that HTTP download grows to be bigger than 1MB, chances are it's someone downloading a file, streaming, etc. so that connection is not as important.
Once you have your traffic classified, set up a queue tree that will take this into account. In a queue tree you specify a minimum amount of bandwidth that something is guaranteed, and the maximum amount of bandwidth you want that class to receive. Priority in there defines what sub-queue will reach max-limit first if there is free bandwidth.