Code: Select all
recv_socks_reply: Socks proxy returned bad reply
Code: Select all
Invalid SOCKS command: '3'
The Arch client is running the openvpn-obfs package https://aur.archlinux.org/packages/openvpn-obfs/ ("OpenVPN binary with obfs patch"), and openvpn reports its version as 2.3.6. I've installed obfsproxy using pip2, and it reports its version as 0.2.13. I've also tried this with the Arch obfsproxy package, with the same results.
The client config:
On the client I start obfsproxy like this:client
dev tun
proto udp
remote SERVER_IP 21194
socks-proxy-retry
socks-proxy 127.0.0.1 443
route SERVER_IP 255.255.255.255 net_gateway
resolv-retry infinite
nobind
persist-key
persist-tun
ca PATH_TO_FILE
cert PATH_TO_FILE
key PATH_TO_FILE
remote-cert-tls server
tls-auth PATH_TO_FILE
comp-lzo
verb 6
tun-mtu 1500
tun-mtu-extra 32
mssfix 1400
Code: Select all
sudo obfsproxy --log-file=obfsproxy.log --log-min-severity=debug obfs3 socks 127.0.0.1:443
That repeats indefinitely. Meanwhile, the output of obfsproxy is:LZO compression initialized
Control Channel MTU parms [ L:1574 D:166 EF:66 EB:0 ET:0 EL:10 ]
Socket Buffers: R=[212992->131072] S=[212992->131072]
Data Channel MTU parms [ L:1574 D:1400 EF:42 EB:135 ET:32 EL:10 AF:3/1 ]
Local Options String: 'V4,dev-type tun,link-mtu 1574,tun-mtu 1532,proto UDPv4,comp-lzo,keydir 1,cipher BF-CBC,auth SHA1,keysize 128,tls-auth,key-method 2,tls-client'
Expected Remote Options String: 'V4,dev-type tun,link-mtu 1574,tun-mtu 1532,proto UDPv4,comp-lzo,keydir 0,cipher BF-CBC,auth SHA1,keysize 128,tls-auth,key-method 2,tls-server'
Local Options hash (VER=V4): 'ec497616'
Expected Remote Options hash (VER=V4): '7cd8ed90'
Attempting to establish TCP connection with [AF_INET]127.0.0.1:443 [nonblock]
TCP connection established with [AF_INET]127.0.0.1:443
recv_socks_reply: Socks proxy returned bad reply
TCP/UDP: Closing socket
SIGUSR1[soft,init_instance] received, process restarting
Restart pause, 5 second(s)
Re-using SSL/TLS context
This, too, repeats indefinitely.[INFO] OBFSSOCKSv5Factory starting on 443
[INFO] Starting factory <obfsproxy.network.socks.OBFSSOCKSv5Factory instance at 0x7f6e618bc710>
[DEBUG] socks_fact_0x7f6e618bc710: Starting up SOCKS server factory.
[INFO] Launched 'socks' listener at '[scrubbed]:443' for transport 'obfs3'.
[DEBUG] socks_fact_0x7f6e618bc710: New connection.
[ERROR] Invalid SOCKS command: '3'
[DEBUG] socks_up_0x7f6e618b8f10: Connection was lost (Connection was closed cleanly.).
[DEBUG] socks_up_0x7f6e618b8f10: Closing connection.
[DEBUG] circ_0x7f6e618bce60: Tearing down circuit.
[DEBUG] socks_fact_0x7f6e618bc710: New connection.
[ERROR] Invalid SOCKS command: '3'
Does anyone know why they won't talk to each other?
Thanks!
Eric