Closed freeacetone closed 2 years ago
It seems to be the problem of proxy server side. You see, the proxy server close the tcp connection (which is needed to be connected during the whole UDP session according to the RFC doc) and there's an EOF
error when performing SOCKS5 UDP associate handshakes.
Hmm. So it's really works with another proxy server side settings. Now I'm trying to find the cause of the error. If I get anything concrete, I'll write it here for the story.
So if 3proxy.cfg
contains just one any deny
rule - UDP in tun2socks not works.
I’ve never used 3proxy, so I don’t have any idea about it. You may contact the author of 3proxy to indicate the problem.
Environment
Windows 10 x64
v2.3.1
I saw
Game ready: optimized UDP transmission
in project description, but UDP taffic not works (also DNS too). In logs many lines like this:To Reproduce Steps to reproduce the behavior:
tun2socks-windows-amd64.exe -device tun://tun1 -proxy socks5://192.168.0.21:2010
10.10.10.1
to new TUN manuallyroute add 0.0.0.0 mask 0.0.0.0 10.10.10.1