FPyro 2 Posted ... Hi! I've disconnected and everything worked fine. Then 5 mins later I tried to reconnect to a different server...SEEMED to work and icon turned blue and said connected. - lies ... maybe the logs give you a clue 08.02.2013 - 12:05 open_tun, tt->ipv6=0 08.02.2013 - 12:05 TAP-WIN32 device [Local Area Connection 3] opened: \\.\Global\{F3B7132F-08E8-485E-9E84-38265F7C06B3}.tap 08.02.2013 - 12:05 TAP-Windows Driver Version 9.9 08.02.2013 - 12:05 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.0.106/255.255.255.252 on interface {F3B7132F-08E8-485E-9E84-38265F7C06B3} [DHCP-serv: 10.4.0.105, lease-time: 31536000] 08.02.2013 - 12:05 Successful ARP Flush on interface [33] {F3B7132F-08E8-485E-9E84-38265F7C06B3} 08.02.2013 - 12:05 TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up 08.02.2013 - 12:05 C:\Windows\system32\route.exe ADD 95.211.186.65 MASK 255.255.255.255 192.168.178.1 08.02.2013 - 12:05 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=10 and dwForwardType=4 08.02.2013 - 12:05 Route addition via IPAPI succeeded [adaptive] 08.02.2013 - 12:05 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.4.0.105 08.02.2013 - 12:05 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4 08.02.2013 - 12:05 Route addition via IPAPI succeeded [adaptive] 08.02.2013 - 12:05 C:\Windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.4.0.105 08.02.2013 - 12:05 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4 08.02.2013 - 12:05 Route addition via IPAPI succeeded [adaptive] 08.02.2013 - 12:05 C:\Windows\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.0.105 08.02.2013 - 12:05 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4 08.02.2013 - 12:05 Route addition via IPAPI succeeded [adaptive] 08.02.2013 - 12:05 Initialization Sequence Completed 08.02.2013 - 12:05 Starting Management Interface... 08.02.2013 - 12:05 Checking... 08.02.2013 - 12:05 Retrieve statistics... 08.02.2013 - 12:05 Connected. 08.02.2013 - 12:30 Disconnecting... 08.02.2013 - 12:30 SIGTERM received, sending exit notification to peer 08.02.2013 - 12:30 C:\Windows\system32\route.exe DELETE 10.4.0.1 MASK 255.255.255.255 10.4.0.105 08.02.2013 - 12:30 Route deletion via IPAPI succeeded [adaptive] 08.02.2013 - 12:30 C:\Windows\system32\route.exe DELETE 95.211.186.65 MASK 255.255.255.255 192.168.178.1 08.02.2013 - 12:30 Route deletion via IPAPI succeeded [adaptive] 08.02.2013 - 12:30 C:\Windows\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 10.4.0.105 08.02.2013 - 12:30 Route deletion via IPAPI succeeded [adaptive] 08.02.2013 - 12:30 C:\Windows\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 10.4.0.105 08.02.2013 - 12:30 Route deletion via IPAPI succeeded [adaptive] 08.02.2013 - 12:30 Closing TUN/TAP interface 08.02.2013 - 12:30 SIGTERM[hard,] received, process exiting 08.02.2013 - 12:30 Disconnected. 08.02.2013 - 13:15 Login... 08.02.2013 - 13:15 Login success. 08.02.2013 - 13:15 Contacting service... 08.02.2013 - 13:15 Connecting... 08.02.2013 - 13:15 OpenVPN 2.3.0 x86_64-w64-mingw32 [sSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [iPv6] built on Jan 8 2013 08.02.2013 - 13:15 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables 08.02.2013 - 13:15 Socket Buffers: R=[8192->8192] S=[8192->8192] 08.02.2013 - 13:15 UDPv4 link local: [undef] 08.02.2013 - 13:15 UDPv4 link remote: [AF_INET]46.165.208.69:443 08.02.2013 - 13:15 TLS: Initial packet from [AF_INET]46.165.208.69:443, sid=3bac03f8 d6fdd86e 08.02.2013 - 13:15 VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org 08.02.2013 - 13:15 VERIFY OK: nsCertType=SERVER 08.02.2013 - 13:15 VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org 08.02.2013 - 13:15 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key 08.02.2013 - 13:15 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication 08.02.2013 - 13:15 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key 08.02.2013 - 13:15 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication 08.02.2013 - 13:15 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA 08.02.2013 - 13:15 [server] Peer Connection Initiated with [AF_INET]46.165.208.69:443 08.02.2013 - 13:15 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) 08.02.2013 - 13:15 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.4.0.1,comp-lzo no,route 10.4.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.4.0.54 10.4.0.53' 08.02.2013 - 13:15 OPTIONS IMPORT: timers and/or timeouts modified 08.02.2013 - 13:15 OPTIONS IMPORT: LZO parms modified 08.02.2013 - 13:15 OPTIONS IMPORT: --ifconfig/up options modified 08.02.2013 - 13:15 OPTIONS IMPORT: route options modified 08.02.2013 - 13:15 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified 08.02.2013 - 13:15 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 08.02.2013 - 13:15 open_tun, tt->ipv6=0 08.02.2013 - 13:15 TAP-WIN32 device [Local Area Connection 3] opened: \\.\Global\{F3B7132F-08E8-485E-9E84-38265F7C06B3}.tap 08.02.2013 - 13:15 TAP-Windows Driver Version 9.9 08.02.2013 - 13:15 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.0.54/255.255.255.252 on interface {F3B7132F-08E8-485E-9E84-38265F7C06B3} [DHCP-serv: 10.4.0.53, lease-time: 31536000] 08.02.2013 - 13:15 Successful ARP Flush on interface [33] {F3B7132F-08E8-485E-9E84-38265F7C06B3} 08.02.2013 - 13:15 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:15 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:15 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:15 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:15 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:15 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 Route: Waiting for TUN/TAP interface to come up... 08.02.2013 - 13:16 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down 08.02.2013 - 13:16 C:\Windows\system32\route.exe ADD 46.165.208.69 MASK 255.255.255.255 192.168.178.1 08.02.2013 - 13:16 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=10 and dwForwardType=4 08.02.2013 - 13:16 Route addition via IPAPI succeeded [adaptive] 08.02.2013 - 13:16 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.4.0.53 08.02.2013 - 13:16 Warning: route gateway is not reachable on any active network adapters: 10.4.0.53 08.02.2013 - 13:16 Route addition via IPAPI failed [adaptive] 08.02.2013 - 13:16 Route addition fallback to route.exe 08.02.2013 - 13:16 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem 08.02.2013 - 13:16 OK! 08.02.2013 - 13:16 C:\Windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.4.0.53 08.02.2013 - 13:16 Warning: route gateway is not reachable on any active network adapters: 10.4.0.53 08.02.2013 - 13:16 Route addition via IPAPI failed [adaptive] 08.02.2013 - 13:16 Route addition fallback to route.exe 08.02.2013 - 13:16 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem 08.02.2013 - 13:16 OK! 08.02.2013 - 13:16 C:\Windows\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.0.53 08.02.2013 - 13:16 Warning: route gateway is not reachable on any active network adapters: 10.4.0.53 08.02.2013 - 13:16 Route addition via IPAPI failed [adaptive] 08.02.2013 - 13:16 Route addition fallback to route.exe 08.02.2013 - 13:16 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem 08.02.2013 - 13:16 OK! 08.02.2013 - 13:16 SYSTEM ROUTING TABLE 08.02.2013 - 13:16 78.1 p=0 i=10 t=4 pr=3 a=4266 h=0 m=10/0/0/0/0 08.02.2013 - 13:16 53 p=0 i=10 t=4 pr=3 a=0 h=0 m=11/0/0/0/0 08.02.2013 - 13:16 10.4.0.53 p=0 i=10 t=4 pr=3 a=0 h=0 m=11/0/0/0/0 08.02.2013 - 13:16 2 10.4.0.106 p=0 i=33 t=3 pr=3 a=4259 h=0 m=286/0/0/0/0 08.02.2013 - 13:16 5 10.4.0.106 p=0 i=33 t=3 pr=3 a=4259 h=0 m=286/0/0/0/0 08.02.2013 - 13:16 5 10.4.0.106 p=0 i=33 t=3 pr=3 a=4259 h=0 m=286/0/0/0/0 08.02.2013 - 13:16 .255 192.168.178.1 p=0 i=10 t=4 pr=3 a=0 h=0 m=10/0/0/0/0 08.02.2013 - 13:16 .0.1 p=0 i=1 t=3 pr=3 a=60558 h=0 m=306/0/0/0/0 08.02.2013 - 13:16 127.0.0.1 p=0 i=1 t=3 pr=3 a=60558 h=0 m=306/0/0/0/0 08.02.2013 - 13:16 55.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=60558 h=0 m=306/0/0/0/0 08.02.2013 - 13:16 0.53 p=0 i=10 t=4 pr=3 a=0 h=0 m=11/0/0/0/0 08.02.2013 - 13:16 .0 192.168.178.22 p=0 i=10 t=3 pr=3 a=4266 h=0 m=266/0/0/0/0 08.02.2013 - 13:16 5.255 192.168.178.22 p=0 i=10 t=3 pr=3 a=4266 h=0 m=266/0/0/0/0 08.02.2013 - 13:16 55.255 192.168.178.22 p=0 i=10 t=3 pr=3 a=4266 h=0 m=266/0/0/0/0 08.02.2013 - 13:16 .0.1 p=0 i=1 t=3 pr=3 a=60558 h=0 m=306/0/0/0/0 08.02.2013 - 13:16 0.106 p=0 i=33 t=3 pr=3 a=4276 h=0 m=286/0/0/0/0 08.02.2013 - 13:16 68.178.22 p=0 i=10 t=3 pr=3 a=4276 h=0 m=266/0/0/0/0 08.02.2013 - 13:16 55.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=60558 h=0 m=306/0/0/0/0 08.02.2013 - 13:16 55.255 10.4.0.106 p=0 i=33 t=3 pr=3 a=4276 h=0 m=286/0/0/0/0 08.02.2013 - 13:16 55.255 192.168.178.22 p=0 i=10 t=3 pr=3 a=4276 h=0 m=266/0/0/0/0 08.02.2013 - 13:16 SYSTEM ADAPTER LIST 08.02.2013 - 13:16 TAP-Windows Adapter V9 #2 08.02.2013 - 13:16 Index = 33 08.02.2013 - 13:16 85E-9E84-38265F7C06B3} 08.02.2013 - 13:16 .255.252 08.02.2013 - 13:16 MAC = 00:ff:f3:b7:13:2f 08.02.2013 - 13:16 55.255.255 08.02.2013 - 13:16 255.255.255.255 08.02.2013 - 13:16 ri Feb 08 12:05:24 2013 08.02.2013 - 13:16 at Feb 08 12:05:24 2014 08.02.2013 - 13:16 .255.255.255 08.02.2013 - 13:16 -E Gigabit Ethernet Controller #2 08.02.2013 - 13:16 Index = 11 08.02.2013 - 13:16 43C-8034-F44E60E0F662} 08.02.2013 - 13:16 IP = 0.0.0.0/0.0.0.0 08.02.2013 - 13:16 MAC = bc:ae:c5:16:48:1c 08.02.2013 - 13:16 55.255.255 08.02.2013 - 13:16 DHCP SERV = 08.02.2013 - 13:16 ri Feb 08 13:16:23 2013 08.02.2013 - 13:16 ri Feb 08 13:16:23 2013 08.02.2013 - 13:16 DNS SERV = 08.02.2013 - 13:16 -E Gigabit Ethernet Controller 08.02.2013 - 13:16 Index = 10 08.02.2013 - 13:16 85F-A573-FBC715657EDD} 08.02.2013 - 13:16 .255.255.0 08.02.2013 - 13:16 MAC = 00:10:0b:d2:0b:a8 08.02.2013 - 13:16 /255.255.255.255 08.02.2013 - 13:16 .1/255.255.255.255 08.02.2013 - 13:16 ri Feb 08 12:05:17 2013 08.02.2013 - 13:16 on Feb 18 12:05:17 2013 08.02.2013 - 13:16 55.255.255.255 156.154.70.22/255.255.255.255 08.02.2013 - 13:16 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv ) 08.02.2013 - 13:16 Starting Management Interface... 08.02.2013 - 13:16 Checking... 08.02.2013 - 13:16 Retrieve statistics... 08.02.2013 - 13:16 Connected. I've done nothing to any adapter or changed NOTHING in the 5 mins. I just dced, checked my ping without air, made coffee, reconnected to Air ...then still had same IP Maybe some kind of warning system in such cases would be nice. Apparently the tun/tap adapter has some kind of bug! Maybe it's openVPN? thank you! kind regards fpyro Quote Share this post Link to post
FPyro 2 Posted ... Reistalling the openVPN software enabled a successful reconnect. Very strange. I don't understand this behavior at all, but then again, computers are very complex. Quote Share this post Link to post
Staff 9781 Posted ... I've done nothing to any adapter or changed NOTHING in the 5 mins. I just dced, checked my ping without air, made coffee, reconnected to Air ...then still had same IP Maybe some kind of warning system in such cases would be nice. Apparently the tun/tap adapter has some kind of bug! Maybe it's openVPN? thank you! kind regardsfpyroHello!The tun interface did not come up. It might be a bug or a crash in the TAP-Win32 Adapter driver (unlikely) or a TCP/IP stack Windows handling problem. We have noticed that all Windows versions (tested on XP, Vista and 7) have issues when they are "stressed" with repeated changes of default gateway and routing table. Sometimes these problems require an "ipconfig /renew" to be solved, but (rarely) it's not sufficient, they require also a Windows socket (WinSock catalog) reset followed by a reboot (unfortunately a Winsock catalog reset seems to require a reboot to be completed...) or a reset of the physical network card.Kind regards Quote Share this post Link to post
FPyro 2 Posted ... Hi! Well, that is actually very helpful so far since you are obviously aquainted with the problem or bug. It's not like it's happening all the time anyway, but occasionally, especially when changing servers a few times, it comes up. Which would support your claims about windows being "stressed" by the changes. Now, would reinstalling openVPN count as resetting the Windows socket or the physical network card? And would dis- and renabling of my network card be worth a try in that case too? I wouldn't want to restart or reinstall everytime it happens. Thanks a lot so far! Quote Share this post Link to post
Staff 9781 Posted ... Hi! Well, that is actually very helpful so far since you are obviously aquainted with the problem or bug. It's not like it's happening all the time anyway, but occasionally, especially when changing servers a few times, it comes up. Which would support your claims about windows being "stressed" by the changes. Now, would reinstalling openVPN count as resetting the Windows socket or the physical network card? And would dis- and renabling of my network card be worth a try in that case too? I wouldn't want to restart or reinstall everytime it happens. Thanks a lot so far!Hello!You don't have to reinstall, although re-installing and rebooting will for sure reset the TAP-Win32 Adapter, of course.When you have the problem, try the following steps (each successive step to be performed only if the previous did not solve the problem)- "ipconfig /renew" (from a command prompt with administrator privileges)- turn off and then turn on your physical interface- disable and re-enable the TAP-Win32 Adapter (this will cause it a reset), reset the TCP/IP stack and reboot, seehttp://support.microsoft.com/kb/299357As far as we have seen, the last step always works, saving you the need, time and annoyance to uninstall and reinstall OpenVPN. It's an extremely rare condition, so it's not in the FAQ, sorry. It's also not easy to reproduce the issue, however a condition to enhance occurrence probabilities of such a behavior is repeatedly changing the default gateway.Kind regards Quote Share this post Link to post
FPyro 2 Posted ... Hi! It's awesome that you've found a way to fix it so quickly, thanks a lot. It's also a shame that I seem to be stricken with such a rare "condition" sounds quite serious. I've done some further "investigation" into my condition... and found these instructions: Maybe you could tell us what you think about them? 1.Restart the DHCP client service a.Go to Start > Run, type services.msc , and Click OK. The service manager appears. b.In the list of services, find and double-click DHCP Client. c.Set the Startup type to Automatic. d.If the Service status is Started, click Stop. e.Click Start. f.Click OK, and close the service manager. g.Restart ExpressVPN and try connecting again. 2.If that didn't resolve the problem, reset winsock: a.Go to Start > All Programs > Accessories, and do one of the following: ?On Windows Vista or Windows 7, right-click Command Prompt and select Run as administrator. ?On Windows XP, click Command Prompt. b.Run the following commands: netsh int ip reset logfile.txt netsh winsock reset catalog c.Restart the computer. d.Start ExpressVPN and try connecting again. Then the Waiting for TUN/TAP interface to come up stopped to loop. I'm so happy to get such good support in the Air forum :kiss: kind regards pyro Quote Share this post Link to post
Staff 9781 Posted ... Hello! Actually it's interesting, those instructions suggest to restart the DHCP client service before trying a complete stack reset. In our tests, when the problem occurred, if an ipconfig /renew and a normal reboot did not work we jumped to reset the winsock catalog and perform a reboot, we did not try to restart the DHCP client service. If it works and it does not require the aforementioned reset, then the real cause of the problem would be detected, it would probably be a bug in the DHCP Windows service which is there since so many years. That would also explain why the problem has more chances to occur when default gateways are repeatedly DHCP-pushed. Kind regards Quote Share this post Link to post
Not connected, Your IP: 3.15.2.78
Online: 23779 users - 291284 Mbit/s total BW