Christopher Fitzgerald
- solaryn
- solaryn
- Europe/Stockholm
- Yes
- No
MC-3776![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
Since the new multiplayer interface, Minecraft no longer works for me when using IPv6.
My home network is configured using IPv6, while Internet is only IPv4. Each system has a statically assigned IPv6 address in the unique unicast range fc00::/7. Hostnames have been added for these addresses to each system's hosts file.
What I expected to happen was...:
I should be able to connect to local IPv6 servers.What actually happened was...:
IPv6 hostnames fail to resolve. IPv4 hostnames in the hosts file do resolve.
A fix in 1.4.5 allows IPv6 addresses to be used, but they fail to connect with the error "Protocol family unavailable".Steps to Reproduce:
1. Add a server or direct connect using a hostname that resolves only to IPv6 or using an IPv6 address ([::1] or [fc00::1]).
2. Try to connect.This may require limiting Internet to only use IPv4. I don't have access to IPv6 Internet, or I'd try and see if that works correctly.
If I revert to Minecraft 1.2.5, I can connect to any local IPv6 servers by hostname or IPv6 address without failure.
All other applications I have that support IPv6 work with my network setup.
Since the new multiplayer interface, Minecraft no longer works for me when using IPv6.
My home network is configured using IPv6, while Internet is only IPv4. Each system has a statically assigned IPv6 address in the unique unicast range fc00::/7. Hostnames have been added for these addresses to each system's hosts file.
What I expected to happen was...:
I should be able to connect to local IPv6 servers.What actually happened was...:
IPv6 hostnames fail to resolve. IPv4 hostnames in the hosts file do resolve.
A fix in 1.4.5 allows IPv6 addresses to be used, but they fail to connect with the error "Protocol family unavailable".Steps to Reproduce:
1. Add a server or direct connect using a hostname that resolves only to IPv6 or using an IPv6 address ([::1] or [fc00::1]).
2. Try to connect.This may require limiting Internet to only use IPv4. I don't have access to IPv6 Internet, or I'd try and see if that works correctly.
If I revert to Minecraft 1.2.5, I can connect to any local IPv6 servers by hostname or IPv6 address without failure.
All other applications I have that support IPv6 work with my network setup.
Since the new multiplayer interface, Minecraft no longer works for me when using IPv6.My home network is configured using IPv6, while Internet is only IPv4. Each system has a statically assigned IPv6 address in the unique unicast range fc00::/7. Hostnames have been added for these addresses to each system's hosts file.
What I expected to happen was...:
I should be able to connect to local IPv6 servers.What actually happened was...:
IPv6 hostnames fail to resolve. IPv4 hostnames in the hosts file do resolve.
A fix in 1.4.5 allows IPv6 addresses to be used, but they fail to connect with the error "Protocol family unavailable".Steps to Reproduce:
1. Add a server or direct connect using a hostname that resolves only to IPv6 or using an IPv6 address ([::1] or [fc00::1]).
2. Try to connect.This may require limiting Internet to only use IPv4. I don't have access to IPv6 Internet, or I'd try and see if that works correctly.
If I revert to Minecraft 1.2.5, I can connect to any local IPv6 servers by hostname or IPv6 address without failure.
All other applications I have that support IPv6 work with my network setup.
This appears to be a problem with the Minecraft.exe launcher, rather than the minecraft.jar file itself. If Minecraft is started with a 3rd party launcher (such as MultiMC) it operates correctly.
------------------------------------------------------------------------
Since the new multiplayer interface, Minecraft no longer works for me when using IPv6.
My home network is configured using IPv6, while Internet is only IPv4. Each system has a statically assigned IPv6 address in the unique unicast range fc00::/7. Hostnames have been added for these addresses to each system's hosts file.
What I expected to happen was...:
I should be able to connect to local IPv6 servers.What actually happened was...:
IPv6 hostnames fail to resolve. IPv4 hostnames in the hosts file do resolve.
A fix in 1.4.5 allows IPv6 addresses to be used, but they fail to connect with the error "Protocol family unavailable".Steps to Reproduce:
1. Add a server or direct connect using a hostname that resolves only to IPv6 or using an IPv6 address ([::1] or [fc00::1]).
2. Try to connect.This may require limiting Internet to only use IPv4. I don't have access to IPv6 Internet, or I'd try and see if that works correctly.
If I revert to Minecraft 1.2.5, I can connect to any local IPv6 servers by hostname or IPv6 address without failure.
All other applications I have that support IPv6 work with my network setup.
This appears to be a problem with the Minecraft.exe launcher, rather than the minecraft.jar file itself.
If Minecraft is started with a 3rd party launcher (such as MultiMC) itoperatescorrectly.------------------------------------------------------------------------
Since the new multiplayer interface, Minecraft no longer works for me when using IPv6.
My home network is configured using IPv6, while Internet is only IPv4. Each system has a statically assigned IPv6 address in the unique unicast range fc00::/7. Hostnames have been added for these addresses to each system's hosts file.
What I expected to happen was...:
I should be able to connect to local IPv6 servers.What actually happened was...:
IPv6 hostnames fail to resolve. IPv4 hostnames in the hosts file do resolve.
A fix in 1.4.5 allows IPv6 addresses to be used, but they fail to connect with the error "Protocol family unavailable".Steps to Reproduce:
1. Add a server or direct connect using a hostname that resolves only to IPv6 or using an IPv6 address ([::1] or [fc00::1]).
2. Try to connect.This may require limiting Internet to only use IPv4. I don't have access to IPv6 Internet, or I'd try and see if that works correctly.
If I revert to Minecraft 1.2.5, I can connect to any local IPv6 servers by hostname or IPv6 address without failure.
All other applications I have that support IPv6 work with my network setup.
This appears to be a problem with the Minecraft.exe launcher, rather than the minecraft.jar file itself. The launcher sets the "java.net.preferIPv4Stack" property to true and the "java.net.preferIPv6Addresses" to false, prohibiting the use of IPv6 on systems configured as described. Adjusting these two properties should fix the problem.
If Minecraft is started with a 3rd party launcher (such as MultiMC) that doesn't modify these properties as above, it operates correctly.
------------------------------------------------------------------------
Since the new multiplayer interface, Minecraft no longer works for me when using IPv6.
My home network is configured using IPv6, while Internet is only IPv4. Each system has a statically assigned IPv6 address in the unique unicast range fc00::/7. Hostnames have been added for these addresses to each system's hosts file.
What I expected to happen was...:
I should be able to connect to local IPv6 servers.What actually happened was...:
IPv6 hostnames fail to resolve. IPv4 hostnames in the hosts file do resolve.
A fix in 1.4.5 allows IPv6 addresses to be used, but they fail to connect with the error "Protocol family unavailable".Steps to Reproduce:
1. Add a server or direct connect using a hostname that resolves only to IPv6 or using an IPv6 address ([::1] or [fc00::1]).
2. Try to connect.This may require limiting Internet to only use IPv4. I don't have access to IPv6 Internet, or I'd try and see if that works correctly.
If I revert to Minecraft 1.2.5, I can connect to any local IPv6 servers by hostname or IPv6 address without failure.
All other applications I have that support IPv6 work with my network setup.
This
appears to be a problem with the Minecraft.exelauncher, rather than the minecraft.jar file itself. The launcher sets the "java.net.preferIPv4Stack" property to true and the "java.net.preferIPv6Addresses" to false, prohibiting the use of IPv6 on systems configured as described. Adjusting these two properties should fix the problem.If Minecraft is started with a 3rd party launcher (such as MultiMC) that doesn't modify these properties as above, it operates correctly.
------------------------------------------------------------------------
Since the new multiplayer interface, Minecraft no longer works for me when using IPv6.
My home network is configured using IPv6, while Internet is only IPv4. Each system has a statically assigned IPv6 address in the unique unicast range fc00::/7. Hostnames have been added for these addresses to each system's hosts file.
What I expected to happen was...:
I should be able to connect to local IPv6 servers.What actually happened was...:
IPv6 hostnames fail to resolve. IPv4 hostnames in the hosts file do resolve.
A fix in 1.4.5 allows IPv6 addresses to be used, but they fail to connect with the error "Protocol family unavailable".Steps to Reproduce:
1. Add a server or direct connect using a hostname that resolves only to IPv6 or using an IPv6 address ([::1] or [fc00::1]).
2. Try to connect.This may require limiting Internet to only use IPv4. I don't have access to IPv6 Internet, or I'd try and see if that works correctly.
If I revert to Minecraft 1.2.5, I can connect to any local IPv6 servers by hostname or IPv6 address without failure.
All other applications I have that support IPv6 work with my network setup.
This bug/flaw is by design. The Minecraft launcher disables IPv6 (by setting "java.net.preferIPv4Stack" to true). The only workarounds for this are to use a 3rd party launcher or to modify the official one.
------------------------------------------------------------------------
This appears to be a problem with the Minecraft.exe launcher, rather than the minecraft.jar file itself. The launcher sets the "java.net.preferIPv4Stack" property to true and the "java.net.preferIPv6Addresses" to false, prohibiting the use of IPv6 on systems configured as described. Adjusting these two properties should fix the problem.
If Minecraft is started with a 3rd party launcher (such as MultiMC) that doesn't modify these properties as above, it operates correctly.
------------------------------------------------------------------------
Since the new multiplayer interface, Minecraft no longer works for me when using IPv6.
My home network is configured using IPv6, while Internet is only IPv4. Each system has a statically assigned IPv6 address in the unique unicast range fc00::/7. Hostnames have been added for these addresses to each system's hosts file.
What I expected to happen was...:
I should be able to connect to local IPv6 servers.What actually happened was...:
IPv6 hostnames fail to resolve. IPv4 hostnames in the hosts file do resolve.
A fix in 1.4.5 allows IPv6 addresses to be used, but they fail to connect with the error "Protocol family unavailable".Steps to Reproduce:
1. Add a server or direct connect using a hostname that resolves only to IPv6 or using an IPv6 address ([::1] or [fc00::1]).
2. Try to connect.This may require limiting Internet to only use IPv4. I don't have access to IPv6 Internet, or I'd try and see if that works correctly.
If I revert to Minecraft 1.2.5, I can connect to any local IPv6 servers by hostname or IPv6 address without failure.
All other applications I have that support IPv6 work with my network setup.
Windows 7
64-bit, Java664-bit,vanilla Minecraft 1.3.0+Windows 7, Linux, probably Mac as well, Java 64-bit, official launcher
Local NetworkIPv6 Does Not Work
Windows 7, Linux, probably Mac as well, Java 32/64-bit, official launcher
This problem still persists in Minecraft 1.4.6.
I recently discovered that the problem I've been having appears to be caused by the Minecraft.exe launcher. If I run Minecraft from one of the third party launchers or straight from the minecraft.jar file (albeit without logging in) the problem vanishes.
It looks to me like the launcher may be setting some Java network property that interferes with the use of IPv6 addresses when IPv4 is also present.
Let me know if there is anything I can do to further help determine why this occurs. It would really be nice to use my IPv6 server again.
Sorry for the lack of updates. I've been having some trouble using this site. When I try to browse issues or even a specific issue, it puts me in some kind of redirect loop. I had to enable NoScript so I could start this reply.
The IPv6 problem still persists. As I mentioned previously, the launcher appears to be the culprit. It works fine when I run it in MultiMC. I think the launcher may be setting a Java property that causes it to prefer using the IPv4 stack. Unfortunately, I haven't yet had the time to run it in a debugger to find out exactly what's going on.
Good to see confirmation regarding the launcher.
Speaking of which, I had a chance to do a cursory look over its classes and the problem is with LauncherFrame.class. It sets the "java.net.preferIPv4Stack" property to true and the "java.net.preferIPv6Addresses" property to false, which prohibits the use of IPv6 on systems configured as we've described.
Apologies for the lack of updates lately.
I've just had a chance to test out the last few versions to see if there was any change. As before, the problem lies with the launcher. I've updated the summary to point out my previous comment regarding its cause.
I've not had the time to test (or inspect the bytecode) of versions past 1.6.4 myself. As of those tests, I can for certain state that (at least on Windows) the problem definitely is the launcher (whether that be .exe or .jar). Given you (Hugo) state that Linux appears to suffer a similar problem, I'd bet the same for it. Try running the game from a 3rd party launcher (IPv6 worked with both MultiMC and MagicLauncher last I checked).
At this point, given Grum's statement (as pointed out by Omar) I don't feel the need to keep updating this report, since the bug will remain by design. Perhaps they'll fix it when IPv6 becomes more prevalent. At the very least it wouldn't hurt to add an IPv6 option (with an appropriate warning) to the launcher. In the meantime, to use IPv6 we're forced to use a 3rd party launcher or a modified version of the official one.
I'll update the topic version (to 1.7.9) and modify the summary to clarify that the launcher's extension is irrelevant and that this affects Linux users as well.