On 5/3/07, David Purdy <[EMAIL PROTECTED]> wrote:
1) Given 2 peers A & B (there are no other peers):
2) A runs btlaunchmany to share a directory which contains 1 torrent
file and the complete downloaded file for that torrent.
3) Then B attempts to download the torrent (important: B starts
btdownload *after* btlaunchmany is started on A)
Then:
4) B will not see any peers.
I've seen something like this occurring when one or both of the peers
is behind a NAT or firewall. Is that the case here?
But if you restart btlaunchmany on A then B will suddenly detect peer A and
start downloading from it.
This could occur if A is behind a NAT/firewall, so B can't connect to
it, but if starting A after B then A makes the connection, which works
fine.
If you share the file on A with btdownload rather than btlaunchmany,
then B will be able to start downloading right away.
btlaunchmany from the 'bittorrent' package doens't have this problem.
I've tested with various combinations of bttrack, btdownload and
btlaunchmany from the 'bittornado' and 'bittorrent' packages. As far as
I can tell, the problem is definitely with the seeding 'btlaunchmany'
only registering as a peer when it starts up, but not later.
This sounds like maybe it's not NAT/firewall related after all, but
let me know the answer to the question above to make sure, and if it's
not then I'll investigate further.
Cameron
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
