Opened 3 years ago

Last modified 21 months ago

#665 new Bug / Defect

Route: Waiting for TUN/TAP interface to come up...

Reported by: hildeb Owned by:
Priority: major Milestone:
Component: Generic / unclassified Version: OpenVPN 2.3.10 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc: selvanair

Description

On a pristine Win10 installation, the TAP interface won't come up:

Wed Mar 02 14:26:57 2016 OpenVPN 2.3.10 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Jan 4 2016
Wed Mar 02 14:26:57 2016 Windows version 6.2 (Windows 8 or greater)
Wed Mar 02 14:26:57 2016 library versions: OpenSSL 1.0.1q 3 Dec 2015, LZO 2.09
Enter Management Password:
Wed Mar 02 14:26:57 2016 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed Mar 02 14:26:57 2016 Need hold release from management interface, waiting...
Wed Mar 02 14:26:58 2016 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed Mar 02 14:26:58 2016 MANAGEMENT: CMD 'state on'
Wed Mar 02 14:26:58 2016 MANAGEMENT: CMD 'log all on'
Wed Mar 02 14:26:58 2016 MANAGEMENT: CMD 'hold off'
Wed Mar 02 14:26:58 2016 MANAGEMENT: CMD 'hold release'
Wed Mar 02 14:27:12 2016 MANAGEMENT: CMD 'username "Auth" "tsotsasn"'
Wed Mar 02 14:27:12 2016 MANAGEMENT: CMD 'password [...]'
Wed Mar 02 14:27:12 2016 Control Channel Authentication: tls-auth using INLINE static key file
Wed Mar 02 14:27:12 2016 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Mar 02 14:27:12 2016 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Mar 02 14:27:12 2016 Socket Buffers: R=[65536->65536] S=[65536->65536]
Wed Mar 02 14:27:12 2016 MANAGEMENT: >STATE:1456925232,RESOLVE,
Wed Mar 02 14:27:12 2016 UDPv4 link local: [undef]
Wed Mar 02 14:27:12 2016 UDPv4 link remote: [AF_INET]193.175.73.200:1194
Wed Mar 02 14:27:12 2016 MANAGEMENT: >STATE:1456925232,WAIT
,
Wed Mar 02 14:27:13 2016 MANAGEMENT: >STATE:1456925233,AUTH,
Wed Mar 02 14:27:13 2016 TLS: Initial packet from [AF_INET]193.175.73.200:1194, sid=6d40a300 9f685b6b
Wed Mar 02 14:27:13 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Mar 02 14:27:13 2016 VERIFY OK: depth=1, C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=Charite-VPN CA, name=EasyRSA, emailAddress=vpn@…
Wed Mar 02 14:27:13 2016 VERIFY OK: nsCertType=SERVER
Wed Mar 02 14:27:13 2016 Validating certificate extended key usage
Wed Mar 02 14:27:13 2016 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Wed Mar 02 14:27:13 2016 VERIFY EKU OK
Wed Mar 02 14:27:13 2016 VERIFY X509NAME OK: C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=openvpn.charite.de, emailAddress=vpn@…
Wed Mar 02 14:27:13 2016 VERIFY OK: depth=0, C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=openvpn.charite.de, emailAddress=vpn@…
Wed Mar 02 14:27:13 2016 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Wed Mar 02 14:27:13 2016 Data Channel Encrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Mar 02 14:27:13 2016 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Wed Mar 02 14:27:13 2016 Data Channel Decrypt: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Mar 02 14:27:13 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Wed Mar 02 14:27:13 2016 [openvpn.charite.de] Peer Connection Initiated with [AF_INET]193.175.73.200:1194
Wed Mar 02 14:27:14 2016 MANAGEMENT: >STATE:1456925234,GET_CONFIG
,
Wed Mar 02 14:27:15 2016 SENT CONTROL [openvpn.charite.de]: 'PUSH_REQUEST' (status=1)
Wed Mar 02 14:27:15 2016 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 141.42.3.33,dhcp-option DNS 141.42.2.22,dhcp-option DOMAIN charite.de,register-dns,block-outside-dns,route-gateway 172.29.0.1,topology subnet,ping 10,ping-restart 30,route 10.28.0.0 255.255.0.0,route 10.32.0.0 255.224.0.0,route 172.16.0.0 255.254.0.0,route 192.168.192.0 255.255.192.0,route 141.42.0.0 255.255.0.0,route 193.175.72.0 255.255.255.0,route 193.175.74.0 255.255.254.0,route 194.94.4.0 255.255.254.0,peer-id 16,ifconfig 172.29.8.203 255.255.192.0'
Wed Mar 02 14:27:15 2016 OPTIONS IMPORT: timers and/or timeouts modified
Wed Mar 02 14:27:15 2016 OPTIONS IMPORT: --ifconfig/up options modified
Wed Mar 02 14:27:15 2016 OPTIONS IMPORT: route options modified
Wed Mar 02 14:27:15 2016 OPTIONS IMPORT: route-related options modified
Wed Mar 02 14:27:15 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Mar 02 14:27:15 2016 OPTIONS IMPORT: peer-id set
Wed Mar 02 14:27:15 2016 OPTIONS IMPORT: adjusting link_mtu to 1573
Wed Mar 02 14:27:15 2016 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=6 HWADDR=00:03:7f:bf:0a:eb
Wed Mar 02 14:27:15 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Mar 02 14:27:15 2016 MANAGEMENT: >STATE:1456925235,ASSIGN_IP,,172.29.8.203,
Wed Mar 02 14:27:15 2016 open_tun, tt->ipv6=0
Wed Mar 02 14:27:15 2016 TAP-WIN32 device [Ethernet] opened:
.\Global\{CE798891-9C1C-4C0C-8FAF-27116B9D3226}.tap
Wed Mar 02 14:27:15 2016 TAP-Windows Driver Version 9.21
Wed Mar 02 14:27:15 2016 Set TAP-Windows TUN subnet mode network/local/netmask = 172.29.0.0/172.29.8.203/255.255.192.0 [SUCCEEDED]
Wed Mar 02 14:27:15 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 172.29.8.203/255.255.192.0 on interface {CE798891-9C1C-4C0C-8FAF-27116B9D3226} [DHCP-serv: 172.29.63.254, lease-time: 31536000]
Wed Mar 02 14:27:15 2016 NOTE: FlushIpNetTable? failed on interface [2] {CE798891-9C1C-4C0C-8FAF-27116B9D3226} (status=1168) : Element nicht gefunden.
Wed Mar 02 14:27:20 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:20 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:25 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:25 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:27 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:27 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:28 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:28 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:29 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:29 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:31 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:31 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:32 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:32 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:33 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:33 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:34 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:34 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:36 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:36 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:37 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:37 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:38 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:38 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:39 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:39 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:40 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:40 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:41 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:41 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:42 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:42 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:43 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:43 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:44 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:44 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:45 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:45 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:46 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:46 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:47 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:47 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:48 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:48 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:49 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:49 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 02 14:27:50 2016 TEST ROUTES: 0/8 succeeded len=8 ret=0 a=0 u/d=up
Wed Mar 02 14:27:50 2016 MANAGEMENT: >STATE:1456925270,ADD_ROUTES,
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\route.exe ADD 10.28.0.0 MASK 255.255.0.0 172.29.0.1
Wed Mar 02 14:27:50 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:27:50 2016 Route addition via IPAPI failed [adaptive]
Wed Mar 02 14:27:50 2016 Route addition fallback to route.exe
Wed Mar 02 14:27:50 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\route.exe ADD 10.32.0.0 MASK 255.224.0.0 172.29.0.1
Wed Mar 02 14:27:50 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:27:50 2016 Route addition via IPAPI failed [adaptive]
Wed Mar 02 14:27:50 2016 Route addition fallback to route.exe
Wed Mar 02 14:27:50 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\route.exe ADD 172.16.0.0 MASK 255.254.0.0 172.29.0.1
Wed Mar 02 14:27:50 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:27:50 2016 Route addition via IPAPI failed [adaptive]
Wed Mar 02 14:27:50 2016 Route addition fallback to route.exe
Wed Mar 02 14:27:50 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\route.exe ADD 192.168.192.0 MASK 255.255.192.0 172.29.0.1
Wed Mar 02 14:27:50 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:27:50 2016 Route addition via IPAPI failed [adaptive]
Wed Mar 02 14:27:50 2016 Route addition fallback to route.exe
Wed Mar 02 14:27:50 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\route.exe ADD 141.42.0.0 MASK 255.255.0.0 172.29.0.1
Wed Mar 02 14:27:50 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:27:50 2016 Route addition via IPAPI failed [adaptive]
Wed Mar 02 14:27:50 2016 Route addition fallback to route.exe
Wed Mar 02 14:27:50 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\route.exe ADD 193.175.72.0 MASK 255.255.255.0 172.29.0.1
Wed Mar 02 14:27:50 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:27:50 2016 Route addition via IPAPI failed [adaptive]
Wed Mar 02 14:27:50 2016 Route addition fallback to route.exe
Wed Mar 02 14:27:50 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\route.exe ADD 193.175.74.0 MASK 255.255.254.0 172.29.0.1
Wed Mar 02 14:27:50 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:27:50 2016 Route addition via IPAPI failed [adaptive]
Wed Mar 02 14:27:50 2016 Route addition fallback to route.exe
Wed Mar 02 14:27:50 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\route.exe ADD 194.94.4.0 MASK 255.255.254.0 172.29.0.1
Wed Mar 02 14:27:50 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:27:50 2016 Route addition via IPAPI failed [adaptive]
Wed Mar 02 14:27:50 2016 Route addition fallback to route.exe
Wed Mar 02 14:27:50 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.1.1 p=0 i=6 t=4 pr=3 a=186243 h=0 m=25/0/0/0/0
10.28.0.0 255.255.0.0 172.29.0.1 p=0 i=6 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
10.32.0.0 255.224.0.0 172.29.0.1 p=0 i=6 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=1474645 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1474645 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1474645 h=0 m=306/0/0/0/0
141.42.0.0 255.255.0.0 172.29.0.1 p=0 i=6 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
172.16.0.0 255.254.0.0 172.29.0.1 p=0 i=6 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
192.168.1.0 255.255.255.0 192.168.1.24 p=0 i=6 t=3 pr=2 a=186243 h=0 m=281/0/0/0/0
192.168.1.24 255.255.255.255 192.168.1.24 p=0 i=6 t=3 pr=2 a=186243 h=0 m=281/0/0/0/0
192.168.1.255 255.255.255.255 192.168.1.24 p=0 i=6 t=3 pr=2 a=186243 h=0 m=281/0/0/0/0
192.168.192.0 255.255.192.0 172.29.0.1 p=0 i=6 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
193.175.72.0 255.255.255.0 172.29.0.1 p=0 i=6 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
193.175.74.0 255.255.254.0 172.29.0.1 p=0 i=6 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
194.94.4.0 255.255.254.0 172.29.0.1 p=0 i=6 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=1474645 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 192.168.1.24 p=0 i=6 t=3 pr=2 a=1474597 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=1474645 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 192.168.1.24 p=0 i=6 t=3 pr=2 a=1474597 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
Atheros AR5005GS-Drahtlosnetzwerkadapter

