Jump to content

Even encrypted connections get disconnected


Recommended Posts

Downloading is fine and some uploading is fine too. Still a lot of clients get disconnected immediately. The lazy bitfield is true and still encrypted connections are disconnected. So the ISP interference should not be the problem.

I have tested this with 1.8.2, 2.2.1, 3.1.2 and the results are the same. I currently have one torrent from private tracker where all peers just connect and disconnect. At least it was easy to test all settings I thought off.

If I resume other torrent some clients will get seeded on that one, so everything should work.

What really happens in the connection. I think it goes like this:

- connecttion

- handshake

- Lazy "I have something... and the all the rest" bitfield exchange

- ... ?

Snippets of log:

[2012-02-15 22:43:04] aaa:55471: Connecting: source: TI

[2012-02-15 22:43:06] aaa:55471: [µTorrent/ (0.0)]: Encrypted handshake completed

[2012-02-15 22:43:06] aaa:55471: [µTorrent 2.2.1 (2.8)]: Disconnect: Connection closed

[2012-02-15 22:43:30] bbb:15648: Connecting: source: T

[2012-02-15 22:43:30] bbb:15648: [µTorrent/ (0.0)]: Encrypted handshake completed

[2012-02-15 22:43:31] bbb:15648: [µTorrent 3.1.2 (0.5)]: Disconnect: Connection closed

[2012-02-15 22:43:47] Incoming connection from ccc:50708

[2012-02-15 22:43:48] ccc:50708: [µTorrent/ (0.0)]: Encrypted handshake completed

[2012-02-15 22:43:53] ccc:50708: [µTorrent/ (0.0)]: Disconnect: Connection closed

Link to comment
Share on other sites

As you can see from the log they are not. And disconnected seeds are reported differently. If you didn't know utorrent reports the completeness like that "[µTorrent 3.1.2 (0.5)]" peer has 0.5 percent of the torrent and seeds are like this "[µTorrent 2.0.4 (100.0)]: Disconnect: Is seed"

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...