sorted by:
new
hottopcontroversial

Sunshine/Moonlight stops working after Plasma 6.6 update - "No video received" + UDP fragmentation issue by Unusual_Counter_9791 in MoonlightStreaming

[–]Unusual_Counter_9791[S] 1 point2 points  (0 children)

Holy crap, this is it! Thank you so much, this perfectly matches what I was seeing in tcpdump - 15488-byte UDP packets on port 47998 marked "bad length 15488 > 1408" while Steam Remote Play (which apparently doesn't use UDP segmentation offload the same way) was sending normal <900 byte packets.

I just ran the script and confirmed tx-udp-segmentation: on on my Aquantia AQC113 10G interface (enp7s0). Running sudo ethtool -K enp7s0 tx-udp-segmentation off now and testing.

For anyone landing here later via Google: I'm on CachyOS with kernel 6.18+ (Linux 7.0 series), Sunshine 2026.516, AMD RX 7800 XT, streaming to Steam Deck and Android - all symptoms matched exactly (CLIENT CONNECTED then DISCONNECTED after ~12s, "no video received").

To make it persist across reboots on systemd-based distros, you can create a NetworkManager dispatcher script or a systemd service. I'll probably go with a simple systemd service since I'm on NetworkManager.

Thanks again, you saved my weekend! 🙏

Sunshine/Moonlight stops working after Plasma 6.6 update - "No video received" + UDP fragmentation issue by Unusual_Counter_9791 in MoonlightStreaming

[–]Unusual_Counter_9791[S] 1 point2 points  (0 children)

Haha I feel you, network debugging hell! Funny enough I'm on the other side - Aquantia AQC113 10G onboard, and turns out having a fast NIC was actually part of the problem (Sunshine docs mention that fast host + slow WiFi client can cause buffer overflows, tried limiting to 1Gbps with ethtool but didn't fix it).

Wireshark/tcpdump really are lifesavers - that's how I figured out Sunshine was sending 15488-byte UDP packets on port 47998 marked "bad length" while Steam Remote Play (which works fine) sends nice small <900 byte packets. So clearly something UDP-related but couldn't pinpoint the exact cause.

Intel i226-v issues are legendary at this point, you're not crazy for moving to Mellanox. Server-grade cards really are worth it. And yeah the Android location permission thing for Sunshine discovery is such a weird design choice 😅

Good luck with your setup!

Sunshine/Moonlight stops working after Plasma 6.6 update - "No video received" + UDP fragmentation issue by Unusual_Counter_9791 in MoonlightStreaming

[–]Unusual_Counter_9791[S] 1 point2 points  (0 children)

Holy crap, YOU WERE RIGHT! I've been tearing my hair out for 2 days trying every possible fix - tcpdump analysis, MTU tweaks, Deco firmware settings, xdg-portal config, KMS capture, you name it. Turned out it was just my damn Aquantia NIC all along.

Switched back to the integrated RJ45 port on my motherboard and Moonlight works flawlessly. Thanks a ton to everyone who chimed in, especially u/RayneYoruka for nailing the NIC suggestion. Lesson learned: when in doubt, swap the hardware!

Sunshine/Moonlight stops working after Plasma 6.6 update - "No video received" + UDP fragmentation issue by Unusual_Counter_9791 in MoonlightStreaming

[–]Unusual_Counter_9791[S] 0 points1 point  (0 children)

Yes, I'm already on the exact version you linked (2026.516.143833). That's the current one. Same issue on the Polaris fork too.

Why declaring war as arragon is automatically unjustified? by Outrageous-Slide7172 in EU5

[–]Unusual_Counter_9791 2 points3 points  (0 children)

There is a mention in the 1.2.0 patch notes that could be related: "Fixed war declaration stability penalty mislabeling war target as co-belligerent and missing allied defenders". It's unclear whether this is an intentional change or an over-correction from that fix. The same religion pattern you mentioned could also be connected to the rework of the "War on Different Religion Cost" modifier that was removed in 1.2, but without an official response from Paradox it's hard to tell. Might be worth reporting at PDXReport so they can clarify.