Chromebooks Disconnect From Hosted Game
Intel based Chromebooks connect to host server on same network briefly, but then disconnect. AMD based Chromebooks connect to same host server and stay connected without issue. Intel Chromebooks are the only device that experiences the issue; AMD Chromebooks, Windows devices, etc all work fine.
-
I have captured traffic from an Intel Chromebook at the at each hop all the way to the internet edge to verify that the traffic is making it all the way out, starting closest to the Chromebook and working my way out. We have captured timestamps of when the Chromebook gets disconnected from the game and correlated it to the packets that we captured and found that there are destination unreachable messages in the capture to 20.202.20.0 /22 which is Microsoft's subnet. It does make it to some IPs in that subnet but there are IPs within that subnet that there is a problem.
0 -
Thank you for sending that. These are all the backend changes that we implemented for multiplayer. The main thing is that any content filter that is in place can cause this issue and should be researched.
- Make sure that //*.minecraft-services.net/ has been allow listed through firewall and content filters.
- The signaling connections use wss://signal.franchise.minecraft-services.net.
- The STUN and TURN connections use turn.azure.com / world.relay.skype.com on the 20.202.0.0 / 16 IP range using remote TCP port 443 and remote UDP ports 3478-3481
- The peer-to-peer connections between host and joining client use local ephemeral UDP ports specified by the host client (the local port range is defined by the OS) and sent to the joining client via the signaling service.
- Our system now uses ephemeral ports. They will need to be unblocked.
- Can you tell me if this is device specific or is this happening to everyone and how often?
- Try toggling
cellular datasetting to on with tablets, Chromebooks, android phones and iOS phones.- It's a setting under Profile on all devices.
0 -
I have verified and just confirmed again that *.minecraft-services.net/ is allowed through the content filter. The problem does not occur on the same model Chromebook with AMD chipset, which rules out the content filter. I am fairly certain at this point that the issue does not occur higher than layer 3. At this point I believe the issue occurs between the radio of the access point and the Intel Chromebook. In the latest pcaps I am able to see the traffic destined for the Intel Chromebook at the switchport where the access point is connected to, as well as in the air between the access point radio and the Intel Chromebook. I think I have it narrowed down to a problem between this specific model of access point and the Intel chipset in the Chromebook, as an older model access point of the same manufacturer does not exhibit the same issue. One could easily point the finger at the access point now but it still could be an issue with the Intel chipset hardware/driver and it's interaction with this particular access point. When the issue occurs, the Intel Chromebook stops RX/TX completely (pings, Mincecraft, etc), almost as if the radio in the Intel Chromebook hangs up. I have a ticket open with the wireless manufacturer. Right now it doesn't seem like a Minecraft specific issue but I thought it best to still post this information.
0 -
Oh wow Mitch, thanks so much for taking the time out to post about your findings here! I am sure this will help others as well.
0
Please sign in to leave a comment.
Comments
4 comments