I been testing MikroTik for a while and discovered that MikroTik doesn’t “catch” all p2p traffic.
I made simple test. Added rule to forward chains that drop all know p2p traffic. Most p2p traffic stopped but some users still had running p2p taking all available bandwitdth. I think this is p2p becouse most common TCP ports to wchich clients where connecting where 2234 (default used by SoulSeek) and 6881,6882,688x (default used by BitTorrent)
What do you think about that?!
P.S.
If someone would like more info I can send logs or even whole “catched” TCP packets.
The same happens to me.
I created a mangle at the end catching all the rest (after mangling all known traffic like http/s,ftp,dns, p2p etc..).
Then you limit (for instance to 75kb/s) this traffic to each user.
In this way you limit the traffic and if they have to use a not known (mangled) traffic, they just have to stop the p2p.
I forgot to say that as I suppose that p2p is recognised through patterns on the packets, we all should post our info (which programs etc..) and also copy it to support@mikrotik.com
in this way they can test it, find the pattern, append it in the code and include in the new release.
In my case, some of my customers using azureus are correctly mangled, and some of them escape the mangle, which is even more strange.
When you add a rule in the forward chain that should drop p2p traffic then note that it will start to work on the new p2p connections - already created p2p connections will not be dropped. You can reboot the router so it will clear all the connections, that could help you.
The best way to avoid that is to add a mangle rule which marks all p2p traffic and then later if you want, you can use this flow to limit speed, to use in the firewall, etc.
but what i am seeing is that also after rebooting, or is pc connects after router is rebooted, some p2p programs are not recognised.
We have a clear case with a program called azureus, upload is not limited (or not well mangled …)
About the p2p we have 2 users using a client of bit torrent called BitComet.
Apparently this is recognised as p2p (but not sure) but then when shaping the traffic (for instance it is limited to 180 Kb/s and works for all other clients), these 2 clients can download at 700 or more Kb/s. No way to limit the bandwidth. I see thet Bit Comet is not in your bittorrent list of p2p programs
Some users work with Morpeus