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

[hildeb]

My user is getting the dreaded "Waiting for TUN/TAP interface to come up..." message. What can he do?

Fri Apr 28 08:34:53 2017 OpenVPN 2.4.1 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Mar 22 2017
Fri Apr 28 08:34:53 2017 Windows version 6.1 (Windows 7) 64bit
Fri Apr 28 08:34:53 2017 library versions: OpenSSL 1.0.2k  26 Jan 2017, LZO 2.09
Enter Management Password:
Fri Apr 28 08:34:53 2017 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Fri Apr 28 08:34:53 2017 Need hold release from management interface, waiting...
Fri Apr 28 08:34:54 2017 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Fri Apr 28 08:34:54 2017 MANAGEMENT: CMD 'state on'
Fri Apr 28 08:34:54 2017 MANAGEMENT: CMD 'log all on'
Fri Apr 28 08:34:54 2017 MANAGEMENT: CMD 'echo all on'
Fri Apr 28 08:34:54 2017 MANAGEMENT: CMD 'hold off'
Fri Apr 28 08:34:54 2017 MANAGEMENT: CMD 'hold release'
Fri Apr 28 08:34:55 2017 MANAGEMENT: CMD 'username "Auth" "martmuel"'
Fri Apr 28 08:34:55 2017 MANAGEMENT: CMD 'password [...]'
Fri Apr 28 08:34:55 2017 WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.
Fri Apr 28 08:34:55 2017 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Fri Apr 28 08:34:55 2017 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Fri Apr 28 08:34:55 2017 MANAGEMENT: >STATE:1493361295,RESOLVE,,,,,,
Fri Apr 28 08:34:55 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]193.175.73.200:1194
Fri Apr 28 08:34:55 2017 Socket Buffers: R=[8192->8192] S=[8192->8192]
Fri Apr 28 08:34:55 2017 UDP link local: (not bound)
Fri Apr 28 08:34:55 2017 UDP link remote: [AF_INET]193.175.73.200:1194
Fri Apr 28 08:34:55 2017 MANAGEMENT: >STATE:1493361295,WAIT,,,,,,
Fri Apr 28 08:34:55 2017 MANAGEMENT: >STATE:1493361295,AUTH,,,,,,
Fri Apr 28 08:34:55 2017 TLS: Initial packet from [AF_INET]193.175.73.200:1194, sid=d14a10e8 fbef2ede
Fri Apr 28 08:34:55 2017 VERIFY OK: depth=1, C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=Charite-VPN CA, name=EasyRSA, emailAddress=vpn@charite.de
Fri Apr 28 08:34:55 2017 VERIFY OK: nsCertType=SERVER
Fri Apr 28 08:34:55 2017 Validating certificate extended key usage
Fri Apr 28 08:34:55 2017 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Fri Apr 28 08:34:55 2017 VERIFY EKU OK
Fri Apr 28 08:34:55 2017 VERIFY X509NAME OK: C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=openvpn.charite.de, emailAddress=vpn@charite.de
Fri Apr 28 08:34:55 2017 VERIFY OK: depth=0, C=DE, ST=Berlin, L=Berlin, O=Charite-VPN, OU=GB-IT, CN=openvpn.charite.de, emailAddress=vpn@charite.de
Fri Apr 28 08:34:55 2017 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Fri Apr 28 08:34:55 2017 [openvpn.charite.de] Peer Connection Initiated with [AF_INET]193.175.73.200:1194
Fri Apr 28 08:34:56 2017 MANAGEMENT: >STATE:1493361296,GET_CONFIG,,,,,,
Fri Apr 28 08:34:56 2017 SENT CONTROL [openvpn.charite.de]: 'PUSH_REQUEST' (status=1)
Fri Apr 28 08:34:56 2017 PUSH: Received control message: 'PUSH_REPLY,dhcp-option DNS 141.42.1.1,dhcp-option DOMAIN charite.de,register-dns,block-outside-dns,sndbuf 393216,rcvbuf 393216,route-gateway 172.29.0.1,topology subnet,ping 10,ping-restart 30,redirect-gateway def1,ifconfig 172.29.5.78 255.255.192.0,peer-id 6,cipher AES-256-GCM'
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: timers and/or timeouts modified
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified
Fri Apr 28 08:34:56 2017 Socket Buffers: R=[8192->393216] S=[8192->393216]
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: --ifconfig/up options modified
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: route options modified
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: route-related options modified
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: peer-id set
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: adjusting link_mtu to 1625
Fri Apr 28 08:34:56 2017 OPTIONS IMPORT: data channel crypto options modified
Fri Apr 28 08:34:56 2017 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Apr 28 08:34:56 2017 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Apr 28 08:34:56 2017 interactive service msg_channel=0
Fri Apr 28 08:34:56 2017 ROUTE_GATEWAY 10.31.32.1/255.255.240.0 I=12 HWADDR=24:77:03:6c:d7:28
Fri Apr 28 08:34:56 2017 open_tun
Fri Apr 28 08:34:56 2017 TAP-WIN32 device [LAN-Verbindung 2] opened: \\.\Global\{995E69E0-5281-4004-8833-3F3E4AFF6335}.tap
Fri Apr 28 08:34:56 2017 TAP-Windows Driver Version 9.21 
Fri Apr 28 08:34:56 2017 Set TAP-Windows TUN subnet mode network/local/netmask = 172.29.0.0/172.29.5.78/255.255.192.0 [SUCCEEDED]
Fri Apr 28 08:34:56 2017 Notified TAP-Windows driver to set a DHCP IP/netmask of 172.29.5.78/255.255.192.0 on interface {995E69E0-5281-4004-8833-3F3E4AFF6335} [DHCP-serv: 172.29.63.254, lease-time: 31536000]
Fri Apr 28 08:34:56 2017 Successful ARP Flush on interface [16] {995E69E0-5281-4004-8833-3F3E4AFF6335}
Fri Apr 28 08:34:56 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Apr 28 08:34:56 2017 MANAGEMENT: >STATE:1493361296,ASSIGN_IP,,172.29.5.78,,,,
Fri Apr 28 08:34:56 2017 Block_DNS: WFP engine opened
Fri Apr 28 08:34:56 2017 Block_DNS: Using existing sublayer
Fri Apr 28 08:34:56 2017 Block_DNS: Added permit filters for exe_path
Fri Apr 28 08:34:56 2017 Block_DNS: Added block filters for all interfaces
Fri Apr 28 08:34:56 2017 Block_DNS: Added permit filters for TAP interface
Fri Apr 28 08:35:01 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:01 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:07 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:07 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:08 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:08 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:09 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:09 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:10 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:10 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:11 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:11 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:12 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:12 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:13 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:13 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:14 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:14 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:15 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:15 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:16 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:16 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:17 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:17 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:18 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:18 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:19 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:19 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:20 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:20 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:21 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:21 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:22 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:22 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:23 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:23 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:24 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:24 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:25 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:25 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:26 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:26 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:27 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:27 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:28 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:28 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:29 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:29 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:30 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:30 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:31 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:31 2017 C:\Windows\system32\route.exe ADD 193.175.73.200 MASK 255.255.255.255 10.31.32.1
Fri Apr 28 08:35:31 2017 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=25 and dwForwardType=4
Fri Apr 28 08:35:31 2017 Route addition via IPAPI succeeded [adaptive]
Fri Apr 28 08:35:31 2017 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 172.29.0.1
Fri Apr 28 08:35:31 2017 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Fri Apr 28 08:35:31 2017 Route addition via IPAPI failed [adaptive]
Fri Apr 28 08:35:31 2017 Route addition fallback to route.exe
Fri Apr 28 08:35:31 2017 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Fri Apr 28 08:35:31 2017 C:\Windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 172.29.0.1
Fri Apr 28 08:35:31 2017 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Fri Apr 28 08:35:31 2017 Route addition via IPAPI failed [adaptive]
Fri Apr 28 08:35:31 2017 Route addition fallback to route.exe
Fri Apr 28 08:35:31 2017 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 10.31.32.1 p=0 i=12 t=4 pr=3 a=125 h=0 m=25/0/0/0/0
0.0.0.0 128.0.0.0 172.29.0.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
10.31.32.0 255.255.240.0 10.31.46.139 p=0 i=12 t=3 pr=3 a=125 h=0 m=281/0/0/0/0
10.31.46.139 255.255.255.255 10.31.46.139 p=0 i=12 t=3 pr=3 a=125 h=0 m=281/0/0/0/0
10.31.47.255 255.255.255.255 10.31.46.139 p=0 i=12 t=3 pr=3 a=125 h=0 m=281/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=289 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=3 a=289 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=3 a=289 h=0 m=306/0/0/0/0
128.0.0.0 128.0.0.0 172.29.0.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
169.254.0.0 255.255.0.0 169.254.202.100 p=0 i=16 t=3 pr=3 a=268 h=0 m=276/0/0/0/0
169.254.202.100 255.255.255.255 169.254.202.100 p=0 i=16 t=3 pr=3 a=268 h=0 m=276/0/0/0/0
169.254.255.255 255.255.255.255 169.254.202.100 p=0 i=16 t=3 pr=3 a=268 h=0 m=276/0/0/0/0
193.175.73.200 255.255.255.255 10.31.32.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=25/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=289 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 169.254.202.100 p=0 i=16 t=3 pr=3 a=278 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 10.31.46.139 p=0 i=12 t=3 pr=3 a=265 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=3 a=289 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 169.254.202.100 p=0 i=16 t=3 pr=3 a=278 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 10.31.46.139 p=0 i=12 t=3 pr=3 a=265 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
Microsoft Virtual WiFi Miniport Adapter
  Index = 17
  GUID = {344EA4AB-8B50-458B-8C0F-1DA94FAF8E73}
  IP = 0.0.0.0/0.0.0.0 
  MAC = 24:77:03:6c:d7:29
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV =  
  DHCP LEASE OBTAINED = Fri Apr 28 08:35:31 2017
  DHCP LEASE EXPIRES  = Fri Apr 28 08:35:31 2017
  DNS SERV =  
