gs007
Assigned
Reported
Comments
@Ziloloshka I'm sorry to tell you this but I don't think a fix is coming. I have been commenting on this issue, offering technical analysis and suggesting solutions for 8 years, along with others. I'm assuming Mojang keeps it low priority because they want you and your sister to subscribe to realms to play together. I hate to be so jaded but it's the only conclusion I can come to given the number of votes this issue has. The reality is that frogs falling into holes and pathfinding is higher priority than this according to Mojang (Not lying, see MC-250238 and MC-249232 if you don't believe me).
Happily there are easy solutions to get you guys playing together if you're willing to get a little bit technical. The great thing about Java edition is it's flexibility. When you start your LAN world, you will see a message that says "Local game hosted on port xxxx." Write that down. If it disappears before you do, press "t" to get back to your chat window. Then you just need the LAN ip of your computer: type ipconfig /all in a terminal window (windows 10) to get it. You can look up how to do this for your OS on google if you're not running windows.
Finally, give this information to your sister, have her choose Multiplayer >> Direct Connection on her minecraft client. Type in the IP and Port in this format: ip:port So for example if your IP was 192.168.1.50 and the port the LAN world is hosted on is 3187, you'd have her type 192.168.1.50:3187
She should be able to connect then. Sorry it's so complicated, but-- capitalism rules I guess?
Have fun and happy mining!!
Some quick stats on this issue:
Just under 40 duplicate issues opened for this issue over 7 years.
The first mention of this bug was in 2015.
It's still 9th on the list of issues people most want fixed by vote for MC Java Edition. After 7 years that's pretty impressive.
Last version of MC Java that worked: 1.8
The solution is really simple: Have minecraft java app listen for multicast on ALL interfaces on the client. If you do that it will work.
As a note to bugfix PMs: Maybe 7 years open and reliably in top ten issues users vote on is enough to get the priority raised and have it assigned for a fix. I'm not saying there aren't more important issues out there, but this one keeps slipping through the cracks.
If it's possible, I think a very sane approach/fix for java edition in general (since it's cross platform) is to just listen on all active network interfaces for multicast traffic. It's a very simple solution to a problem that has been around for a long time.
Also note that in terms of open issues, this one only has 2 less votes than the top voted open issue on MC Java Edition. If we could get more votes to put it on top, perhaps this long lasting issue could be resolved.
@Tres
I'm not sure there will be much you can do on your mac to reliably populate the game list until this bug is addressed by a developer. You can eliminate your wireless, network stack setup, etc, as the problem by running the tcpdump command above on the mac that wants to join the game. If you get an output showing the LAN announcement, your setup is fine. If you only use one interface for 'regular networking' i.e., you don't have any VPN interfaces, don't use virtualization software like VMware or Virtualbox, you may be able to solve it by:
Disabling the ipv6 on your interface at the OSX level:
List interfaces:
networksetup -listallnetworkservicesthen (Let's say your interface is 'Wi-Fi' like most), turn off ipv6:{{}}
networksetup -setv6off Wi-FiThen you would have to make sure the interface you want is on the top of the priority list in the sidebar of Settings > Network (which looks like the below):
[media]You can also do this with a Java option in the minecraft launcher or by modifying parameters for Java on your system framework directly. Both are a pain for various reasons and are outlined in detail here.
For what it's worth, I've tried to figure it out on mac-- messing with interface priority, etc, but there doesn't seem to be a consistent correlation where I can this working. I believe there is a logic, I just can't figure it out experimentally.
I am a network guy, not a developer. I've researched all network centric approaches, but the simple answer is, that with OSX, the logic that was used to do this was broken (regression) around 1.8 and no one bothered to fix it. To be fair, OSX has less marketshare, and the networking stack isn't the most fun to work with. I have issues with almost all vendors that develop cross platform networking solutions that include mac.
However, it's my personal opinion, that if an individual minecraft developer with the right knowledge were to look at this, it would be an extremely quick fix.
On the bright side, my kids know how to run a packet capture and understand networking now. I guess that's a positive.
By the way, this is the technique I use when I want to use my Mac to connect to my kids LAN worlds using direct connect option. The number between the — [AD] /AD tags is the port. The IP is the source IP of the UDP packet (So in the above example you'd type in — 10.88.88.88:59973 for direct connect). But if it's your kid who has the Mac, good luck with that. They'll probably get frustrated and just play fortnite instead 😉
There are no solutions posted here that will work reliably. Gábor's solution will not work because it's not a problem with the network stack. The Java arguments will work as long as you don't have any other valid ipv4 interfaces that the minecraft application will choose (i.e. VPN interfaces).
My suspicion (as I've posted 3 times already), is that the minecraft application picks an arbitrary interface to listen for the multicast traffic on, but that is not always the interface the traffic arrives at. This is an application issue. If we knew what logic the application was using to pick the interface, we could come up with a workaround, but it doesn't seem that anyone with access to the source code is interested in looking at this painful regression that has existed since 1.9 was released.
IN ALL CASES, you can see the traffic arrive at your PC by running:
sudo tcpdump -A -n host 224.0.2.60This will output something like this if another client is announcing a LAN game:
11:13:07.739601 IP 10.88.88.88.53383 > 224.0.2.60.4445: UDP, length 61
..^..<..@.-...E..Y........
Ed,...<...].E..[MOTD]Fire*** - ultimate survival[/MOTD][AD]59973[/AD]
^CThis is proof that the traffic arrives at the network stack, it's just not processed by minecraft.
The issue is not that the Mac looking to join isn't receiving the multicast traffic. In all cases, the multicast traffic gets to the client on the correct interface. It's the application that's not listening for it on the correct interface.
I think this one just needs someone to take a look at the logic on how the LAN list gets populated. In all cases I've seen where the multicast traffic is actually getting to the client, the only time the game doesn't show up is when there's other network interfaces (or ipv6 interfaces) involved. True you could disable them, but people have legitimate needs for multiple interfaces (Wifi/wired docking stations, VPN interfaces, etc). So maybe the best way is to just listen for 224.0.2.60:4445 announcements on all available (or up) interfaces.
This has been an issue for quite some time (since 1.8 I believe) and will affect most OSX users by default because of the way ipv6 is enabled by default (which is why you need the JVM options). But even with those options enabled, you can still run into issues if you have multiple interfaces (like me).
The core of the problem is that the game seems to just pick some arbitrary interface to listen on, and if the announcement doesn't come in via that specific interface, then it's no dice.
Ah to walk down memory lane. To say I was there at the beginning of Minecraft is a bit of a stretch, but I consider myself an early adopter and remember things about the game that likely no one does (anyone remember what happened when you punched a sheep?). Notch and I had similar beginnings (except I'm probably a bit older and started on a c64 instead of a c128 like him). I remember being fascinated that he was developing a game pretty much as a project and taking so much community input. It was more of a neat indie lego world as opposed to a full fledged game, but still it was pretty cool. Later when Jeb took over we started to see some really cool stuff and Minecraft started looking more like it does today. I still remember when 1.0 dropped.
So imagine how excited I was to play a game with my kids when they were finally old enough to understand what a computer game was. What did I pick? Of course Minecraft!!!! We played constantly. And since LAN worlds were an easy and safe way for us to play together, that's what we chose. So since they're 3 years old we've been playing together. Best thing is that they started playing with each other. Having twins play together and help each other was so cool, and they didn't need my help... That is until 1.9 dropped. I taught them how to deal with it, but it wasn't the same. They lost interest and picked up other games. We've recently gotten back into MC but they're 12 now and I can't help but feel like we lost time (I did get pretty cracked at Fortnite playing with them in the meantime tho).
In any case, glad you got into IT @Ben White. Hope you continue in the networking field-- the industry definitely needs new talent. I think it's being too charitable to credit Mojang's lack of attention to their user community for this issue as the genesis of your future career. Instead use this as a lesson and remember to honor the people who support you in your journey. Should you ever rise to to success due to the collaboration of others, honor that community when they raise their voice. No one succeeds but for the grace of others.
Happy mining!