IPv6 missing in deluge2/lt-1.2.x.

[mhertz]

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.

[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.

[mhertz]

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