Forums Feature Suggestions IPv6 implementation

Do you think IPv6 will be implemented into mIRC in the [very near] future? This is a problem I have, considering I use IPv6 for my normal, everyday, IRC-oriented activities. As of now, I have to either IRC using my router address, or setup a [generic] BNC on it.

I think it'd be a great implementation, and could do a lot of good for far-future releases of mIRC.

If you try the search feature you can see what the many other posts on this subject say.

Not all versions of Windows support IPv6, this makes it difficult to add. I doubt you will be seeing IPv6 in mIRC anytime soon. There are very few servers actually using it, and as far as Windows goes, your average user doesn't even know how to activate ipv6 support.

I actually searched the entire message board for 'ipv6' and came up with no results. That's the reason I started this thread.

As for implementation; It'd be nice if mIRC would allow you to bind sockets to an IPv6 address. More and more people are using IPv6 every day.

Here and here.

Looks like you left the Date Range to "newer than one week". Sorry, i should have specified that the posts were older than that, i dont always remind ppl to check "all forums" and expand the date range as needed.

Actually, the way MS setup the SDK for the IPv6 implementation on the 2000 tech demo at least, you can build an executable in hybrid support mode. You use the IPv6-aware name resolution funcs (getaddrinfo, getnameinfo), and a link lib will pass it down to the native function if you're IPv6 (or update resolver) capable, and kick down to the older gethostby* funcs if you aren't. Now, presuming MS didn't NT-tree specific this link lib, it should work with anything running Winsock2+, and maybe lower (they talk about asking for ws1 in the ws init routines). The rest of the changes should be just updates to use the step-up API. Either drop a checkbox to enable v6, or auto-use if the connect is intended for a v6 host.