Index = 6
GUID = {43FA17D6-0B42-4B95-B760-092C876CA43B}
IP = 192.168.1.24/255.255.255.0
MAC = 00:03:7f:bf:0a:eb
GATEWAY = 192.168.1.1/255.255.255.255
DHCP SERV = 192.168.1.1/255.255.255.255
DHCP LEASE OBTAINED = Wed Mar 02 12:52:53 2016
DHCP LEASE EXPIRES = Wed Mar 09 12:52:53 2016
DNS SERV = 192.168.1.1/255.255.255.255

Wed Mar 02 14:27:50 2016 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Wed Mar 02 14:27:50 2016 MANAGEMENT: >STATE:1456925270,CONNECTED,ERROR,172.29.8.203,193.175.73.200
Wed Mar 02 14:27:50 2016 Start net commands...
Wed Mar 02 14:27:50 2016 C:\WINDOWS\system32\net.exe stop dnscache
Wed Mar 02 14:27:58 2016 C:\WINDOWS\system32\net.exe start dnscache
Wed Mar 02 14:27:58 2016 ERROR: Windows ipconfig command failed: returned error code 2
Wed Mar 02 14:27:58 2016 C:\WINDOWS\system32\ipconfig.exe /flushdns
Wed Mar 02 14:27:58 2016 C:\WINDOWS\system32\ipconfig.exe /registerdns
Wed Mar 02 14:28:01 2016 End net commands...
Wed Mar 02 14:30:46 2016 SIGTERM received, sending exit notification to peer
Wed Mar 02 14:30:47 2016 C:\WINDOWS\system32\route.exe DELETE 194.94.4.0 MASK 255.255.254.0 172.29.0.1
Wed Mar 02 14:30:47 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:30:47 2016 Route deletion via IPAPI failed [adaptive]
Wed Mar 02 14:30:47 2016 Route deletion fallback to route.exe
Wed Mar 02 14:30:47 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:30:47 2016 C:\WINDOWS\system32\route.exe DELETE 193.175.74.0 MASK 255.255.254.0 172.29.0.1
Wed Mar 02 14:30:47 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:30:47 2016 Route deletion via IPAPI failed [adaptive]
Wed Mar 02 14:30:47 2016 Route deletion fallback to route.exe
Wed Mar 02 14:30:47 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:30:47 2016 C:\WINDOWS\system32\route.exe DELETE 193.175.72.0 MASK 255.255.255.0 172.29.0.1
Wed Mar 02 14:30:47 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:30:47 2016 Route deletion via IPAPI failed [adaptive]
Wed Mar 02 14:30:47 2016 Route deletion fallback to route.exe
Wed Mar 02 14:30:47 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:30:47 2016 C:\WINDOWS\system32\route.exe DELETE 141.42.0.0 MASK 255.255.0.0 172.29.0.1
Wed Mar 02 14:30:47 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:30:47 2016 Route deletion via IPAPI failed [adaptive]
Wed Mar 02 14:30:47 2016 Route deletion fallback to route.exe
Wed Mar 02 14:30:47 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:30:47 2016 C:\WINDOWS\system32\route.exe DELETE 192.168.192.0 MASK 255.255.192.0 172.29.0.1
Wed Mar 02 14:30:47 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:30:47 2016 Route deletion via IPAPI failed [adaptive]
Wed Mar 02 14:30:47 2016 Route deletion fallback to route.exe
Wed Mar 02 14:30:47 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:30:47 2016 C:\WINDOWS\system32\route.exe DELETE 172.16.0.0 MASK 255.254.0.0 172.29.0.1
Wed Mar 02 14:30:47 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:30:47 2016 Route deletion via IPAPI failed [adaptive]
Wed Mar 02 14:30:47 2016 Route deletion fallback to route.exe
Wed Mar 02 14:30:47 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:30:47 2016 C:\WINDOWS\system32\route.exe DELETE 10.32.0.0 MASK 255.224.0.0 172.29.0.1
Wed Mar 02 14:30:47 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:30:47 2016 Route deletion via IPAPI failed [adaptive]
Wed Mar 02 14:30:47 2016 Route deletion fallback to route.exe
Wed Mar 02 14:30:47 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:30:47 2016 C:\WINDOWS\system32\route.exe DELETE 10.28.0.0 MASK 255.255.0.0 172.29.0.1
Wed Mar 02 14:30:47 2016 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Wed Mar 02 14:30:47 2016 Route deletion via IPAPI failed [adaptive]
Wed Mar 02 14:30:47 2016 Route deletion fallback to route.exe
Wed Mar 02 14:30:47 2016 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Wed Mar 02 14:30:47 2016 Closing TUN/TAP interface
Wed Mar 02 14:30:47 2016 SIGTERM[soft,exit-with-notification] received, process exiting
Wed Mar 02 14:30:47 2016 MANAGEMENT: >STATE:1456925447,EXITING,exit-with-notification

