You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 6, 2024. It is now read-only.
Tun2socks stack will supposedly call udpHandler.Close() when the app socket is closed.
No, tun2socks has no way to know whether the app socket has been closed. It only has access to the "tun device" as an io.ReadWriteCloser, with IP packets flowing in and out.
If a read hits the timeout, we stop listening for packets:
outline-go-tun2socks/shadowsocks/udp.go
Lines 52 to 56 in ab0408a
I wonder if this is causing issues with apps that use UDP, specially in extreme conditions.
The default timeout is 30 seconds:
outline-go-tun2socks/outline/tunnel.go
Line 84 in 2f14928
It's not clear to me that we need the timeout. Tun2socks stack will supposedly call
udpHandler.Close()
when the app socket is closed.My suggestion is to remove the timeout. At least make is longer, like the 5 minutes we use on the server:
https://github.com/Jigsaw-Code/outline-ss-server/blob/8269318bb6268f9de5b289c31a59da7617520ce8/server.go#L50-L51
The text was updated successfully, but these errors were encountered: