connection to seed maintained after completion
Posted: Tue Jan 14, 2014 12:14 pm
Noticed on five completed jobs that qBT is keeping a active connection to seeding peers. The jobs are Ubuntu and Centos ISOs
In all cases the peer is flagged H (DHT), using BitTorrent protocol and the client is MLDonkey. All the IPs are different.
The coincidences of DHT, protocol and client suggest that the problem may be with MLDonkey over BT mis-reporting it's peering status to DHT nodes, so I'm wondering if anyone had noticed anything similar with other clients.
In all cases the peer is flagged H (DHT), using BitTorrent protocol and the client is MLDonkey. All the IPs are different.
The coincidences of DHT, protocol and client suggest that the problem may be with MLDonkey over BT mis-reporting it's peering status to DHT nodes, so I'm wondering if anyone had noticed anything similar with other clients.