Windows 10 pro
4 GB RAM
64 Bit, x86

Attachments (1)

system.png (93.0 KB) - added by hildeb 3 years ago.
system Info

Download all attachments as: .zip

Change History (14)

Changed 3 years ago by hildeb

Attachment: system.png added

system Info

comment:1 Changed 3 years ago by debbie10t

Have you started Windows DHCP Client Service ?

comment:2 Changed 3 years ago by hildeb

Yes, it's active, since the real IP is obtained (1 hour prior to the VPN connection attempt) using DHCP!

IP = 192.168.1.24/255.255.255.0
MAC = 00:03:7f:bf:0a:eb
GATEWAY = 192.168.1.1/255.255.255.255
DHCP SERV = 192.168.1.1/255.255.255.255
DHCP LEASE OBTAINED = Wed Mar 02 12:52:53 2016

comment:3 Changed 3 years ago by debbie10t

Please post your openvpn configuration file.

comment:4 Changed 3 years ago by hildeb

# Konfiguration fuer Charite-OpenVPN
client
dev tun

<connection>
proto udp
remote openvpn.charite.de
port 1194
explicit-exit-notify
nobind
</connection>

<connection>
proto udp
remote 193.175.73.200
port 1194
explicit-exit-notify
nobind
</connection>

<connection>
proto tcp
remote openvpn.charite.de
port 1194
</connection>

