Opened 15 years ago
Last modified 7 years ago
#1130 new feature-request
IPv6 Interfaces support (daemon,webui,gtk)
Reported by: | jinks | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | Core | Version: | |
Keywords: | Cc: | tikal808, jaarli@mbnet.fi, flo@freakempire.de, russianneuromancer@yandex.ru |
Description
The daemon and webUI don't listen on ipv6 sockets.
And even when forwarding to the specific ports (in which you have to use another port, since even though it doesn't use them, deluge blocks the same ports on the ipv6 socket) the GTK client cannot connect to ipv6 hosts in any way.
Attachments (2)
Change History (16)
comment:1 by , 15 years ago
Milestone: | → 1.4.0 |
---|
comment:2 by , 15 years ago
Cc: | added |
---|
comment:3 by , 15 years ago
Cc: | added |
---|
comment:4 by , 14 years ago
Priority: | major → minor |
---|---|
Summary: | interfaces (daemon,webui,gtk) don't support ipv6 → IPv6 Interfaces support (daemon,webui,gtk) |
Version: | 1.2.0 |
damoxc:
We have to wait for Twisted to support IPv6 unfortunately.
comment:5 by , 14 years ago
Milestone: | 1.4.0 → Future |
---|
Twisted still haven't made any progress on this.
comment:6 by , 13 years ago
From http://twistedmatrix.com/trac/wiki/IPv6 the 2 ipv6 tcp bugs: 5084 and 5085 are now resolved. Does that mean that work can begin on getting ipv6 support for the webui, etc?
comment:7 by , 13 years ago
Cc: | added |
---|
comment:8 by , 12 years ago
Cc: | added |
---|
comment:9 by , 9 years ago
Any update on this?
I was half-way migrating to deluge today, and noticed I can't use the web-ui from a different host, because deluged doesn't listen to IPv6 by default.
The only way to use the server and client on different hosts, seems to be port-forwarding (eg: via ssh -L).
Am I missing something? Is this what everyone else is doing?
comment:10 by , 9 years ago
I think this is really overdue now, pretty much everything is slowly moving away from IPv4. Would be nice to at least have a dev chime in and say it hasn't been completely forgotten about.
comment:11 by , 9 years ago
Hey, if any twisted bugs have been fixed this may get into v2. I'll take a look.
comment:12 by , 9 years ago
On develop, it works passing an IPv6 address:
deluge-web --interface "::"
comment:13 by , 9 years ago
Not exactly 100% related but just thought id mention the check for is_ip() doesnt work for windows ipv6 currently however win_inet_pton could be used to fix this. Note i suppose this is also related to http://dev.deluge-torrent.org/ticket/2786 .
by , 7 years ago
Attachment: | 0001-Support-IPv6-literal-for-daemon-connection-in-gtkui-master.patch added |
---|
by , 7 years ago
Attachment: | 0001-Support-IPv6-literal-for-daemon-connection-in-gtkui-1.3.patch added |
---|
comment:14 by , 7 years ago
Submitted patch for supporting IPv6 literal for daemon connection in gtkui for both 1.3.x and 1.4.
If a daemon is listening to "::" (i.e. invoked by deluged -u "::"
) or
a specific IPv6 address, the client could connect to it with IPv6
address literal (e.g. "2001:db8::1234", but not domain names).
I really need deluged, webui and gtk to listen on IPv6 interfaces as well. I can use the limited features of deluge-console if I can ssh to a deluged server using IPv6 since opensshd listens on all interfaces. Considering how long IPv6 support has been in Linux, I'm surprised that the daemon is not listening on all interfaces by default. I'd love to help with this ticket an any way I can.