Opened 4 years ago

Closed 4 years ago

#606 closed Bug / Defect (invalid)

Adding and removing Route error on Win 10 Workstation OpenVPN 2.3.8

Reported by: opi Owned by:
Priority: minor Milestone:
Component: Networking Version: OpenVPN 2.3.8 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

Workstation
Win 10 64-bit
ASUS UX32VD Notebook

OpenVPN Client
2.3.8 openvpn-install-2.3.8-I601-x86_64.exe
TAP 9.21.1

OpenVPN 2.3.8 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Aug 4 2015
library versions: OpenSSL 1.0.2d 9 Jul 2015, LZO 2.08
Originally developed by James Yonan
Copyright (C) 2002-2010 OpenVPN Technologies, Inc. <sales@…>
Compile time defines: enable_crypto=yes enable_crypto_ofb_cfb=yes enable_debug=no enable_def_auth=yes enable_dlopen=unknown enable_dlopen_self=unknown enable_dlopen_self_static=unknown enable_fast_install=needless enable_fragment=yes enable_http_proxy=yes enable_iproute2=no enable_libtool_lock=yes enable_lzo=yes enable_lzo_stub=no enable_management=yes enable_multi=yes enable_multihome=yes enable_pam_dlopen=no enable_password_save=yes enable_pedantic=no enable_pf=yes enable_pkcs11=yes enable_plugin_auth_pam=no enable_plugin_down_root=no enable_plugins=yes enable_port_share=yes enable_selinux=no enable_server=yes enable_shared=yes enable_shared_with_static_runtimes=yes enable_small=no enable_snappy=no enable_socks=yes enable_ssl=yes enable_static=yes enable_strict=no enable_strict_options=no enable_systemd=no enable_win32_dll=yes enable_x509_alt_username=no with_crypto_library=openssl with_gnu_ld=yes with_mem_check=no with_plugindir='$(libdir)/openvpn/plugins' with_special_build= with_sysroot=no

The client is started with administrator priviledge and connection works without any apparent issue except the error in the log when establishing the connection and disconnecting (see log entries below)

When connecting
ROUTE: route addition failed using CreateIpForwardEntry?: The object already exists

When disconnecting
ROUTE: route deletion failed using DeleteIpForwardEntry?: Element not found.

Change History (2)

comment:1 Changed 4 years ago by Gert Döring

Priority: majorminor

If it works, it's certainly not a "major" bug :-)

Could you attach a log with --verb 4 so we can see which route is actually failing? It might be that the server pushes something which is in use locally (like, "route 192.168.1.0/24" if the local network is 192.168.1.x) - so it tells you, but goes on.

comment:2 Changed 4 years ago by Gert Döring

Resolution: invalid
Status: newclosed

No log, no bug. Closing.

Please reopen if you can provide the necessary information so we can actually work on that.

Note: See TracTickets for help on using tickets.