TAP-Windows Adapter V9
  Index = 16
  GUID = {995E69E0-5281-4004-8833-3F3E4AFF6335}
  IP = 169.254.202.100/255.255.0.0 
  MAC = 00:ff:99:5e:69:e0
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV = 0.0.0.0/255.255.255.255 
  DHCP LEASE OBTAINED = Fri Apr 28 08:35:31 2017
  DHCP LEASE EXPIRES  = Fri Apr 28 08:35:31 2017
  DNS SERV =  
Dell Wireless 5550 HSPA+ Mini-Card Network Adapter
  Index = 15
  GUID = {9DB2AE8B-33FF-46BF-90AD-659DEA580C34}
  IP = 0.0.0.0/0.0.0.0 
  MAC = 02:80:37:ec:02:00
  GATEWAY = 0.0.0.0/255.255.255.255 
  DNS SERV =  
Bluetooth-Ger\E4t (PAN)
  Index = 13
  GUID = {552C8E14-C0E5-4A81-ABF2-E9308727AF86}
  IP = 0.0.0.0/0.0.0.0 
  MAC = 7c:e9:d3:bf:b0:69
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV =  
  DHCP LEASE OBTAINED = Fri Apr 28 08:35:31 2017
  DHCP LEASE EXPIRES  = Fri Apr 28 08:35:31 2017
  DNS SERV =  
