From 3cb0a5f94299d8121855481578c6a82933dc64e8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Er=C3=A8be=20-=20Romain=20Gerard?= Date: Sun, 5 Nov 2023 19:21:17 +0100 Subject: [PATCH] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index e9abc80..f6aa308 100644 --- a/README.md +++ b/README.md @@ -218,6 +218,7 @@ Now your wstunnel server, will only accept connection if the client specify the ### Wireguard and wstunnel https://kirill888.github.io/notes/wireguard-via-websocket/ +- Disable default udp tunnel timeout that will close it after 30sec. `i.e: udp://1212:127.0.0.1:5201?timeout_sec=0` - If you see some throughput issue, be sure to lower the MTU of your wireguard interface (you can do it via config file) to something like 1300 or you will endup fragmenting udp packet (due to overhead of other layer) which is always causing issues - If wstunnel cannot connect to server while wireguard is on, be sure you have added a static route via your main gateway for the ip of wstunnel server. Else if you forward all the traffic without putting a static route, you will endup looping your traffic wireguard interface -> wstunnel client -> wireguard interface