<connection>
proto tcp
remote 193.175.73.200
port 1194
</connection>

resolv-retry infinite

cipher AES-256-CBC
auth SHA256
ns-cert-type server
verify-x509-name 'C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=openvpn.charite.de, emailAddress=vpn@…' subject
remote-cert-eku "TLS Web Server Authentication"

persist-key
persist-tun
comp-lzo
verb 3
reneg-sec 0
auth-user-pass
auth-nocache
script-security 2
mute-replay-warnings

key-direction 1
<tls-auth>
#
# 2048 bit OpenVPN static key
#


...


</tls-auth>

<ca>


...


</ca>

<key>


...


</key>

<cert>
Certificate:

Data:

Version: 3 (0x2)
Serial Number: 7144 (0x1be8)

Signature Algorithm: sha256WithRSAEncryption

Issuer: C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=Charite-VPN CA/name=EasyRSA/emailAddress=vpn@…
Validity

Not Before: Aug 5 13:02:11 2015 GMT
Not After : Aug 2 13:02:11 2025 GMT

Subject: C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=tsotsasn/emailAddress=vpn@…
Subject Public Key Info:

Public Key Algorithm: rsaEncryption

Public-Key: (2048 bit)
Modulus:

00:ea:b5:64:20:15:5f:99:55:d3:b0:84:d6:d7:d0:
dd:51:49:bc:bf:26:43:d6:59:52:d7:ed:5c:a9:41:
07:50:86:e4:7d:cd:8a:b4:d2:6d:fa:fd:77:e1:4a:
1b:b9:53:97:c9:a7:5e:80:fa:1e:9c:a8:b2:d4:ec:
2f:fb:1d:d8:b4:72:e0:d3:3e:b6:0a:51:ad:23:e8:
49:92:8c:45:39:48:af:09:be:e1:12:24:30:11:c1:
d1:f9:ec:c0:88:4f:60:29:62:43:70:a4:07:54:bf:
88:41:dd:cf:1f:29:8f:da:e6:2c:ce:78:2e:c1:f5:
70:c7:ac:64:cc:b5:74:59:00:7c:9d:99:3b:ab:75:
39:a3:94:74:08:0d:bc:e3:47:4e:ff:04:06:79:81:
e5:e1:72:bb:01:21:d8:ae:48:8c:23:08:69:57:bf:
4a:f5:de:7d:77:8c:11:cc:f6:ec:82:c5:1b:5e:de:
cb:05:58:e8:43:28:cc:ea:24:4f:0c:25:ad:8f:f3:
94:f1:3a:97:74:67:e2:b9:65:7f:e7:dc:d0:c1:04:
97:25:0b:3f:ba:f3:76:1c:99:d2:e5:d7:4d:0f:7e:
01:8a:5c:53:17:20:4c:a4:b9:1d:f0:24:e6:67:39:
dc:13:8d:3d:39:b8:27:75:1a:2b:66:bd:11:7b:78:
15:79

