Closed ghost closed 4 years ago
we were using ipv6 , but we have problem with h2s
2019/03/04 16:18:12.772507 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:13.863631 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:14.445864 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:14.560087 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:14.791805 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:16.867652 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:17.780151 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:18.875932 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:18.875946 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:19.782748 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:19.782799 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:20.874084 h2s: serve: read request: unexpected command 0x03 2019/03/04 16:18:21.782399 h2s: serve: read request: unexpected command 0x03
"unexpected command 0x03" has nothing to do with ipv6.
"CMD 3" means "UDP ASSOCIATE" in SOCKS5 as per RFC1928. HTTPS proxy does not support UDP, so h2s doesn't handle any UDP association in SOCKS5 as well.
we were using ipv6 , but we have problem with h2s