Files

dtoro 4efddb8bed docs: fix pre-existing broken links surfaced by docs-lint

Problem: docs-lint (added in the wiki-hq reorg) surfaced 126 broken relative
links that predated this session — a container rename, incident/plan docs
that moved into archive/done subfolders without their inbound links being
updated, and a handful of relative-depth bugs in files nested under
containers/archive/ and plans/done/.

Fixes applied, by category:
- 124-authentik.md -> 106-auth-outpost.md (container was renamed; ~40 refs).
- investigations/{2026-04-21-hubris-crash-loop,2026-05-31-authentik-vps-migration}.md
  -> archive/ prefix (both moved to investigations/archive/ previously).
- plans/{2026-06-01-slate-ax-to-sodola-migration,2026-06-04_130000-deprecate-claudio-bot,
  2026-06-25-yuvomi-deployment}.md -> plans/done/ prefix.
- Depth bugs in files nested one level deeper than their siblings assumed
  (investigations/archive/*, knowledge/wiki/containers/archive/*,
  plans/done/*) — corrected relative-path depth.
- Destroyed containers with no surviving page (126-plato) delinked to the
  containers/index.md archaeology row instead of a 404.
- ludo-mini.yaml -> strong.yaml (host was renamed, same physical machine).
- netbird-vps.md (no narrative page exists) -> netbird-vps.yaml (substrate
  record, matching the existing convention for hosts without a wiki page).
- runbook-dpkg-interrupted.md refs -> .agents/skills/runbook-dpkg-interrupted/SKILL.md
  (missed in the phase-4 runbook move because the referencing files used a
  bare filename, not a runbooks/ prefix).
- One dangling forward-reference to a never-written investigation delinked
  to the actual incident record it was describing.

Left alone: two links in knowledge/wiki/containers/101-jellyfin.md into
devops/homelab-authentik-admin/ — an intentional reference to a sibling repo,
not present in this checkout.

Verification: broken-link count 126 -> 2 (real remainder is the cross-repo
reference above); gen-topology.py --check still exit 0; build_host_files.py
still idempotent; all inventory.yaml doc_page targets still resolve.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-06 17:53:35 +02:00

4.7 KiB

Raw Blame History

2026-06-03 — Moonlight/Sunshine game streaming unstable over WiFi

Summary

ludo-mini runs Sunshine as the game-streaming server; mac-mini runs Moonlight as the client. Despite both machines being on the same physical subnet (192.168.178.0/24), streaming was unstable — stuttering, dropouts, and high latency. Root cause: mac-mini is connected only via WiFi, while ludo-mini is wired Ethernet (2.5 Gbps). WiFi throughput shows 1-second UDP dropouts and high jitter (28 ms stddev), which breaks real-time video streaming.

Timeline

Pre-existing state

ludo-mini: wired Ethernet (eno1, 2.5 Gbps), 192.168.178.181/24
mac-mini: WiFi (en1, 802.11ac, 234 Mbps Tx rate, 1 stream, -60 dBm RSSI), 192.168.178.99/24
Both on the same subnet via a consumer router at 192.168.178.1
Sunshine configured: bitrate=80 Mbps, encoder=amf (AMD GPU), fec_percentage=5, hevc_mode=2
Moonlight configured: bitrate=57 Mbps, fps=60, localaddr=192.168.178.181 (correct)

2026-06-03 — investigation

Network tests (iperf3 between mac-mini ↔ ludo-mini):

TCP throughput: 49–86 Mbps, average ~65 Mbps — highly variable
UDP throughput: 1-second complete dropout during a 5-second test; 0% loss otherwise
Ping: 4.7 ms avg, but 28 ms stddev, max 138 ms — WiFi-level jitter
Netbird P2P connection also showed 7 ms latency over the tunnel (unnecessary given same-subnet direct connection)

Additional findings:

mac-mini has a built-in Ethernet port (en0) but it is inactive — no cable connected
mac-mini also has Thunderbolt Ethernet adapters (en5, en6, en7) all inactive
ludo-mini's en0 shows speed 2500 (2.5 GbE)
Netbird routes 192.168.8.0/24 via utun100, but 192.168.178.0/24 traffic stays on en1

Root cause

mac-mini is on WiFi. WiFi introduces:

Throughput variance — 49–86 Mbps TCP fluctuation
Dropouts — 1-second UDP blackouts from radio retransmissions
Jitter — 28 ms stddev with spikes to 138 ms

Moonlight/Sunshine streams real-time video over UDP. Any jitter spike or dropout causes visual stutter or frame drops. The 57 Mbps Moonlight bitrate was too aggressive for the WiFi link's consistency, even though the average throughput is ~65 Mbps.

Mitigations applied

mac-mini — Moonlight (via `defaults write`)

| Setting | Before | After | Rationale | ||---------|--------|-------|-----------| || bitrate | 57 Mbps | 25 Mbps | Reduce to a level WiFi can sustain consistently | || framepacing | off (0) | on (1) | Smooths frame timing over variable latency | || fps | 30 | 60 | Restored to game-appropriate value |

mac-mini — Moonlight (current, wired — 2026-06-04)

| Setting | WiFi value | Wired value | Rationale | ||---------|-----------|-------------|-----------| || bitrate | 60 Mbps | 80 Mbps | Wired 1 GbE can sustain comfortably | || framepacing | on (1) | off (0) | Wired latency is consistent, no smoothing needed | || fps | 60 | 60 | Unchanged |

ludo-mini — Sunshine (via SSH)

| Setting | WiFi value | Wired value | Rationale | ||---------|-----------|-------------|-----------| || bitrate | 40 Mbps | 80 Mbps | Wired can handle full bandwidth | || fec_percentage | 2 | 5 | Restored to default — wired has no dropout concern | || packetsize | 1024 | 1316 | Restored to default (Ethernet MTU) |

Sunshine restarted after changes; confirmed active.

Resolution

2026-06-04 — mac-mini wired to LAN

mac-mini plugged into Ethernet (en0, 192.168.178.182). This definitively resolves the WiFi jitter that caused streaming instability. All WiFi-era conservative settings reverted to appropriate wired values on both ends.

Open questions

~~1. Ethernet wiring — mac-mini has an active en0 port. Plugging it into the same switch/router as ludo-mini would eliminate WiFi jitter entirely. This is the definitive fix.~~ RESOLVED — mac-mini now wired via en0. 2. WiFi alternatives — If wiring is impractical, a WiFi 6 (802.11ax) USB adapter or Thunderbolt-to-Ethernet adapter would help, but wired Ethernet is the only reliable solution for game streaming. 3. Netbird route — 192.168.8.0/24 is routed over Netbird utun100. If Moonlight ever falls back to that subnet (ludo-mini's 192.168.8.133 LAN IP), traffic tunnels unnecessarily. Moonlight correctly uses 192.168.178.181, so this is not currently an issue.

Changelog

2026-06-04 — mac-mini wired to LAN, configs reverted from WiFi mitigations

mac-mini connected via en0 (wired Ethernet, 192.168.178.182), WiFi mitigations no longer needed
Moonlight: bitrate 60→80 Mbps, framepacing disabled
Sunshine: bitrate 40→80 Mbps, fec_percentage 2→5, packetsize restored to default (1316)
First root cause in investigation (Open questions #1) resolved

4.7 KiB Raw Blame History Unescape Escape