What you said is definitely bad - or my description was not too good: "with high pps and not high bandwidth"Hello,
if you are using mikrotiks on client side, then configure these as routers and add simple queues.
so you will limit max throughput on client side. This is most effective solution.
I already have burst queues set to each user, and that limits both up and down. Queueing method used is "pfifo" with around 100packets in queue.Limit maximum upload speed to hinder sending traffic that would be otherwise thrown away when reaching where you normally limit bandwidth (i.e. pppoe server). Make sure you properly size queue type so you don't create high latency.
Then for the specific answer to your question, use a firewall rule in forward chain with "limit" match to limit the packets per second. Look up "limit" in firewall filter wiki.
Try to research torrent client behavior with packet sniffer and you will see, that it receives data with large packetsize.What you said is definitely bad - or my description was not too good: "with high pps and not high bandwidth"
drop torrents at all??is there any known way to get desired effect?
/ ip firewall filter add chain=forward action=drop protocol=udp dst-port=!53 connection-limit=3,32 comment="UDP Conn Limit" add chain=forward action=drop tcp-flags=syn protocol=tcp dst-port=1024-65535 connection-limit=10,32 comment="High Port Conn Limit" add chain=forward action=drop tcp-flags=syn protocol=tcp dst-port=80 connection-limit=40,32 comment="Port 80 Conn Limit" /
Sadly i have a bunch of customers with badly configured torrent clients, so they are overloading the sector with high number of packet/sec with low frame size.
(yes, we can tell them, they have no more download speed if they download by 10 streams or 100 streams - but the latter one highly degrades whole sector, even using NV2)
I don't care what gentle users do, but i hate P2P traffic kills sector (with high pps and not high bandwidth) with bad configuration/stupid user.
I know, i can mark P2P packets, but it seems, i cannot limit it properly per user.
Any ideas would be welcome, especially a solution what can be installed on client CPE (mikrotik) what limits ~100pps in each direction (i can change for all traffic or only p2p).
Well, this sector running NV2. Yes, small rise in latency - or even bigger latency in case of bigger tdma period (but that causes higher thruput as well). I think if one CPE is responsible for ~25% of packet/s on sector, that would affect others. I think, polling gives no equal "airtime" for CPEs.Can you confirm that NV2 is affected badly, I would expect a small rise in latency but not so bad as to effect the user experience. TDMA should not allow a single node to take control of the AP like this