-
Notifications
You must be signed in to change notification settings - Fork 44
can not share data with the same btdownloadheadless.py client each other. #23
Comments
Have you tested using the original BitTorrent (or BitTornado v0.3.18) on both ends of the connection? My experience is with very small swarms (mostly tried with n = 2), it will work, but for some reason it takes a while to initiate the connections, and that this is generally true with most clients. I haven't tried with multiple trackers, so it's possible that there's a problem with bttrack sending on a full list of peers on small swarms. |
BitTornado v0.3.18 has the same problem. |
my OS is debian8, i have installed BitTorrent using apt-get install python-bittorrent, i don't k know whether the python-bittorrent is what you are saying the original BitTorrent. |
To be clear, you're running a server that has a tracker and an initial seeder, and a client that has a leecher? And these are the situations you've described?
Assuming this is correct: What we need to know is whether the tracker works as expected, whether the client works as expected, and whether the bug was introduced between BitTorrent and BitTornado or between BitTornado v0.3.18 and master. Case 5 indicates we can use python-bittorrent (yes, this is the original bittorrent, though possibly with Debian-introduced patches) as a benchmark. Can you test the following cases?
Comparing case 6 and 4 will help determine where the tracker bug was introduced. Cases 7-9 will test the old BitTornado clients in different positions, and cases 10-12 will test the current clients. What would be ideal in all of these cases is if you could give them up to ten minutes to connect, and estimate how long they take to connect. e.g. < 1min, > 10min (failure). Sorry to push this work on you, but I don't have a ton of time, and knowing the conditions this fails in will help reduce the time it takes me to figure this out. |
hi, effigies, i have tested all the situations.
all the exceptions are occurred after the download is completed:
Case 6 leecher:
Case 8 leecher:
|
Thanks for the info! 4 suggests that the current tracker is okay, at least sometimes, so I do think this is a client problem. From 9 and 12, it looks like there were some issues that either emerged in the BitTornado fork from BitTorrent, or that were fixed in BitTorrent since the fork. It's also possible that some changes occurred to the libraries we depend on since then. I'll look into this as I find time. It might be a bit as I have a lot going on right now, but hopefully I can get to it soon. If you're inspired to do some digging and want to submit a PR, I'd be glad to review it. In any case, thanks again for your work. |
From playing with the last few issues/PRs, I think I've established that BitTornado clients are having trouble seeding. I can seed with Hope to make some progress on this, soon. (Tagging in @yang502.) |
I also have faced the same problem about "can not share data with the same btdownloadheadless.py client each other in master branch",for that , I hope you can solve it soon ,thank you,effigies! |
the latest code. ./btdownloadheadless.py --security 0 --crypto_allowed 0 file.torrent with https://github.com/feross/bittorrent-tracker bittorrent-tracker --port 6969 can share data with the same btdownloadheadless.py client on same computer. if use ./bttrack.py --dfile /tmp/bt_state --port 6969 the btdownloadheadless.py can not get peers from bttrack.py so: maybe bttrack.py has a bit bug. :-) |
Thanks for the report. I'll have a look when I get a chance (not likely before February). Figuring out issues in bttrack is what #50 is aimed at, so hopefully once I get back to this project I'll have the tools to get to the bugs. And yes, the crypto in BitTornado might not have translated cleanly in the conversion to Python 3. |
Has there any progress related to this? I am experiencing the same issue here and I would like to get bittornado running. |
No. Sorry, I have way too much going on to put any effort into this repo, at this point. I can try to review PRs, if someone's interested in pushing forward, but the hold-up on #50 is that I don't have time to re-read and test it before merging. |
i am using the master branch on python 3.5
my torrent file is:
start a tracker server on http://172.20.4.22:6969/announce
start a bt client on the tracker server as seeder server.
start a another bt client on another computer, but they can not share data with each other.
but:
if i use another btclient as the seeder server or client, they can share data with btdownloadheadless.py. i have tested the original python-bittorrent and deluge.
thanks,effigies, do you have the same problem on you computer?
The text was updated successfully, but these errors were encountered: