3 daemons, Transmission 2.92 (14714), debian 9.1 amd64
- client-a, 192.168.1.103, seeding torrent_x, torrent_y
- client-b, 192.168.1.114
- client-c, 192.168.1.110
- Tracker-a 192.168.1.97
- Upload torrent_x on client-b, let it finish
- Trash data and remove from list... on client-b, torrent_x
- Upload torrent_x on client-b again => torrent_x never starts
client-b doesn't receive any piece from client-a, nothing useful in logs (both sides) - Upload torrent_x on client-c => torrent_x, client-c starts, client-b too (from client-c)
- Trash data and remove from list... on client-b, torrent_x
- Upload torrent_x on client-b again => torrent_x never starts
client-b doesn't receive any piece from client-a/client-c, nothing useful in logs again
The behavior is the same with Windows daemons (*.msi from transmission's github)
MY QUESTION IS: Is it a bandwith protection feature (if so, can it be disabled from settings.json?) or a bug ?
Harry.