MC-92923"Open to LAN" servers accessible on IPv6-only LAN should show up under Multiplayer without manually entering IP address
Bug MC-3776 (IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6? Ed: sources suggest "hextet", "hexadectet", "hexadecatet", "quibble", "quartet", or "piece")).
But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (MCL-2627 Launcher will not download game over IPv6) and to authenticate to Mojang
This may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Steps to reproduce
- On server machine, turn off IPv4 (eg on MacOS, go to System Preferences -> Network -> Advanced -> TCP/IP -> Configure IPv4 = Off), but ensure that IPv6 is enabled and addressable.
- On client machine, turn off IPv4 as well, and IPv6 is enabled. Both hosts are now IPv6-only single stack hosts.
- On server machine, launch Minecraft session, enter a Minecraft world, hit escape to pause, and choose "Open to LAN" -> "Start LAN World"
- On client machine, choose "Multiplayer" from the title screen
Expected results
- Server machine session is seen at the bottom "local network" section of the "Play Multiplayer" server list
→ Note that if the session does show up, you might be able to connect at a low level, but you wouldn't be able to authenticate on an IPv6-only host, so you would not successfully join the session untilWEB-197is fixed. This report is only about populating LAN list, not connecting/authenticating.
Actual results
- Server session is not seen
Environment
OS: Mac OS X 10.11.1, Java 1.8.0u60, 64bit, Mac Launcher 1.4.48, probably other platforms
Linked Issues
Low
NormalAttachments1
Created Issue:
"Open to LAN" servers accessible on IPv6-only LAN should show up under Multiplayer without manually entering IP address
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6?)).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (https://bugs.mojang.com/browse/MCL-2627 Launcher will not download game over IPv6) and to authenticate to Mojang
Environment
OS: Mac OS X 10.11.1, Java 1.8.0u60, 64bit, Mac Launcher 1.4.48, probably other platforms
is duplicated by
![[Mod] Torabi](../../../data/assets/gravatar/torabi.png){kind=small}
relates to
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
Is this still an issue in the most recent versions (i.e. 1.10.2, or 16w42a) of Minecraft?
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6?)).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (https://bugs.mojang.com/browse/MCL-2627 Launcher will not download game over IPv6) and to authenticate to Mojang
This may be a form of MC-98598
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6?)).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (https://bugs.mojang.com/browse/MCL-2627 Launcher will not download game over IPv6) and to authenticate to Mojang
This may be a
formof MC-98598Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6?)).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (https://bugs.mojang.com/browse/MCL-2627 Launcher will not download game over IPv6) and to authenticate to Mojang
This may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6?)).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (https://bugs.mojang.com/browse/MCL-2627 Launcher will not download game over IPv6) and to authenticate to Mojang
This may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6? Ed: sources suggest "hextet", "hexadectet", "hexadecatet", "quibble", "quartet", or "piece")).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (https://bugs.mojang.com/browse/MCL-2627 Launcher will not download game over IPv6) and to authenticate to Mojang
This may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6? Ed: sources suggest "hextet", "hexadectet", "hexadecatet", "quibble", "quartet", or "piece")).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (
https://bugs.mojang.com/browse/MCL-2627Launcher will not download game over IPv6) and to authenticate to MojangThis may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6? Ed: sources suggest "hextet", "hexadectet", "hexadecatet", "quibble", "quartet", or "piece")).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (
MCL-2627Launcher will not download game over IPv6) and to authenticate to MojangThis may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6? Ed: sources suggest "hextet", "hexadectet", "hexadecatet", "quibble", "quartet", or "piece")).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (
MCL-2627Launcher will not download game over IPv6) and to authenticate to MojangThis may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Steps to reproduce
#On server machine, turn off IPv4 (eg on MacOS, go to System Preferences -> Network -> Advanced -> TCP/IP -> Configure IPv4 = Off), but ensure that IPv6 is enabled and addressable.
#On client machine, turn off IPv4 as well, and IPv6 is enabled. Both hosts are now IPv6-only single stack hosts.
#On server machine, launch Minecraft session, enter a Minecraft world, hit escape to pause, and choose "Open to LAN" -> "Start LAN World"
#On client machine, choose "Multiplayer" from the title screenExpected results
#Server machine session is seen at the bottom "local network" section of the "Play Multiplayer" server list
→ Note that if the session does show up, you might be able to connect at a low level, but you wouldn't be able to authenticate on an IPv6-only host, so you would not successfully join the session untilWEB-197is fixed. This report is only about populating LAN list, not connecting/authenticating.Actual results
#Server session is not seen
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6? Ed: sources suggest "hextet", "hexadectet", "hexadecatet", "quibble", "quartet", or "piece")).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (
MCL-2627Launcher will not download game over IPv6) and to authenticate to MojangThis may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Steps to reproduce
#On server machine, turn off IPv4 (eg on MacOS, go to System Preferences -> Network -> Advanced -> TCP/IP -> Configure IPv4 = Off), but ensure that IPv6 is enabled and addressable.
#On client machine, turn off IPv4 as well, and IPv6 is enabled. Both hosts are now IPv6-only single stack hosts.
#On server machine, launch Minecraft session, enter a Minecraft world, hit escape to pause, and choose "Open to LAN" -> "Start LAN World"
#On client machine, choose "Multiplayer" from the title screenExpected results
#Server machine session is seen at the bottom "local network" section of the "Play Multiplayer" server list
→ Note that if the session does show up, you might be able to connect at a low level, but you wouldn't be able to authenticate on an IPv6-only host, so you would not successfully join the session untilWEB-197is fixed. This report is only about populating LAN list, not connecting/authenticating.Actual results
#Server session is not seen
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6? Ed: sources suggest "hextet", "hexadectet", "hexadecatet", "quibble", "quartet", or "piece")).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (
MCL-2627Launcher will not download game over IPv6) and to authenticate to MojangThis may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Steps to reproduce
- On server machine, turn off IPv4 (eg on MacOS, go to System Preferences -> Network -> Advanced -> TCP/IP -> Configure IPv4 = Off), but ensure that IPv6 is enabled and addressable.
- On client machine, turn off IPv4 as well, and IPv6 is enabled. Both hosts are now IPv6-only single stack hosts.
- On server machine, launch Minecraft session, enter a Minecraft world, hit escape to pause, and choose "Open to LAN" -> "Start LAN World"
- On client machine, choose "Multiplayer" from the title screen
Expected results
- Server machine session is seen at the bottom "local network" section of the "Play Multiplayer" server list
→ Note that if the session does show up, you might be able to connect at a low level, but you wouldn't be able to authenticate on an IPv6-only host, so you would not successfully join the session untilWEB-197is fixed. This report is only about populating LAN list, not connecting/authenticating.Actual results
- Server session is not seen
Bug
MC-3776(IPv6 Does Not Work) is marked as fixed, so I went to test out Minecraft between two IPv6-only hosts. While it is possible to connect to another multiplayer session over IPv6 by entering the IPv6 address manually in the "server address" box of the "direct connect" UI screen (you have to remember to enclose the IPv6 address in square brackets so the port number can be distinguished from the IP address segments delimited by colons (what are these called? IPv4 called the octets, since they were 8bits. So hexidectets for IPv6? Ed: sources suggest "hextet", "hexadectet", "hexadecatet", "quibble", "quartet", or "piece")).But IPv4 multiplayer servers on your LAN show up automatically under your list of multiplayer servers, so the kids can connect without manually entering IP addresses. This functionality should also work with IPv6.
Note that while it is possible to play multiplayer over IPv6, you still have to be dual stack, because IPv4 is required to download the jar files (
MCL-2627Launcher will not download game over IPv6) and to authenticate to MojangThis may be a manifestation or consequence of MC-98598 "LAN List does not populate reliably"
Steps to reproduce
- On server machine, turn off IPv4 (eg on MacOS, go to System Preferences -> Network -> Advanced -> TCP/IP -> Configure IPv4 = Off), but ensure that IPv6 is enabled and addressable.
- On client machine, turn off IPv4 as well, and IPv6 is enabled. Both hosts are now IPv6-only single stack hosts.
- On server machine, launch Minecraft session, enter a Minecraft world, hit escape to pause, and choose "Open to LAN" -> "Start LAN World"
- On client machine, choose "Multiplayer" from the title screen
Expected results
- Server machine session is seen at the bottom "local network" section of the "Play Multiplayer" server list
→ Note that if the session does show up, you might be able to connect at a low level, but you wouldn't be able to authenticate on an IPv6-only host, so you would not successfully join the session untilWEB-197is fixed. This report is only about populating LAN list, not connecting/authenticating.Actual results
- Server session is not seen
Is this still an issue in the most recent versions (currently that is 1.12.2, or the latest 1.13 development snapshot 18w07c) of Minecraft?
is blocked by
Can someone please check, if this still applies to 1.15.2 or the latest 1.16 development snapshot (currently that is 20w07a)?
relates to
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] EVGENSYPERPRO](../../../data/avatars/users/92853.png){kind=small}
Today (using 15w47a and launcher 1.6.48 for Mac OS X) I tried out Minecraft after switching two computers on my LAN to IPv6 only. In accordance with MCL-2627, I was not able to download the jar files over IPv6, nor authenticate to Mojang over IPv6. So I reverted to IPv4, launched the launcher, downloaded the jar files, authenticated to Mojang, started Minecraft, and then switched them both to IPv6 only. On one, I started a world and "Opened to LAN". But the host did not show up in the multiplayer list on the other machine. So I entered the address manually in the "server address" box of the "Direct connect" multiplayer UI. I used square brackets to separate the IP address and port number like [1111:2222:3333:4444:5555:6666:7777:8888]:60505. With IPv6-only, I was not able to login, the message was "Failed to login: The authentication servers are currently down for maintenance". If I switch IPv4 back on, but direct connect to the IPv6 address, I am able to connect. If I turn off IPv4 after successfully joining a multiplayer session, I am able to remain in the session over IPv6.
So in addition to MCL-2627 (unable to download jar files over IPv6) I see two more issues: the screen that scans for minecraft servers on the LAN is not checking IPv6 network, and the Mojang authentication servers are not accessible over IPv6. I don't fully understand the issue that was fixed in this bugreport (edit: on re-reading, I guess it was direct connect to an IPv6 address, which I did confirm), but until all three issues are resolved, it think it would be premature to say IPv6 works with Minecraft.
I will enter a new bugreport for getting multiplayer sessions to show up on IPv6 LAN scans (edit: MC-92923). As for making the Mojang minecraft authentication servers accessible over IPv6 (edit: WEB-197), should I also file a bug report for that? Since It doesn't relate to the game itself, it's more Mojang server infrastructure...
If I open the Minecraft launcher on a host with IPv4 turned off, only IPv6, then the launcher goes into offline mode. If I try to join a LAN multiplayer session, I am refused with the message "Failed to login: The authentication servers are currently down for maintenance". It is possible to connect and play over IPv6 if IPv4 is also connected, but at the moment IPv6-only cannot authenticate.
Also the launcher cannot download jar files over IPv6 (MCL-2627), and LAN multiplayer sessions do not appear in scan (MC-92923)
How do you add a label to a bugreport? I want this to be in the IPv6 label https://bugs.mojang.com/browse/MC-2507?jql=labels%20%3D%20ipv6
This bugreport appears to be a duplicate of
MC-56782(Open to lan only listens on IPv4). I didn't find it because I was searching in the IPv6 label. Apologies for the duplication.But that bugreport was itself marked as a duplicate of
MC-3776(IPv6 Does Not Work). SinceMC-3776was recently resolved as fixed, but the game is still not listening for IPv6 multiplayer sessions, eitherMC-3776orMC-56782needs to be reopened. Or this one needs to be left open.Fixed the link on
MC-56782Confirm issue in 1.11
ziggurism, you, as the reporter of the ticket, can update the affected versions yourself.
Oh right, thanks.
Is this still a issue in the latest version of the game(currently 1.13.1)?
If so, please add it to the affected versions, thanks!
On my macs, I can no longer reliably populate LAN multiplayer sessions, even if the host is not IPv6 only. I think that's MC-98598. The list also doesn't populate for IPv6-only hosts, but the discrepancy between "expected behavior" and "actual behavior" does not occur, so I cannot test this bug. Is MC-98598 a mac-only issue? Maybe this could be tested on windows boxes.
Can this still be reproduced in 1.16.1 or later?
I don't think that the original creator of this bug report is active anymore. (Doesn't seem to be updating this surtain post anymore.)
Is this still a concern in 1.17 or later?
Mojang have stated that they're not interested in supporting IPv6 for the foreseeable future, so there is no point in me updating this bug for newer versions. Just close it as "won't fix" like the rest of them
This is still a problem in 1.20.4, 8 years after being reported.
I made a mod that lets dedicated servers send these pings out, and while I found out that 224.0.2.60 is being used for IPv4 I also found some GitHub commits using ff75:230::60 for the same thing, but there is no code I can see in vanilla Minecraft that uses this address.
I just checked and there isn't even code for listening/multicasting on IPv6 in the client or server.
Please add it 😇
Edit: I decided to see if I could fix it in MCP-Reborn, the answer is yes.
To listen for IPv6 multicast, add a joinGroup call for the IPv6 group address to the already existing socket, since Java was already listening on IPv6.
The address is not wrapped in '[' and ']' as required, so the other change is to add that in the addServer function if the address is instanceof Inet6Address.
Took me all of 10 minutes total....... ᵃⁿᵈ ⁱ'ᵐ ⁿᵒᵗ ᵉᵛᵉⁿ ᵃ ʲᵃᵛᵃ ᵖʳᵒᵍʳᵃᵐᵐᵉʳ ʲᵘˢᵗ ᵃ ⁿᵉʳᵈ