Exponent: 65537 (0x10001)

X509v3 extensions:

X509v3 Basic Constraints:

CA:FALSE

Netscape Comment:

Easy-RSA Generated Certificate

X509v3 Subject Key Identifier:

1A:CF:A5:D4:31:D6:E5:18:0D:E5:1A:52:6E:F5:8D:98:B8:E5:9F:0E

X509v3 Authority Key Identifier:

keyid:10:65:59:FB:70:DB:E1:92:C8:39:9C:84:A0:FD:00:AB:A3:F2:CA:DC
DirName:/C=DE/ST=Berlin/L=Berlin/O=Charite-VPN/OU=GB-IT/CN=Charite-VPN CA/name=EasyRSA/emailAddress=vpn@…
serial:B8:28:31:2F:58:94:16:93

X509v3 Extended Key Usage:

TLS Web Client Authentication

X509v3 Key Usage:

Digital Signature

X509v3 Subject Alternative Name:

DNS:tsotsasn

Signature Algorithm: sha256WithRSAEncryption

a8:60:f1:a6:94:cb:b2:81:72:ea:a2:59:6a:b1:0b:ea:e2:57:
ed:76:24:93:df:e6:b5:a9:cb:c0:2d:df:cd:8e:6b:7a:db:f1:
c6:54:6b:ca:c0:59:31:02:f1:1c:36:ba:07:97:98:9d:61:df:
c0:f0:44:54:3b:cf:4a:07:51:ae:82:de:df:a1:55:fd:6a:29:
2e:53:f6:6c:46:0c:c4:30:05:8d:81:d8:73:18:c0:80:17:52:
b0:45:d7:33:fd:f1:c9:aa:ac:ce:52:3e:d6:49:f5:e3:3f:52:
94:b6:28:cc:3e:a0:0e:17:2d:25:c2:1b:e1:a2:38:c5:fe:a7:
35:b8:4b:ed:03:fd:d4:3f:3b:53:e2:9c:e4:23:61:3f:83:a3:
ce:bb:53:43:03:04:e4:3a:61:81:02:f1:7e:0e:e6:14:84:b8:
83:7f:a7:2b:74:b9:8a:18:0c:5b:b5:4e:27:5c:e7:96:a9:61:
84:90:98:4f:a2:ff:91:e8:49:ac:26:95:d2:ae:32:38:3c:3c:
75:8b:95:34:be:29:ef:0c:c3:5a:7c:79:ba:09:a7:eb:63:aa:
36:ae:84:5d:08:2f:20:bf:89:ad:48:72:b6:3e:1a:c4:9b:a9:
cf:3c:01:94:58:f6:ca:d5:32:7f:3b:ea:5e:94:1f:1c:3a:39:
98:2d:0a:e3


