you can limit p2p that way - set bandiwth for http, ftp and other well known protocols and for the rest of traffic set harsh limits so - any unknown protocol will be limited - ares, encrypted bittorent etc.
i can’t even drop Ares… how should I configure MT to drop Ares¿? gimme the syntax. Sorry if it sounds too “pretencioso” (i don’t know how to say that word in english), but i´m really new in MT stuff.
P2P are a headache for networks administrators… and one of the most important feature i see in MT is the ability to detect (drop or control) P2P.
I´m want to migrate to MT.. but first i want to know… Now MT can’t stop one of the most popular p2p clientes … but will stop it one day¿? in future versions…
Normis you tell us that you tested the rule to drop warez… I know the rule must be added and taked to the top of the list, and the router rebooted to it works.
In this case the Ares client never get conected again (in prior versions of ARES)… It`s that the solution?? I must tell you the client still get the download of the queued files, and the problem is not solved, PLEASE TAKE YOUR TIME TEST IT.
You never gonna implement a better solution??? We must drop the ports…? Thanks to Kolo !!!