FTP has lots of design flaws and not to mention implementation problems, and so does HTTP.
Check out GSTP, http://sf.net/projects/gstp/.
It's TLS-based, and feature-rich.
PacketShaper work entirely by checking the destination ports in the packets. Just change the ports for kazaa and direct connect and your traffic will be classed as "default" instead of peer-to-peer.
Ports to avoid are 1412 for kazaa, and 412-413 for Direct Connect.
Use port 80 or something, and smile:)
At least until someone decides to buy a PacketLogic from Netintact;)
Slashdot Mirror
FTP has lots of design flaws and not to mention implementation problems, and so does HTTP. Check out GSTP, http://sf.net/projects/gstp/. It's TLS-based, and feature-rich.
PacketShaper work entirely by checking the destination ports in the packets. Just change the ports for kazaa and direct connect and your traffic will be classed as "default" instead of peer-to-peer. Ports to avoid are 1412 for kazaa, and 412-413 for Direct Connect. Use port 80 or something, and smile :)
At least until someone decides to buy a PacketLogic from Netintact ;)