Page 1 of 1

1 minute delay when peer and tracker have the same IP

Posted: Wed Jul 31, 2013 2:59 am
by Maximus
hi all,

I'm using deluge in a p2p file distribution system. Now my experimental environment is as below:

A linux computer(Debian, deluge 1.3.3 as p2p tool, bttrack as tracker) is used as tracker and peer, and all new files are first seeding on that computer. Other peers are windows pc.
After getting the torrents on a windows pc, I start to download using deluge 1.3.6 and this is when strange things happen. I use wireshark to catch packages and find that deluge will annouce to the tracker(the linux computer) and get peer list(only one peer: linux computer) correctly, but it will not contact the peer(the linux computer) until one minute later(exactly 60 seconds).
Then I try to put the tracker on another windows PC, and deluge 1.3.6 on the downloading pc will start to download soon after I add torrents to its download list.

Has anyone met such situation before? Really don't want to use another computer as tracker. Waiting for your suggestions :)

BTW: should it be reported as a bug?