Socks5 relay uses a wrong protocol?

[laohyx]

Hi, I am using pproxy as a socks5 relay server.
according to proto.py, Socks5.connect sends b'\x05\x01\x02\x01' + ... to server at first. But other socks5 clients only sends b'\x05\x02\x00\x01

Another proof is running two pproxy process, one is:

pproxy -l socks5://:8080/ -v

the other is:

pproxy -l socks5://:8081/ -v -r socks5://localhost:8080 --test http://ifconfig.co/

It results in Unsupported protocol b'1' from ::1 and Exception: Unknown remote protocol.

I am going to figure out the correct protocol then.

Thanks!

[qwj]

I cannot reproduce according to your test case. Socks5 works fine as the protocol defines. What is the version of pproxy? Did you use an old bugged version? laohyx <notifications@github.com>于2018年11月30日 周五11:03写道：

…

Hi, I am using pproxy as a socks5 relay server. according to proto.py, Socks5.connect sends b'\x05\x01\x02\x01' + ... to server at first. But other socks5 clients only sends b'\x05\x02\x00\x01 Another proof is running two pproxy process, one is: pproxy -l socks5://:8080/ -v the other is: pproxy -l socks5://:8081/ -v -r socks5://localhost:8080 --test http://ifconfig.co/ It results in Unsupported protocol b'1' from ::1 and Exception: Unknown remote protocol. I am going to figure out the correct protocol then. Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#17>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEBnhM7hBiGS9Pxss1gblrx_15bxWR-Qks5u0J_-gaJpZM4Y66_b> .

[laohyx]

Thanks for quick reply!
I am using 1.9.4, the latest version from pip.

I will try on linux. I used on windows before.

[qwj]

I will try on windows. It may be a bug on windows OS laohyx <notifications@github.com>于2018年11月30日 周五11:23写道：

…

Thanks for quick reply! I am using 1.9.4, the latest version from pip. I will try on linux. I used on windows before. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#17 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEBnhJuV2717e_V_QcEwhpg-lk94FEGjks5u0KSegaJpZM4Y66_b> .

[laohyx]

yeah, on linux it works fine. Close the issue for now

[laohyx]

Oh on Windows I modified some code to cause the error.

Then the reason not working for me is to use Shadowsocks client as upstream socks server.
Maybe it doesn't fully support socks5 protocol.