...


</cert>

comment:5 Changed 3 years ago by debbie10t

Try this approach:

In Windows Network connections >Rename your TAP-Windows Adaptor >

From: Local Area Connection

To: tun0

Then
Add this to the TOP of your client config file:

dev-type tun
dev-node tun0

And remove this from your client config file:

persist-key
persist-tun
Last edited 3 years ago by debbie10t (previous) (diff)

comment:6 Changed 3 years ago by dms

I've started rolling out openvpn 2.3.12 to a suit of laptops and am seeing this issue regularly.

What we see is the same as above namely repeated lines of:

"Route: Waiting for TUN/TAP interface to come up..." and then the routing information is not set up correctly on the client and hence no vpn traffic works, although the connection is made to the server.

The procedure mentioned by debbie10t above makes no difference to our laptops connecting to the vpn over wifi (a couple of brands of laptops are being used). I have never yet seen this issue using openvpn on a desk over a wired network.

comment:7 Changed 3 years ago by john439

Same problem with 2.3.13, Upgrading from older openvpn.

None of the suggestions worked.

Solution, uninstall openvpn, uninstalled the TAP device/driver
then install openvpn again, which installs TAP device if none present. working now.

1) uninstall openvpn, click "Uninstall" in OpenVPN directory
e.g. C:\Program Files (x86)\OpenVPN

