DCC fails with IPv6

[steffen678]

Whenever I try to receive a file via XDCC with IPv6, the download immediately fails — it's just being displayed red in the transfers window. I'm connected to the network via IPv6, too, but I doubt that matters. IPv4 transfers work just fine. There are no error messages, so that's all I can tell. It works fine in other clients, for example in KVIrc.

PS: I'm running the latest version of HexChat on Windows 8.1.

[TingPing]

It's not supposed to work, nobody implemented ipv6 support for dcc.

[steffen678]

Ah, I figured that might be it. Would be nice to see this in the future.

[bspkrs]

Per http://www.kvirc.de/docu/doc_dcc_connection.html it looks like KVIrc implemented DCC over IPv6 by allowing DCC CHAT chat to handle IPv6 addresses without any sort of numeric conversion.

[uzlonewolf]

I have a (very) rough draft written that receives from iroffer-dinoex fine, hopefully I'll have something submittable next week. Figuring out which address to send with the SEND request is problematic though as there is no way to determine if the other end has a v4/v6 address.

[SeraphimlabsLLC]

Still not implemented as of Hexchat 2.14.1 and May 2018. Its one of those nice to have things that probably wouldn't get used enough to make it score high on the todo list, but if someone familiar with that segment of the code has the time to work on it I would appreciate it.

With IPv6 networks becoming more commonplace, having IPv6 support for all of the networking features will become increasingly more significant.

[uzlonewolf]

While I never did find time to finish it, my rough draft is still there if anyone wants to look at it. uzlonewolf@9f65c75 It works fine when iroffer-dinoex sends an IPv6 address to connect to, but sending our address for other clients to connect to hasn't even been started (even the older IPv4 way has been commented out in the above code). It's going to be tricky as when we send our address we have absolutely no idea if the other side is IPv4 only, IPv6 only, or dual stack. My original idea is to send our IPv6 address, wait a few seconds, and if a transfer isn't started then re-send with IPv4. Due to some operating systems (Win XP, OpenBSD) not supporting IPv4-mapped IPv6 sockets, this will probably require opening 2 listening sockets on those systems.