Archives/pikvm
2
0
Fork 0
mirror of https://github.com/pikvm/pikvm synced 2024-11-14 18:12:53 +00:00
Code Issues Projects Releases Wiki Activity

Update webrtc.md (#480)

Browse Source
This commit is contained in:
Casey Link 2021-09-24 15:46:35 +02:00 committed by GitHub
parent b0ca69a5ab
commit b08440a700
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pages/webrtc.md
View File

@ -55,3 +55,5 @@ In rare cases, WebRTC may not work. The most common reasons are:
* 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. * 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. * 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. * 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.
* Your browser might not support the h264 codec. This is probably the case if you're on a distro like Fedora (maybe others). There are ways to install h264 support, just google "<your distro> <your browser> h264".
* On Fedora you can: install the rpmfusion repos, then use the `chromium-freeworld` package instead of `chromium`