From 5d41048695975cbcc88ae886a7e6c1d770563384 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miroslav=20=C5=A0ediv=C3=BD?= Date: Fri, 18 Nov 2022 19:41:15 +0100 Subject: [PATCH] update docs. --- docs/getting-started/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/getting-started/README.md b/docs/getting-started/README.md index de58c398..a4fe8aef 100644 --- a/docs/getting-started/README.md +++ b/docs/getting-started/README.md @@ -78,8 +78,10 @@ services: ``` - When using mux, `NEKO_EPR` is ignored. +- Mux accepts only one port, not a range. - You only need to expose maximum two ports for WebRTC on your router/firewall and have many users connected. - It can even be the same port number, so e.g. `NEKO_TCPMUX: 8081` and `NEKO_UDPMUX: 8081`. +- The same port must be exposed from docker container, you can't map them to different ports. So `8082:8082` is OK, but `"5454:8082` will not work. - You can use them alone (either TCP or UDP) when needed. - UDP is generally better for latency. But some networks block UDP so it is good to have TCP available as fallback. - Still, using `NEKO_ICELITE=true` is recommended.