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
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3365>
Deluge <https://deluge-torrent.org/>
Deluge Project
Comment (by Xuefer):
after 1.2.3, it's > 1.2.3, or let's say >=1.2.4
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3365#comment:1>
Comment (by Xuefer):
can anyone verify this? i'm happy to move this ticket to milestone 2.0.4
--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3365#comment:2>
this ticket can be closed
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3365#comment:3>