2) uninstall TAP , open "Network and Sharing Center",
Control Panel\Network and Internet\Network and Sharing Center
click "change adapter settings"
right click "TAP-Windows Adapter V9 #4"
click "Properties"
click "Uninstall"
restart PC

3) install openvpn, this installs TAP driver if not present.

Last edited 3 years ago by john439 (previous) (diff)

comment:8 Changed 3 years ago by mltgames

If you have windows 8 or 10 I fixed this by doing an full restart/reboot on windows.

If I was fast restarting, it wasnt enought, but the full restart/reboot worked.

You need to run cmd.exe as admin and run this command "shutdown /s /t 0" it will perform a full restart and now everything will work after that.

comment:9 Changed 3 years ago by Gert Döring

Cc: selvanair added

also discussed in #807, though this shows a *different* failure mode and also affects 2.3.x (in 807 I assumed it's a new problem in 2.4.0)

comment:10 in reply to:  8 Changed 22 months ago by Rudder2

Replying to mltgames:

If you have windows 8 or 10 I fixed this by doing an full restart/reboot on windows.

If I was fast restarting, it wasnt enought, but the full restart/reboot worked.

You need to run cmd.exe as admin and run this command "shutdown /s /t 0" it will perform a full restart and now everything will work after that.

This worked for me! Thank you very much!

comment:11 Changed 21 months ago by engy

I had a problem with disabled DHCP media sense. I created a pull request to warn about that https://github.com/OpenVPN/openvpn/pull/97

Can be checked with netsh interface ipv4 show global
and fixed with netsh interface ipv4 set global dhcpmediasense=enabled

Last edited 21 months ago by engy (previous) (diff)

comment:12 Changed 21 months ago by selvanair

If you look at this thread, some got it fixed by reinstalling TAP, some by rebooting etc. for whatever reason. There is no clear report that --dhcp-renew helps in these situations.

That said, dhcpmediasense detection in the proposed patch does look useful. However, instead of handling all possible scenarios where dhcp renewal may not happen automatically, why don't we just enable --dhcp-renew unconditionally? Why do we need it to be an option at all? That may also serve situations like tap adapter is set to "Always Connected" requiring a --dhcp-renew.

comment:13 Changed 21 months ago by engy

The fix be rebooting is only temporary. The DHCP addresses is leased only on first connect after reboot and it is not refreshed on reconnect. This was also my case. --dhcp-renew fixed my problem but I searched more deeply the cause of the problem.

Tested also adapter set to "Always connect" and it behaves the same as disabled dhcpmediasense. So "Always connect" is not compatible with DHCP without --dhcp-renew.

Note: See TracTickets for help on using tickets.