vless udp 好像有点问题 #112
Description
Please answer all the questions with enough information. All issues not following this template will be closed immediately.
If you are not sure if your question is truely a bug in V2Ray, please discuss it here first.
-
What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?
v4.27.0 -
What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.
microsoft remote desktop -
What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)
vmess:3389tcp+udp可正常运作, vless:只可3389tcp.
3389udp vless有error.
-
What's your expectation?
3389udp vLess可正常运作. -
Please attach your configuration file (Mask IP addresses before submit this issue).
Server configuration:
// server-inbounds-vmess
{
"protocol": "vmess",
"port": 44391,
"settings": {
"clients": [{
"id": "UUID",
"alterId": 64
}
]
},
"streamSettings": {
"network": "h2",
"httpSettings": {
"host": "{fqdn}",
"path": "/path/"
},
"security": "none"
}
},
// server-inbounds-vless
{
"protocol": "vless",
"port": 44392,
"settings": {
"clients": [{
"id": "UUID"
}
],
"decryption": "none"
},
"streamsettings": {
"network": "h2",
"httpSettings": {
"host": "{fqdn}",
"path": "/path/"
},
"security": "none"
}
},Client configuration:
// "tag": "out-vless_h2"
{
"tag": "out-vless_h2",
"protocol": "vless",
"settings": {
"vnext": [{
"address": "fqdn",
"port": 443,
"users": [{
"UUID",
"encryption": "none"
}
]
}
]
},
"streamSettings": {
"network": "h2",
"httpSettings": {
"host": "fqdn",
"path": "/path/"
},
"security": "tls",
"tlsSettings": {
"allowInsecure": false
}
}
},
//out-vmess_h2
{
"tag": "out-vmess_h2",
"protocol": "vmess",
"settings": {
"vnext": [{
"address": "fqdn",
"port": 443,
"users": [{
"id": "UUID",
"alterId": 64,
"security": "aes-128-gcm",
"testsEnabled": "VMessAEAD"
}
]
}
]
},
"streamSettings": {
"network": "h2",
"httpSettings": {
"host": "fqdn",
"path": "/path/"
},
"security": "tls",
"tlsSettings": {
"allowInsecure": false
}
}
},- Please attach error logs, especially the bottom lines if the file is large. Error log file is usually at
/var/log/v2ray/error.logon Linux.
Server error log:
=== [[[ vless ]===
2020/08/24 12:38:21 [Info] [1739102002] v2ray.com/core/proxy/vless/inbound: received request for tcp:192.168.1.1:3389
2020/08/24 12:38:21 [Info] [1739102002] v2ray.com/core/app/dispatcher: taking detour [out-direct] for [tcp:192.168.1.1:3389]
2020/08/24 12:38:21 [Info] [1739102002] v2ray.com/core/proxy/freedom: opening connection to tcp:192.168.1.1:3389
2020/08/24 12:38:21 [Info] [1739102002] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:192.168.1.1:3389
2020/08/24 12:38:25 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/08/24 12:38:25 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe
2020/08/24 12:38:25 [Info] [3906587314] v2ray.com/core/proxy/vless/inbound: firstLen = 73
2020/08/24 12:38:25 [Info] [3906587314] v2ray.com/core/proxy/vless/inbound: received request for tcp:192.168.1.1:3389
2020/08/24 12:38:25 [Info] [3906587314] v2ray.com/core/app/dispatcher: taking detour [out-direct] for [tcp:192.168.1.1:3389]
2020/08/24 12:38:25 [Info] [3906587314] v2ray.com/core/proxy/freedom: opening connection to tcp:192.168.1.1:3389
2020/08/24 12:38:25 [Info] [3906587314] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:192.168.1.1:3389
2020/08/24 12:38:25 [Info] [1739102002] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/vless/inbound: connection ends > context canceled
2020/08/24 12:38:25 [Info] [1739102002] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2020/08/24 12:38:25 [Info] [454248298] v2ray.com/core/proxy/vless/inbound: firstLen = 1258
2020/08/24 12:38:25 [Info] [454248298] v2ray.com/core/proxy/vless/inbound: received request for udp:192.168.1.1:3389
2020/08/24 12:38:25 [Info] [454248298] v2ray.com/core/app/dispatcher: taking detour [out-direct] for [udp:192.168.1.1:3389]
2020/08/24 12:38:25 [Info] [454248298] v2ray.com/core/proxy/freedom: opening connection to udp:192.168.1.1:3389
Client error log:
=== [[[ vless ]===
2020/08/24 12:38:25 [Info] [4219923563] v2ray.com/core/app/dispatcher: taking detour [out-vless_h2] for [tcp:192.168.1.1:3389]
2020/08/24 12:38:25 [Info] [4219923563] v2ray.com/core/proxy/vless/outbound: tunneling request to tcp:192.168.1.1:3389 via tcp:fqdn:443
2020/08/24 12:38:25 [Info] [3881669924] v2ray.com/core/proxy/dokodemo: received request for 192.168.0.56:61423
2020/08/24 12:38:25 [Info] [3881669924] v2ray.com/core/app/dispatcher: taking detour [out-vless_h2] for [udp:192.168.11.1:3389]
2020/08/24 12:38:25 [Info] [3881669924] v2ray.com/core/proxy/vless/outbound: tunneling request to udp:192.168.1.1:3389 via tcp:fqdn:443- Please attach access log. Access log is usually at '/var/log/v2ray/access.log' on Linux.
// Please attach your server access log here.-
Other configurations (such as Nginx) and logs.
流程: v2client -(tls+h2)-> [internet] -(tls+h2)-> haproxy -(h2c)-> v2server -
If V2Ray doesn't run, please attach output from
--test.
The command is usually /usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json, but may vary according to your scenario.
- If V2Ray service doesn't run, please attach journal log.
Usual command is journalctl -u v2ray.
Please review your issue before submitting.