From 1f1e95a0b98f73eefc1ec2139d3c65faddb269e5 Mon Sep 17 00:00:00 2001 From: arch1mede Date: Tue, 14 Sep 2021 21:08:31 -0700 Subject: [PATCH] Update webrtc.md (#469) Added some more troubleshooting steps --- pages/webrtc.md | 1 + 1 file changed, 1 insertion(+) diff --git a/pages/webrtc.md b/pages/webrtc.md index c18c14b8..31a1d923 100644 --- a/pages/webrtc.md +++ b/pages/webrtc.md @@ -54,3 +54,4 @@ In rare cases, WebRTC may not work. The most common reasons are: * Tricky IPv6 configuration on the network. IPv6 support for WebRTC in Pi-KVM is still in its infancy, so if your network has IPv4, it will be easiest to disable IPv6 on Pi-KVM. To do this, switch the file system to write mode using `rw` command, add option `ipv6.disable_ipv6=1` to `/boot/cmdline.txt` and perform `reboot`. Also see [here](https://wiki.archlinux.org/title/IPv6#Disable_IPv6). * A paranoid firewall when you try to connect to the Pi-KVM by forwarding port 443 to the Internet from the internal network. WebRTC is not enough of this, it uses UDP on ports 10000-20000 for a P2P connection. Make sure that the Firewall does not block them. * If nothing helps, open the browser's JS console and look at the log, and contact our community via [Discord](https://discord.gg/bpmXfz5). Developers and/or experienced users will definitely help you. +* Another option to try is if you have both wifi and eth connected, disable wifi `rfkill list wifi` then `rfkill block X` X=the number that shows in the output. Reason: Arch linux will choose to route all outgoing packets out wifi by default.