Your message dated Fri, 30 Jun 2017 18:15:32 +0200
with message-id <[email protected]>
and subject line Re: Bug#657964: openvpn: Can't connect to a VPN using SOCKS
proxy
has caused the Debian Bug report #657964,
regarding openvpn: Can't connect to a VPN using SOCKS proxy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
657964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657964
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openvpn
Version: 2.2.1-3
Severity: normal
Dear Maintainer,
When I try to connect to a VPN server, passing by a SOCKS proxy, I
always got this message:
Jan 30 18:28:19 localhost ovpn-foo[10502]: OpenVPN 2.2.1 i486-linux-gnu [SSL]
[LZO2] [EPOLL] [PKCS11] [eurephia] [MH] [PF_INET6] [IPv6 payload 20110424-2
(2.2RC2)] built on Dec 20 2011
Jan 30 18:28:19 localhost ovpn-foo[10502]: WARNING: No server certificate
verification method has been enabled. See http://openvpn.net/howto.html#mitm
for more info.
Jan 30 18:28:19 localhost ovpn-foo[10502]: NOTE: the current --script-security
setting may allow this configuration to call user-defined scripts
Jan 30 18:28:19 localhost ovpn-foo[10502]: LZO compression initialized
Jan 30 18:28:19 localhost ovpn-foo[10502]: Control Channel MTU parms [ L:1544
D:140 EF:40 EB:0 ET:0 EL:0 ]
Jan 30 18:28:19 localhost ovpn-foo[10502]: Socket Buffers: R=[87380->131072]
S=[16384->131072]
Jan 30 18:28:19 localhost ovpn-foo[10502]: Data Channel MTU parms [ L:1544
D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Jan 30 18:28:19 localhost ovpn-foo[10502]: Local Options hash (VER=V4):
'69109d17'
Jan 30 18:28:19 localhost ovpn-foo[10502]: Expected Remote Options hash
(VER=V4): 'c0103fa8'
Jan 30 18:28:19 localhost ovpn-foo[10503]: Attempting to establish TCP
connection with [AF_INET]127.0.0.1:12345 [nonblock]
Jan 30 18:28:19 localhost ovpn-foo[10503]: TCP connection established with
[AF_INET]127.0.0.1:12345
Jan 30 18:28:24 localhost ovpn-foo[10503]: recv_socks_reply: TCP port read
timeout expired: Operation now in progress (errno=115)
Jan 30 18:28:24 localhost ovpn-foo[10503]: TCP/UDP: Closing socket
Jan 30 18:28:24 localhost ovpn-foo[10503]: SIGTERM[soft,init_instance]
received, process exiting
The prox server running on localhost:12345 is a SSH prox, using 'ssh
server -D 12345'.
The SOCKS setting in the configuration file looks like this:
socks-proxy localhost 12345
If I remove this setting and if I'm on a network which I can directly
connect to the VPN server, everything works as expected.
I can connect and use the SOCKS proxy using other applications, such as
a web browser.
We can find some related issues looking on the Web, such as
http://readlist.com/lists/lists.sourceforge.net/openvpn-users/2/12784.html.
Thanks.
Jonathan
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages openvpn depends on:
ii debconf [debconf-2.0] 1.5.41
ii libc6 2.13-24
ii liblzo2-2 2.06-1
ii libpam0g 1.1.3-6
ii libpkcs11-helper1 1.09-1
ii libssl1.0.0 1.0.0e-3
ii net-tools 1.60-24.1
openvpn recommends no packages.
Versions of packages openvpn suggests:
ii openssl 1.0.0e-3
ii resolvconf 1.63
-- Configuration Files:
/etc/default/openvpn changed:
AUTOSTART="none"
OPTARGS=""
OMIT_SENDSIGS=0
-- debconf information:
openvpn/create_tun: false
--- End Message ---
--- Begin Message ---
Control: fixed -1 2.4~rc1-1
Control: forwarded -1 https://community.openvpn.net/openvpn/ticket/328
On Mon, Jan 30, 2012 at 06:37:04PM +0800, Jonathan Ballet wrote:
Hi,
according to the upstream bugtracker this should be fixed in 2.4
https://community.openvpn.net/openvpn/ticket/328
Bernhard
--- End Message ---
