From c5f57d6305262ec610c3edc1b6d12c549b810edc Mon Sep 17 00:00:00 2001 From: Mikkeli Matlock Date: Tue, 21 Jul 2026 16:28:12 +0900 Subject: [PATCH] updated conclusion --- blogs/2026-06-27_steam-deck-wifi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blogs/2026-06-27_steam-deck-wifi.md b/blogs/2026-06-27_steam-deck-wifi.md index 601de89..84abdf8 100644 --- a/blogs/2026-06-27_steam-deck-wifi.md +++ b/blogs/2026-06-27_steam-deck-wifi.md @@ -13,7 +13,7 @@ I have a Steam Deck OLED (512GB) and I pretty much like playing games with it. T And for reasons I won't disclose because I don't exactly know myself, I picked Arknights: Endfield to be my controller-native game to play on the Deck. I imagined that with the outrageous mobility of your Steam Decks, it'll be fully possible to enjoy the unnecessarily complicated modern mobile game while lying in bed, connected to WiFi. That's where things started to go wrong, fortunately. -**Spoiler / TL;DR**: It's the wireless NIC being shit. +**Spoiler / TL;DR**: It's the IPv4-over-IPv6 having a tiny MTU, and SteamOS somehow handling that (PMTUD) strangely. ## Running a Windows-oriented modern online game on SteamOS was not a problem So I won't go too deep into this. As simple as booting every relevant Windows exe through Steam using Proton. Then you could have the game executable running.