I have 192.168.7.0/24 NAT network and I want to limit all P2P.


I try this
/queue simple

add burst-limit=64k/64k burst-threshold=64k/64k burst-time=1m/1m comment="" \
direction=both disabled=no dst-address=0.0.0.0/0 interface=all limit-at=\
64k/64k max-limit=64k/64k name="Limit P2P Download" p2p=all-p2p parent=\
none priority=8 queue=default-small/default-small target-addresses=\
192.168.7.0/24 total-queue=default-small

add burst-limit=64k/64k burst-threshold=64k/64k burst-time=1m/1m comment="" \
direction=both disabled=no dst-address=192.168.7.0/24 interface=all \
limit-at=64k/64k max-limit=64k/64k name="Limit P2P Upload" p2p=all-p2p \
parent=none priority=8 queue=default-small/default-small \
target-addresses=0.0.0.0/0 total-queue=default-small

I see the queue on red but when I test with BitTorrent not really limit the P2P

Please help!

It is not encrypting the traffic is it? Some newer versions encrypt the traffic by default.

How do I know if is encrypting traffic?

The P2P is red but the speed is not limit

encrypted torrent is not detected, I think. also, uTP is unknown too, I believe

Maybe something like this works:
http://wiki.mikrotik.com/wiki/Ares

The p2p matcher in MikroTik is a bit old and does not match nearly all of the p2p programs out there. To keep something like that up to date and accurate would take up way too much time and resources to even begin to be worth it. If you want an appliance that keeps up to date on that kind of stuff, then you really pay for it.

It is much easier for you to assign priority for things that you want and know about, HTTP, HTTPS, VoIP, DNS, etc. and then everything else you don't know about mark it as something else with a lower priority. You can also assign connection-bytes in the mangle rules so that once something like HTTP goes past a download limit you assume that it's a lower priority download, and change it's priority.