-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NAT:NoUDP #1137
Labels
bug
Something isn't working
Comments
不是bug你的配置问题。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The ping is green, but when connected, it says NAT:NoUDP and cannot access the network
To Reproduce
1.Open netch
2.Select server
3. Connection
Log
[2024-04-30 06:59:46][Information] Start MainController: VMess [2]Bypass LAN and China
[2024-04-30 06:59:46][Debug] Server Information: VMess auto + ws + xudp + none + none
[2024-04-30 06:59:46][Information] Built-in wintun.dll Hash: 8a0581991caf829cd92b27aabcb2bab618cc8fbc887d8f86a533c95d2e3f17d4
[2024-04-30 06:59:46][Information] Installed wintun.dll Hash: 8a0581991caf829cd92b27aabcb2bab618cc8fbc887d8f86a533c95d2e3f17d4
2024/04/30 06:59:57 [Wintun] ForceCloseWintunAdapterHandle: Failed to perform ioctl on adapter 14: Incorrect function. (Code 0x00000001)
2024/04/30 06:59:57 [Wintun] WintunDeleteAdapter: Failed to force close adapter 14 handles
2024/04/30 06:59:57 [Wintun] WintunCreateAdapter: Creating adapter
2024/04/30 06:59:57 [Wintun] SelectDriver: Using existing driver 0.14
[2024-04-30 06:59:58][Information] Net traffic processes: (13076)v2ray-sn
2024/04/30 07:00:13 [tun2socks][adns] DNS resolution failed: read tcp 10.0.236.10:62428->1.1.1.1:53: i/o timeout
2024/04/30 07:00:14 [tun2socks][adns] DNS resolution failed: read tcp 10.0.236.10:62433->1.1.1.1:53: i/o timeout
2024/04/30 07:00:15 [tun2socks][adns] DNS resolution failed: read tcp 10.0.236.10:62438->1.1.1.1:53: i/o timeout
2024/04/30 07:00:17 [tun2socks][adns] DNS resolution failed: read tcp 10.0.236.10:62443->1.1.1.1:53: i/o timeout
Environment
Additional information
No response
The text was updated successfully, but these errors were encountered: