Technic Launcher Disables IPV6 connections

[carbolemons]

For whatever reason, i believe the launcher disables the ability to connect to ipv6 servers in multiplayer, because on any modpack, even technically ones that should support ipv6 dont connect.

[B#402]  [14:35:19] [Client thread/INFO]: Connecting to 2a02:8108:1340:6a68:4ae:2392:3121:fabe, 25565        (yes, this server is actually running, and OPEN on the ipv6 address)
[B#402]  [14:35:19] [Server Connector #1/ERROR]: Couldn't connect to server
[B#402]  java.net.SocketException: Protocol family unavailable
[B#402]      at sun.nio.ch.Net.connect0(Native Method) ~[?:1.8.0_211]
[B#402]      at sun.nio.ch.Net.connect(Unknown Source) ~[?:1.8.0_211]
[B#402]      at sun.nio.ch.Net.connect(Unknown Source) ~[?:1.8.0_211]
[B#402]      at sun.nio.ch.SocketChannelImpl.connect(Unknown Source) ~[?:1.8.0_211]
[B#402]      at io.netty.channel.socket.nio.NioSocketChannel.doConnect(NioSocketChannel.java:176) ~[NioSocketChannel.class:?]
[B#402]      at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.connect(AbstractNioChannel.java:169) ~[AbstractNioChannel$AbstractNioUnsafe.class:?]
[B#402]      at io.netty.channel.DefaultChannelPipeline$HeadHandler.connect(DefaultChannelPipeline.java:1008) ~[DefaultChannelPipeline$HeadHandler.class:?]
[B#402]      at io.netty.channel.DefaultChannelHandlerContext.invokeConnect(DefaultChannelHandlerContext.java:494) ~[DefaultChannelHandlerContext.class:?]
[B#402]      at io.netty.channel.DefaultChannelHandlerContext.connect(DefaultChannelHandlerContext.java:479) ~[DefaultChannelHandlerContext.class:?]
[B#402]      at io.netty.channel.ChannelOutboundHandlerAdapter.connect(ChannelOutboundHandlerAdapter.java:47) ~[ChannelOutboundHandlerAdapter.class:?]
[B#402]      at io.netty.channel.DefaultChannelHandlerContext.invokeConnect(DefaultChannelHandlerContext.java:494) ~[DefaultChannelHandlerContext.class:?]
[B#402]      at io.netty.channel.DefaultChannelHandlerContext.connect(DefaultChannelHandlerContext.java:479) ~[DefaultChannelHandlerContext.class:?]
[B#402]      at io.netty.channel.ChannelOutboundHandlerAdapter.connect(ChannelOutboundHandlerAdapter.java:47) ~[ChannelOutboundHandlerAdapter.class:?]
[B#402]      at io.netty.channel.DefaultChannelHandlerContext.invokeConnect(DefaultChannelHandlerContext.java:494) ~[DefaultChannelHandlerContext.class:?]
[B#402]      at io.netty.channel.DefaultChannelHandlerContext.connect(DefaultChannelHandlerContext.java:479) ~[DefaultChannelHandlerContext.class:?]
[B#402]      at io.netty.channel.DefaultChannelHandlerContext.connect(DefaultChannelHandlerContext.java:464) ~[DefaultChannelHandlerContext.class:?]
[B#402]      at io.netty.channel.DefaultChannelPipeline.connect(DefaultChannelPipeline.java:847) ~[DefaultChannelPipeline.class:?]
[B#402]      at io.netty.channel.AbstractChannel.connect(AbstractChannel.java:198) ~[AbstractChannel.class:?]
[B#402]      at io.netty.bootstrap.Bootstrap$2.run(Bootstrap.java:187) ~[Bootstrap$2.class:?]
[B#402]      at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:354) ~[SingleThreadEventExecutor.class:?]
[B#402]      at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:348) ~[NioEventLoop.class:?]
[B#402]      at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101) ~[SingleThreadEventExecutor$2.class:?]
[B#402]      at java.lang.Thread.run(Unknown Source) ~[?:1.8.0_211]

 

it SHOULD be able to connect, and i have made it work outside of the launcher on the version i am playing, with its version of forge, but for some reason always with the technic launcher, it doesnt work

[pyramidenkoenig]

I've been seeing the exact same problem. It is still being manually disabled in Technic Launcher. As IPv6 is pretty common nowdays it would be nice for Technic Launcher to support it. 

[JaariAtmc]

9 hours ago, pyramidenkoenig said:

I've been seeing the exact same problem. It is still being manually disabled in Technic Launcher. As IPv6 is pretty common nowdays it would be nice for Technic Launcher to support it. 

When we actually supported it, all hell broke loose. IPv4 is still supported by IPv6.

[pyramidenkoenig]

2 hours ago, JaariAtmc said:

When we actually supported it, all hell broke loose. IPv4 is still supported by IPv6.

No it's not.

If i try to connect with IPv4 connectivity disabled, it doesn't work. IPv6 is not backwards compatible on it's own.

In Vanilla with the Stock launcher, IPv6 as well as DualStack work fine. 

Please fix this. IPv6 adoption is at nearly 40% in Europe and most big Services support it.

[JaariAtmc]

6 hours ago, pyramidenkoenig said:

No it's not.

If i try to connect with IPv4 connectivity disabled, it doesn't work. IPv6 is not backwards compatible on it's own.

In Vanilla with the Stock launcher, IPv6 as well as DualStack work fine. 

Please fix this. IPv6 adoption is at nearly 40% in Europe and most big Services support it.

The moment we enable it again, the launcher will cease working for everyone still using IPv4. That's a LOT of the playerbase, and it still wouldn't actually help with the IPv6.

[Pyker]

This has been tried before in the past. We had to rollback that change because people with broken IPv6 setups (read: that have IPv6 but it isn't working properly) couldn't connect to anything. Besides, Mojang's auth servers are IPv4-only, so it's not like IPv6-only connections can even authenticate on the launcher.

Also, as far as Minecraft servers running on IPv6 addresses goes, Minecraft itself couldn't connect to IPv6 servers until a certain version.

[JaariAtmc]

That certain version being a snapshot for Minecraft 1.9. So Minecraft 1.9 was the soonest Mojang added compatability for IPv6.

I'm sure you'd love to handle all the users that won't be able to play any of the official modpacks anymore?