Intel(R) Centrino(R) Ultimate-N 6300 AGN
  Index = 12
  GUID = {2DE9D370-DE13-45CB-9E10-E435B50037BD}
  IP = 10.31.46.139/255.255.240.0 
  MAC = 24:77:03:6c:d7:28
  GATEWAY = 10.31.32.1/255.255.255.255 
  DHCP SERV = 10.31.32.2/255.255.255.255 
  DHCP LEASE OBTAINED = Fri Apr 28 08:33:26 2017
  DHCP LEASE EXPIRES  = Fri Apr 28 09:03:26 2017
  DNS SERV = 141.42.206.150/255.255.255.255 193.175.73.150/255.255.255.255 
Intel(R) 82579LM Gigabit Network Connection
  Index = 11
  GUID = {06008A5F-658A-4CA5-8429-4718B163BC8B}
  IP = 0.0.0.0/0.0.0.0 
  MAC = d4:be:d9:2a:69:28
  GATEWAY = 10.39.16.1/255.255.255.255 
  DHCP SERV =  
  DHCP LEASE OBTAINED = Fri Apr 28 08:35:31 2017
  DHCP LEASE EXPIRES  = Fri Apr 28 08:35:31 2017
  PRI WINS = 10.39.212.66/255.255.255.255 
  SEC WINS = 10.43.120.59/255.255.255.255 
  DNS SERV =  
