TAP driver issue

p5211871p5211871
in Windows VPN Setup
I've been using PIA for about a year now, but within the past few weeks I've been having and issue wit hthe downloadable desktop version of the app to where it will connect to any given location just fine,  but when I check the ip address in the browser it does not  change I believe this is due to the tap driver being suck on "identifying" I'll screenshot an example https://gyazo.com/9a0a8e748404fdb298c8a75b89d6d59c , I've tried reistalling both the tap driver and the program nothing changed. I tried a few CMD commands suggested in other posts and it hasn't helped. here is a picture of my routing table too, please help. https://gyazo.com/911157d7574ace7abf29d1c08b5970f4

Comments

  • Max-PMax-P
    Hi,

    According to your routing table, it appears that Windows is failing to get an IP at all on the TAP adapter. So far this issue seems to be caused by the NDIS 6 version of OpenVPN's TAP driver to randomly drop packets, which in turn causes the DHCP configuration to fail.

    It's kind of a long shot, but for some people downgrading to the NDIS 5 version as explained in this guide seems to work for some people: https://helpdesk.privateinternetaccess.com/hc/en-us/articles/226694948-I-can-connect-to-the-VPN-but-my-speeds-are-really-slow-using-Windows
  • p5211871p5211871
    Max-P said:
    Hi,

    According to your routing table, it appears that Windows is failing to get an IP at all on the TAP adapter. So far this issue seems to be caused by the NDIS 6 version of OpenVPN's TAP driver to randomly drop packets, which in turn causes the DHCP configuration to fail.

    It's kind of a long shot, but for some people downgrading to the NDIS 5 version as explained in this guide seems to work for some people: https://helpdesk.privateinternetaccess.com/hc/en-us/articles/226694948-I-can-connect-to-the-VPN-but-my-speeds-are-really-slow-using-Windows

  • p5211871p5211871
    Didn't work, maybe this will help----


    Wed Jan 17 22:18:38 2018 OpenVPN 2.4.4 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Sep 26 2017
    Wed Jan 17 22:18:38 2018 Windows version 6.1 (Windows 7) 64bit
    Wed Jan 17 22:18:38 2018 library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.10
    Wed Jan 17 22:18:45 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]169.57.0.224:1198
    Wed Jan 17 22:18:45 2018 UDP link local: (not bound)
    Wed Jan 17 22:18:45 2018 UDP link remote: [AF_INET]169.57.0.224:1198
    Wed Jan 17 22:18:45 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
    Wed Jan 17 22:18:45 2018 [31d4d41286fb3ae36142f76a7babf005] Peer Connection Initiated with [AF_INET]169.57.0.224:1198
    Wed Jan 17 22:18:46 2018 open_tun
    Wed Jan 17 22:18:46 2018 TAP-WIN32 device [Local Area Connection 2] opened: \\.\Global\{EB954AD5-CB18-4D4B-95B9-162884FE1B52}.tap
    Wed Jan 17 22:18:46 2018 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.39.10.6/255.255.255.252 on interface {EB954AD5-CB18-4D4B-95B9-162884FE1B52} [DHCP-serv: 10.39.10.5, lease-time: 31536000]
    Wed Jan 17 22:18:46 2018 Successful ARP Flush on interface [20] {EB954AD5-CB18-4D4B-95B9-162884FE1B52}
    Wed Jan 17 22:18:46 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
    Wed Jan 17 22:19:21 2018 Warning: route gateway is not reachable on any active network adapters: 10.39.10.5
    Wed Jan 17 22:19:21 2018 Warning: route gateway is not reachable on any active network adapters: 10.39.10.5
    Wed Jan 17 22:19:21 2018 Warning: route gateway is not reachable on any active network adapters: 10.39.10.5
    Wed Jan 17 22:19:21 2018 SYSTEM ROUTING TABLE
    Wed Jan 17 22:19:21 2018 0.0.0.0 0.0.0.0 10.0.0.1 p=0 i=10 t=4 pr=3 a=376 h=0 m=10/0/0/0/0
    Wed Jan 17 22:19:21 2018 10.0.0.0 255.255.255.0 10.0.0.12 p=0 i=10 t=3 pr=3 a=375 h=0 m=266/0/0/0/0
    Wed Jan 17 22:19:21 2018 10.0.0.12 255.255.255.255 10.0.0.12 p=0 i=10 t=3 pr=3 a=375 h=0 m=266/0/0/0/0
    Wed Jan 17 22:19:21 2018 10.0.0.255 255.255.255.255 10.0.0.12 p=0 i=10 t=3 pr=3 a=375 h=0 m=266/0/0/0/0
    Wed Jan 17 22:19:21 2018 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=414 h=0 m=306/0/0/0/0
    Wed Jan 17 22:19:21 2018 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=414 h=0 m=306/0/0/0/0
    Wed Jan 17 22:19:21 2018 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=414 h=0 m=306/0/0/0/0
    Wed Jan 17 22:19:21 2018 169.57.0.224 255.255.255.255 10.0.0.1 p=0 i=10 t=4 pr=3 a=0 h=0 m=266/0/0/0/0
    Wed Jan 17 22:19:21 2018 169.254.0.0 255.255.0.0 169.254.171.28 p=0 i=20 t=3 pr=3 a=51 h=0 m=276/0/0/0/0
    Wed Jan 17 22:19:21 2018 169.254.171.28 255.255.255.255 169.254.171.28 p=0 i=20 t=3 pr=3 a=51 h=0 m=276/0/0/0/0
    Wed Jan 17 22:19:21 2018 169.254.255.255 255.255.255.255 169.254.171.28 p=0 i=20 t=3 pr=3 a=51 h=0 m=276/0/0/0/0
    Wed Jan 17 22:19:21 2018 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=414 h=0 m=306/0/0/0/0
    Wed Jan 17 22:19:21 2018 224.0.0.0 240.0.0.0 10.0.0.12 p=0 i=10 t=3 pr=3 a=403 h=0 m=266/0/0/0/0
    Wed Jan 17 22:19:21 2018 224.0.0.0 240.0.0.0 169.254.171.28 p=0 i=20 t=3 pr=3 a=403 h=0 m=276/0/0/0/0
    Wed Jan 17 22:19:21 2018 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=414 h=0 m=306/0/0/0/0
    Wed Jan 17 22:19:21 2018 255.255.255.255 255.255.255.255 10.0.0.12 p=0 i=10 t=3 pr=3 a=403 h=0 m=266/0/0/0/0
    Wed Jan 17 22:19:21 2018 255.255.255.255 255.255.255.255 169.254.171.28 p=0 i=20 t=3 pr=3 a=403 h=0 m=276/0/0/0/0
    Wed Jan 17 22:19:21 2018 SYSTEM ADAPTER LIST
    Wed Jan 17 22:19:21 2018 TAP-Windows Adapter V9
    Wed Jan 17 22:19:21 2018   Index = 20
    Wed Jan 17 22:19:21 2018   GUID = {EB954AD5-CB18-4D4B-95B9-162884FE1B52}
    Wed Jan 17 22:19:21 2018   IP = 169.254.171.28/255.255.0.0 
    Wed Jan 17 22:19:21 2018   MAC = 00:ff:eb:95:4a:d5
    Wed Jan 17 22:19:21 2018   GATEWAY = 0.0.0.0/255.255.255.255 
    Wed Jan 17 22:19:21 2018   DHCP SERV =  
    Wed Jan 17 22:19:21 2018   DHCP LEASE OBTAINED = Wed Jan 17 22:19:21 2018
    Wed Jan 17 22:19:21 2018   DHCP LEASE EXPIRES  = Wed Jan 17 22:19:21 2018
    Wed Jan 17 22:19:21 2018   DNS SERV =  
    Wed Jan 17 22:19:21 2018 Realtek PCIe GBE Family Controller
    Wed Jan 17 22:19:21 2018   Index = 10
    Wed Jan 17 22:19:21 2018   GUID = {F3376AEA-58AC-4ADE-AB2B-280E27455C00}
    Wed Jan 17 22:19:21 2018   IP = 10.0.0.12/255.255.255.0 
    Wed Jan 17 22:19:21 2018   MAC = 10:bf:48:87:28:c4
    Wed Jan 17 22:19:21 2018   GATEWAY = 10.0.0.1/255.255.255.255 
    Wed Jan 17 22:19:21 2018   DHCP SERV = 10.0.0.1/255.255.255.255 
    Wed Jan 17 22:19:21 2018   DHCP LEASE OBTAINED = Wed Jan 17 22:13:06 2018
    Wed Jan 17 22:19:21 2018   DHCP LEASE EXPIRES  = Wed Jan 24 22:13:06 2018
    Wed Jan 17 22:19:21 2018   DNS SERV = 75.75.75.75/255.255.255.255 75.75.76.76/255.255.255.255 
    Wed Jan 17 22:19:21 2018 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
  • Max-PMax-P
    Sorry for the delays, been sick all week.

    That log is indeed useful! This error in particular we have a helpdesk article just for it:
     Warning: route gateway is not reachable on any active network adapters: 10.39.10.5

    This usually takes care of it: https://helpdesk.privateinternetaccess.com/hc/en-us/articles/219459227-I-am-receiving-the-error-Warning-route-gateway-is-not-reachable-on-any-active-network-adapters-X-X-X-X-in-my-debug-log
Sign In or Register to comment.