I second that

the idea is to get those files outside to populate local seeds for faster distribution.

Modding torrent client to give upload priority to local IPs is also a good idea, that way we dont have to mess ourselves having the local torrent tracker getting busted by copyright enforcers.

This post has been edited by strace: Sep 26 2006, 02:52 PM

there is no need to inspect every packet, the hardware just need to monitor connection behaviours for each IPs e.g. having 300 active connections with new 20 connections per 10 seconds will grant you a speed limit.

Anyone wants to setup a massive 500 terabyte p2p cache server? XD

modify torrent clients to give higher priority to local, encourage everyone to use it.

When you're downloading torrent through VPN, proxy and so on, you are actually making a single connection to a server. It doesn't matter if you're connecting to a local or a international server as long as you dont make too many connections. When you're established too many active connections, the device will flag you as a p2p user & throttle every connections. Other solutions are rent a server from TMnet's server farm & install a web based client, from there you can download them through http/ftp. There is a site that also provide such service with a little to no cost - http://66.90.101.200/

This post has been edited by strace: Oct 12 2006, 10:38 AM

There is nothing to do with encryption protocol whatsoever. The traffic shaping hardware monitors traffic patterns & flags multi active connections as p2p. BT clients to work with the hardware is NOT a peer-to-peer software anymore.

lol someone is already ahead of me

Hi again, I got a simple theory about escaping torrent shaping without tunneling. From my observation, what you need to do is
a) forward port below 1024 range, use port 25,80,88,110 just to be safe
b) decrease p2p connection timeout below 30 seconds, I'll set mine at 20 secs
c) do not use forced mode for BT encryption it will get you less peers, just leave it default. AFAIK the tc device is not capable of layer 7 deep packet inspection. Besides it doesn't make any difference protocol encryption or not, it control based on initiated connections count. When your connection hits the count limit, you'll get lame speed.

I'll try these settings for a few days & see how it goes.

I am using utorrent and has that feature hidden in the advanced menu, but i think BC should this feature too. The idea is to emulate like a real web/whatever server, but i am just as afraid that the tc device will mark you through the 1st connection with the trackers e.g. having a tracker monitor bot to check when you initiating connection to popular tracker port numbers. So later on I'll put a http proxy when connecting to a tracker

This is just theory & currently under testing. I'll keep on tweaking until I got some results.

not that, but for that setting IMO is better set at a larger number e.g. 500 or 1000

Maybe BC doesn't have this setting after all
if your connection is unthrottled then leave it at 100ms