> In case you're not following the upstream ticket:
I'm not; I don't even know where their bug tracker is.
> Would you be able to build libtorrent [1] and rtorrent [2] from source,
> in their latest revision from github, and see if the issue is still
> there?
Done. Exact git commits are
libtorrent ff60f659e3270b995c1df7cec991aec43b62b29f
rtorrent d25c4b25aec09d19ae10941f7e22b97b00a94bfc
I've only let the connection sit choked for 5 minutes or so, but here:
IP UP DOWN PEER CT/RE/LO QS DONE REQ
SNUB FAILED
* 78.180.99.43 0.0 0.0 75.1 r /cn/ci 0/0 16
uTorrent 3.0.0.0
203.161.79.192 0.0 0.0 163.8 r /Cn/cn 0/0 100
uTorrent 1.8.5.0
24.142.56.27 0.0 0.0 163.8 r /Cn/cn 0/0 100
uTorrent 1.8.5.0
68.60.53.4 0.0 0.0 163.8 r /Cn/cn 0/0 100
uTorrent 1.8.5.0
95.34.190.185 0.0 0.0 163.8 r /Cn/cn 0/0 100
uTorrent 3.1.2.0
68.231.118.97 0.0 0.0 163.8 r /cn/ci 0/0 100
uTorrent 3.0.0.0
14.201.139.177 0.0 0.0 163.8 r /Cn/cn 0/0 100
uTorrent 3.0.0.0
71.127.1.172 0.0 0.0 0.0 R /Cn/cn 0/0 98
uTorrent 3.1.2.0
80.202.31.147 0.0 0.0 0.0 R /Cn/cn 0/0 100
uTorrent 2.2.0.0
109.224.133.220 0.0 0.0 163.8 r /Cn/cn 0/0 100
uTorrent 3.1.2.0
68.114.141.45 0.0 0.0 163.8 r /Cn/cn 0/0 100
uTorrent 1.8.2.0
That first peer was receiving data at a good clip before I briefly choked it
with "*".
If I kick, it'll reconnect in a few seconds and start downloading...
* 78.180.99.43 11.8 0.0 68.3 r /ci/ui 13/0 16
uTorrent 3.0.0.0
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
