[Deluge] #3417: IPv6 missing in deluge2/lt-1.2.x.

15 views
Skip to first unread message

Deluge

unread,
Jul 24, 2020, 4:32:53 AM7/24/20
to delug...@googlegroups.com
#3417: IPv6 missing in deluge2/lt-1.2.x.
----------------------------+---------------------
Reporter: mhertz | Type: bug
Status: new | Priority: minor
Milestone: needs verified | Component: Unknown
Version: 2.0.0 | Keywords:
----------------------------+---------------------
Libtorrent 1.2.x changed the way it treats 0.0.0.0 in listen_interfaces
setting, so it only resolves to IPv4 now, in contrary to lt-1.1.x, which
means deluge2 with lt-1.2.x only listens/connects to IPv4 by default.
qbittorrent e.g. uses the lt-1.2.x default value, to fix this i.e.:
'0.0.0.0:port,[::]:port.

The PR by DjLegolas: https://github.com/deluge-torrent/deluge/pull/289,
which changes if tracker errors should be shown or not in UIs based on if
lt-1.1.x or lt-1.2.x, could be extended with this extra functionality i'm
thinking.

Btw, libtorrent supports interface names on windows for both
listen_interfaces and outgoing_interfaces, but just specifically needs be
GUIDs on windows(upper-cased in curly-brackets), but this cannot be
configured in deluge's UIs or CLI arg's, as only supports max 15 chars(not
enough for even one GUID) and checks done on allowed chars etc(e.g.
'['isn't allowed, which is needed with GUIDs etc). Also, multiple
IPs/interfaces are allowed in libtorrent, comma seperated, so would be
nice to support that too(commas aren't supported in deluge currently, plus
that 15 chars limit).

Thanks in advance.

--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3417>
Deluge <https://deluge-torrent.org/>
Deluge Project

Deluge

unread,
Jul 24, 2020, 5:15:08 AM7/24/20
to delug...@googlegroups.com
#3417: IPv6 missing in deluge2/lt-1.2.x.
----------------------+----------------------------
Reporter: mhertz | Owner:

Type: bug | Status: new
Priority: minor | Milestone: needs verified
Component: Unknown | Version: 2.0.0
Resolution: | Keywords:
----------------------+----------------------------

Comment (by mhertz):

Sorry, made mistake above, and there's not supported to edit content
annoyingly. Anyway, I meant GUIDs should be in curly-brazes, not brackets,
and that deluge doesn't support e.g. curly-brazes etc. Just wanted to
highlight that and sorry for being to quick writing/posting ticket
originally. Thanks in advance.

--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3417#comment:1>

Deluge

unread,
Aug 20, 2020, 4:08:41 AM8/20/20
to delug...@googlegroups.com
#3417: IPv6 missing in deluge2/lt-1.2.x.
----------------------+----------------------------
Reporter: mhertz | Owner:

Type: bug | Status: new
Priority: minor | Milestone: needs verified
Component: Unknown | Version: 2.0.0
Resolution: | Keywords:
----------------------+----------------------------

Comment (by mhertz):

Strangelovian posted a PR related to this, with support for multiple
interfaces: https://github.com/deluge-torrent/deluge/pull/300

--
Ticket URL: <https://dev.deluge-torrent.org/ticket/3417#comment:2>

Reply all
Reply to author
Forward
0 new messages