[hichkas021]

Thanks for spam detection improvements.

I don’t think it’s a firewall issue. I was able to access Telegram over that SOCKS5 proxy.
Logs says “SOCKS5 ASSOCIATE SUCCESS port: 1082″ (as before on loopback)
“wiresock_enc.pcap” consists of bunch of UDP packets all with 200 bytes length forwarded to the SOCKS5 destination. The packets count is equal to the number of “[SOCKS5]: associate_to_socks5_proxy: SOCKS5 ASSOCIATE SUCCESS port: 1082” messages in the logs.

I increased v2rayN log verbosity and notice that whenever I close the “wiresock-client.exe” process with Ctrl+C, this will be appeared:
“wsarecv: An existing connection was forcibly closed by the remote host”

[hichkas021]

Thanks for your reply.

I tried running v2rayN on my other machine on the same local network, still same result.
However, I can see a 190 byte length WireGaurd packet in WireShark has sent from my primary device.

In intense DPI restricted environments (e.g. China, Iran), SOCKS5 is long gone. No VPN/Proxy protocol is actually working other than Trojan or VLESS/VMESS.

It’s very nice if we see built-in support for other obscured proxies in near future.

 

Off topic:
Your website blocked in my country, so I need VPN to access it.
Your web server also disallows to accept a post or comment from any kind of non-personal IP address.
I had a really hard time to overcome this issue!

[Author]

Posts