Fri Apr 28 08:35:31 2017 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Fri Apr 28 08:35:31 2017 MANAGEMENT: >STATE:1493361331,CONNECTED,ERROR,172.29.5.78,193.175.73.200,1194,,
Fri Apr 28 08:35:31 2017 Start ipconfig commands for register-dns...
Fri Apr 28 08:35:31 2017 C:\Windows\system32\ipconfig.exe /flushdns
Fri Apr 28 08:35:31 2017 C:\Windows\system32\ipconfig.exe /registerdns
Fri Apr 28 08:35:37 2017 End ipconfig commands for register-dns...
Fri Apr 28 08:35:38 2017 SIGTERM received, sending exit notification to peer
Fri Apr 28 08:35:39 2017 C:\Windows\system32\route.exe DELETE 193.175.73.200 MASK 255.255.255.255 10.31.32.1
Fri Apr 28 08:35:39 2017 Route deletion via IPAPI succeeded [adaptive]
Fri Apr 28 08:35:39 2017 C:\Windows\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 172.29.0.1
Fri Apr 28 08:35:39 2017 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Fri Apr 28 08:35:39 2017 Route deletion via IPAPI failed [adaptive]
Fri Apr 28 08:35:39 2017 Route deletion fallback to route.exe
Fri Apr 28 08:35:39 2017 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Fri Apr 28 08:35:39 2017 C:\Windows\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 172.29.0.1
Fri Apr 28 08:35:39 2017 Warning: route gateway is not reachable on any active network adapters: 172.29.0.1
Fri Apr 28 08:35:39 2017 Route deletion via IPAPI failed [adaptive]
Fri Apr 28 08:35:39 2017 Route deletion fallback to route.exe
Fri Apr 28 08:35:39 2017 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Fri Apr 28 08:35:39 2017 Closing TUN/TAP interface
Fri Apr 28 08:35:39 2017 TAP: DHCP address released
Fri Apr 28 08:35:39 2017 SIGTERM[soft,exit-with-notification] received, process exiting
Fri Apr 28 08:35:39 2017 MANAGEMENT: >STATE:1493361339,EXITING,exit-with-notification,,,,,

[Selva Nair]

Looks like dhcp fails to set the address on the interface. Are there multiple tap adapters present? If yes check

(i) what addresses are set currently:

netsh int ip show addr

(ii) whether setting the address manually works:

netsh int ip set addr "LAN-Verbindung 2" static 172.29.5.78 255.255.192.0 172.29.0.1

That may give some clue.

Dont forget to reset the adapter back to dhcp

netsh int ip set addr "LAN-Verbindung 2" source=dhcp

[hildeb]

One of my users reports that he has to disable and enable the TAP32 Adapter. Then he can user VPN successfully - ONCE! So before or after every invocation of openvpn he needs to disable then reenable the adapter.

[hildeb]

In the last few days I encountered 3 users with the same problem (v 2.4.1 and v 2.3.x) -- all on Windows 7!

In all cases DEACTIVATING and REACTIVATING the Tap32 adapter helped - but only for the next connection. I had to do this for every connection attempt they made.

Can this be scripted as a pre-up script somehow?

[hildeb]

Just now I had a remote Teamviewer session: I checked

netsh int ip show addr

-- it showed 169.254.x.x addresses for the TAP32 adapter

I did not check setting the address manually, but I was able to use

netsh int ip set addr "LAN-Verbindung 2" source=dhcp

-- all it did was to say that DHCP was already enabled.

[crasheg]

Have same problem.
For one time could be resolved by changing IP and mask manually, but after connect-reconnect ip changed to auto by DHCP and going to loop

Fri Apr 28 08:35:09 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:10 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:10 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:11 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:11 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:12 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:12 2017 Route: Waiting for TUN/TAP interface to come up...
Fri Apr 28 08:35:13 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Fri Apr 28 08:35:13 2017 Route: Waiting for TUN/TAP interface to come up...

I tried to uninstall and install OpenVPN and TAP, clean registry, remove manually ethernet adapter, but problem still exist((

[skova]

I have recently been seeing this on several sites also that we have that are using this. As noted above, if you Disable and Enable the Tap Adapter, it works for the next start and then fails with any attempt after that one until you Disable and Enable again. We really need to get to the root cause of this issue.

[hildeb]

We're still encountering this problem with Windows7, with both 2.3.x and the most recent 2.4.2 so the openvpn version doesn't really matter.

[SKova]

This has been getting worse all week with sites and started to happen more often since using v2.4.x in all cases. I was able to test an idea on two sites and they worked fine since then:

• Stopped the OpenVPN service (we typically run the service) although the GUI has the same issues.
• Uninstalled OpenVPN from the server
• Set the Security Permissions to Everyone with Full Control the OpenVPN folder and all folders below it.
• Downloaded the v2.3.x (latest version) and installed it in the same path with the same config files that were there.

Now the GUI or the Service both will start and connect without any errors or problems every time (at least in my testing it has). After trying this on one site, I did another and it worked fine also.

I hope that this helps someone with what is happening. I did not try this with the v2.4.x as I was going to just install the v2.3.x and I knew that many times it needs the folder permissions that way to work properly.

[thiagoc]

I'm having this problem on a Windows Server 2012 R2, the only way to fix it was setting a static IP on the TUN/TAP interface, so I think it's a DHCP problem.