as you probably know, comcast (and other isp) uses "sandvine" which sends fake tcpip-reset-packages to both peers to prevent users from seeding. but it usually takes between 20 and 60 seconds till a connection gets lost. if you "manually announce" right after that happens, the connection is back on for another 20 to 60 seconds. you can do that again and again.

i suppose that it isn't important to re announce to the tracker, but it would be enough to merely try to reestablish the connection to the other peer.

it would be pretty cool if ktorrent tried to reconnect (just one time) whenever the connection to a peer is lost. it brings a little more overhead but might be the simplest way to get around sandvine.

From what I remember, if you were to force encryption on all your torrents, sandvine won't work.

But I am not sure if George would be willing to add this, as I don't believe it is referenced in the bittorrent spec.

(1) My tests with sandvine shows that it totally looks through encryption without a care.

(2) I do not support the OP's idea -- it violates netiquette for torrent clients. If I close a connection, the remote side should respect that, not spam me back a afew reconnect requests. That goes against all good-behavior-rules I know of.

There's already TCP reset guards at the iptable level that one can invoke (that still are bad netiquette) so I dont' see the merit of torrent clients bending over backwards for one assinine ISP.

jdong wrote:not spam me back a afew reconnect requests. That goes against all good-behavior-rules I know of.

I agree, and i know transmission does this connection check every x seconds.