UDP relay/proxying in SOCKS5 mode does not work #2944
Comments
|
So yeah, it looks like SOCKS5 protocol is poorly imlplemented. fixes the issue because it appears to be unable to rely UDP packets as a proper SOCKS proxy (including proxying DNS queries, as per Firefox capability). Even if it did I assume it would not be shaped by Which leaves |
Kein
changed the title
|
Actually, I've tested this more without UDP mode and can confirm this has nothing to do with UDP - it just fails with Discord uploads at all. |
|
It is almost impossible to use SOCKS5 UDP Associate without transparent proxy method because in the real world almost no software that supports SOCKS5 actually supports SOCKS5 UDP Associate (including but not limiting to Chrome/Firefox). And your log shows nothing about UDP traffic. If you can fix something by turning off sniffing, usually it means that some traffic has mismatched SNI (or HTTP Host, or something recognized as them) and destination. |
I actually can't, I was wrong. It was just a coincidence that the bug did not appear after I disabled sniffing and UDP and restarted proxy. Right now I'm running with both of these options enabled and it works, but randomly the bug re-appears. It is not related to any of the settings I've tried, it is a fundamental issue of the v2ray vmess protocol it seems. The worst part, as you have seen, logs in |
What version of V2Ray are you using?
v5.14.1
What's your scenario of using V2Ray?
Bypass RU/CIS blackbox DPI that throttles any traffic it does not like.
What problems have you encountered?
Unable to upload pictures on some resources, namely Discord
What's your expectation?
it just works, like Shadowsocks.
Please attach your configuration here
CLIENT:
{ "inbounds": [ { "port": 1083, "listen": "127.0.0.1", "protocol": "socks", "settings": { "udp": true } } ], "outbounds": [ { "protocol": "vmess", "settings": { "vnext": [ { "address": "ipv4.ipv4.ipv4.ipv4", "port": 49533, "users": [ { "id": "3571dcec-073c-4c0a-8bab-0d84351be678" } ] } ] } }, { "protocol": "freedom", "tag": "direct" } ], "routing": { "domainStrategy": "IPOnDemand", "rules": [ { "type": "field", "ip": [ "geoip:private" ], "outboundTag": "direct" } ] } }SERVER:
{ "inbounds": [ { "port": 1081, "protocol": "vmess", "settings": { "clients": [ { "id": "3571dcec-073c-4c0a-8bab-0d84351be678" } ] } } ], "outbounds": [ { "protocol": "freedom" } ] }Please attach error logs here
SERVER
error.log
CLIENT
access.log
error.log
Other configurations (such as Nginx) and logs here
N/A
Additional info
V2ray used in standalone in SOCKS5 mode.
Firefox 123 in FULL SOCKS5 mode (including UDP proxying of DNS)
ANY attempt tp upload any picture on Discord from local PC fails. Upload works on something like
imgur.comwithout issues. Switching toShadowsockson the SAME VPS and the same client pc works flawlessly. The issue appears to be with v2ray SOCKS implementation (?, it is lacking?)The text was updated successfully, but these errors were encountered: