Opened 7 years ago

Last modified 7 years ago

#2949 new bug

Not connecting to newly added peer

Reported by: tristen Owned by:
Priority: minor Milestone: needs verified
Component: libtorrent Version: 1.3.12
Keywords: Cc:


after i "add peer" i almost always have to close deluge, and then re-open it, before deluge will connect to the peer.

deluge then connects automatically to the peer once i re-open.

occasionally it doesn't, upon which i "add peer" again and it will then finally connect.

it's strange. at first i thought it might refuse to connect to some sort of "recent peers" list it might be maintaining or something, but this behaviour can happen even on the first attempt to add a peer.

i haven't tried this on peers out there in the wild. this happens locally on a 10.1.1.n address, when adding a peer on the same 10.1.1.n address. it might be a factor, i dunno.

if anything i would think it would be better to auto-trust local peers, in which case this might be more of a feature request. up to you.


Change History (1)

comment:1 Changed 7 years ago by Cas

  • Component changed from Unknown to libtorrent
  • Summary changed from add peer to Not connecting to newly added peer

This is related to libtorrent, all Deluge does is pass the peer info onwards but I think I have seen this before.

This needs an easy way to reproduce and reported to libtorrent if still an issue in 1.0 or 1.1.

Note: See TracTickets for help on using tickets.