Does not support standard socks5 protocol

Open f4nff opened this issue 3 years ago • 1 comments

After my test, socks5 is not supported?

Jan 11 '22 06:01 f4nff

Dispatch: IPv4 src=192.168.2.4 dst=192.168.1.129 proto=TCP
\ TCP src=1082 dst=18629 syn seq=3425872776 ack=869094521 win=8192 len=0 mss=1460
IPv4 src=192.168.1.129 dst=192.168.2.4 proto=TCP
\ TCP src=18630 dst=1082 syn seq=1147468106 win=64240 len=0 mss=1460
Dispatch: IPv4 src=192.168.2.4 dst=192.168.1.129 proto=TCP
\ TCP src=1082 dst=18630 syn seq=3147499190 ack=1147468107 win=8192 len=0 mss=1460
IPv4 src=192.168.1.129 dst=192.168.2.4 proto=TCP
\ TCP src=18631 dst=1082 syn seq=2076548205 win=64240 len=0 mss=1460
Dispatch: IPv4 src=192.168.2.4 dst=192.168.1.129 proto=TCP
\ TCP src=1082 dst=18631 syn seq=2218419091 ack=2076548206 win=8192 len=0 mss=1460
IPv4 src=192.168.1.129 dst=104.101.190.90 proto=TCP
\ TCP src=18546 dst=443 seq=1319448259 ack=2975521016 win=1026 len=0
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `false`,
 right: `true`', src/main.rs:387:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Jan 11 '22 07:01 f4nff