Opened 4 years ago

Last modified 4 years ago

#3365 new bug

no tracker/dht connected behind nat linked with >=libtorrent-1.2.4

Reported by: Xuefer Owned by:
Priority: minor Milestone: needs verified
Component: libtorrent Version: develop
Keywords: Cc:

Description 

commit 4ceb2ea46713267a7473c7fa653f1fe4d91162a1
Author: arvidn <arvid@libtorrent.org>
Date:   Mon Jan 6 10:11:21 2020 +0100

    limit tracker announces and SOCKS5 connection attempts to listen_socket_t that actually can reach the target

this change in libtorrent after 1.2.3 breaks deluge, making it never connect to any tracker nor any dht nodes tracker status is always: no route to host (boost::system::errc::host_unreachable)

only deluge which bind to lan ip behind NAT is affected. bugs not shown when WAN ip is allocated (by pppoe) locally on the same box running deluge

Change History (2)

comment:1 Changed 4 years ago by Xuefer

  • Summary changed from no tracker/dht connected behind nat linked with libtorrent-1.2.3 to no tracker/dht connected behind nat linked with >=libtorrent-1.2.4

after 1.2.3, it's > 1.2.3, or let's say >=1.2.4

comment:2 Changed 4 years ago by Xuefer

can anyone verify this? i'm happy to move this ticket to milestone 2.0.4

Note: See TracTickets for help on using tickets.