mojira.dev

Josh C

Assigned

No issues.

Reported

No issues.

Comments

1.6.4 also impacted. Has it really taken a year to continue to ask "if it breaks on $CURRENT version?" This is incredibly easy to reproduce for the devs:

1. Run minecraft server. Note that the output of `netstat -a -n -o -p TCPv6` shows java listening on [::]:25565 (wildcard address on the traditional port)
2. Launch the minecraft launcher for any of the current launchers, including the latest as of today.
3. Direct connect to the IPv6 IP of the localhost, which is as follows: ::1
4. The message "Failed to connect to the server java.net.SocketException: Protocol family unavailable" occurs.

Please note that this breaks IPv6 for all but power-users, and more and more ISPs are providing IPv6 access. Additionally, this is a huge problem for users behind CGN (RFC6598) or native-IPv6 with 6to4 transition mechanisms as their IPv4 addresses are NOT globally accessible.

Is there a reason this has taken a year to troubleshoot? Even if global IPv6 access isn't on a developer's machine, surely they have access to >=Vista that has built-in IPv6 support...