4 Commits

Include renames

Author	SHA1	Message	Date
mats	365415740e	improve WebRTC NAT reliability diagnostics	2026-09-22 16:31:21 +02:00
matsandClaude Sonnet 5	78d97ee733	Add a second, LAN-only TURN relay to avoid hairpin NAT entirely ... The existing coturn instance advertises the router's public IP as its relay address (external-ip=94.255.139.35) — correct for real external users, but when both peers are on the same home network as the router, relay traffic has to hairpin through the router's own WAN IP. That only worked with hwnat (hardware NAT offload) disabled, which pegged the router's CPU at 93% for well under half its rated throughput — not an acceptable trade for the whole household's network. Instead of touching hwnat, added a second coturn deployment (coturn-lan, own secret, own relay port range 49210-49220) exposed via its own MetalLB LoadBalancer IP (10.10.3.46) on the same LAN segment. That address is answered directly via L2 ARP — no NAT, no hairpin, hwnat never touches it — and it's deliberately not port-forwarded from WAN, so it's LAN-only by construction. iceConfig() now appends this as an extra iceServers entry whenever TURN_LAN_HOST/TURN_LAN_SECRET are set. It's harmless for anyone not on that network — the address is simply unreachable and ICE ignores it — and WebRTC tries every configured server, using whichever candidates actually connect. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-22 13:13:25 +02:00
mats	4d8a4a0dec	fix(otel): point backend otel endpoint to in-cluster otel-debug-service in monitoring namespace	2026-09-22 10:29:44 +02:00
mats	5757156843	feat: migrate voice app, add otel/rum, dockerfile, k8s deployment with ingress	2026-09-22 09:43:47 +02:00