Checking route - AirVPN works on public net but not home

[dragonbuggle 0]

I'm having problems connecting to any servers with AirVPN--the recent stable version or the beta--on my home internet connection.

 

Some background: I've tested on two Windows 10 64-bit machines and get as far as connecting, then checking the route, before timing out, then repeating.

 

I ran out of ideas until I successfully managed to connect with no issues on a public WiFi connection.

 

So I'm narrowing down to an issue with my router and/or home ISP. I wondered if some bright person on here could help me figure out which.

 

My log is as posted below:

 

I 2016.09.02 18:06:36 - Eddie client version: 2.11.3 / x64, System: Windows, Name: Microsoft Windows NT 10.0.14393.0 / x64
. 2016.09.02 18:06:36 - Reading options from C:\Users\X\AppData\Local\AirVPN\AirVPN.xml
. 2016.09.02 18:06:36 - Profile options not found, using defaults.
. 2016.09.02 18:06:37 - Data Path: C:\Users\X\AppData\Local\AirVPN
. 2016.09.02 18:06:37 - App Path: C:\Program Files\AirVPN
. 2016.09.02 18:06:37 - Executable Path: C:\Program Files\AirVPN\AirVPN.exe
. 2016.09.02 18:06:37 - Command line arguments (1): path="home"
. 2016.09.02 18:06:37 - Operating System: Microsoft Windows NT 10.0.14393.0
. 2016.09.02 18:06:37 - Cannot find tunnel adapter.
E 2016.09.02 18:06:38 - OpenVPN Driver - Not available - Will be installed at next connection.
I 2016.09.02 18:06:38 - OpenVPN - Version: OpenVPN 2.3.11 (C:\Program Files\AirVPN\openvpn.exe)
I 2016.09.02 18:06:38 - SSH - Version: plink 0.63 (C:\Program Files\AirVPN\plink.exe)
I 2016.09.02 18:06:38 - SSL - Version: stunnel 5.32 (C:\Program Files\AirVPN\stunnel.exe)
! 2016.09.02 18:06:41 - Ready
. 2016.09.02 18:06:41 - Updating systems & servers data ...
. 2016.09.02 18:06:43 - Systems & servers data update completed
I 2016.09.02 18:07:01 - Checking login ...
! 2016.09.02 18:07:01 - Logged in.
I 2016.09.02 18:07:05 - Session starting.
. 2016.09.02 18:07:06 - Cannot find tunnel adapter.
! 2016.09.02 18:07:06 - Installing tunnel driver
I 2016.09.02 18:07:18 - IPv6 disabled with packet filtering.
I 2016.09.02 18:07:18 - Checking authorization ...
! 2016.09.02 18:07:19 - Connecting to Tarazed (Netherlands, Alblasserdam)
. 2016.09.02 18:07:19 - OpenVPN > OpenVPN 2.3.11 x86_64-w64-mingw32 [sSL (OpenSSL)] [LZO] [iPv6] built on Jun  1 2016
. 2016.09.02 18:07:19 - OpenVPN > Windows version 6.2 (Windows 8 or greater) 64bit
. 2016.09.02 18:07:19 - OpenVPN > library versions: OpenSSL 1.0.2h  3 May 2016, LZO 2.09
. 2016.09.02 18:07:19 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2016.09.02 18:07:19 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file
. 2016.09.02 18:07:19 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.09.02 18:07:19 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.09.02 18:07:19 - OpenVPN > Socket Buffers: R=[65536->262144] S=[65536->262144]
. 2016.09.02 18:07:19 - OpenVPN > UDPv4 link local: [undef]
. 2016.09.02 18:07:19 - OpenVPN > UDPv4 link remote: [AF_INET]213.152.161.132:443
. 2016.09.02 18:07:19 - OpenVPN > TLS: Initial packet from [AF_INET]213.152.161.132:443, sid=1ebb6384 9bc946b7
. 2016.09.02 18:07:19 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2016.09.02 18:07:19 - OpenVPN > Validating certificate key usage
. 2016.09.02 18:07:19 - OpenVPN > ++ Certificate has key usage  00a0, expects 00a0
. 2016.09.02 18:07:19 - OpenVPN > VERIFY KU OK
. 2016.09.02 18:07:19 - OpenVPN > Validating certificate extended key usage
. 2016.09.02 18:07:19 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2016.09.02 18:07:19 - OpenVPN > VERIFY EKU OK
. 2016.09.02 18:07:19 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
. 2016.09.02 18:07:20 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2016.09.02 18:07:20 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.09.02 18:07:20 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
. 2016.09.02 18:07:20 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
. 2016.09.02 18:07:20 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2016.09.02 18:07:20 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]213.152.161.132:443
. 2016.09.02 18:07:22 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
. 2016.09.02 18:07:22 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 10.4.0.1,comp-lzo no,route-gateway 10.4.0.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.4.78.180 255.255.0.0'
. 2016.09.02 18:07:22 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2016.09.02 18:07:22 - OpenVPN > OPTIONS IMPORT: LZO parms modified
. 2016.09.02 18:07:22 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2016.09.02 18:07:22 - OpenVPN > OPTIONS IMPORT: route options modified
. 2016.09.02 18:07:22 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2016.09.02 18:07:22 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2016.09.02 18:07:22 - OpenVPN > ROUTE_GATEWAY 192.168.0.1/255.255.255.0 I=16 HWADDR=00:1f:1f:ed:6f:fd
. 2016.09.02 18:07:22 - OpenVPN > do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
. 2016.09.02 18:07:22 - OpenVPN > open_tun, tt->ipv6=0
. 2016.09.02 18:07:22 - OpenVPN > TAP-WIN32 device [Ethernet] opened: \\.\Global\{8BAF6344-A1E9-49CA-826E-4FB22A4F6D35}.tap
. 2016.09.02 18:07:22 - OpenVPN > TAP-Windows Driver Version 9.21
. 2016.09.02 18:07:22 - OpenVPN > Set TAP-Windows TUN subnet mode network/local/netmask = 10.4.0.0/10.4.78.180/255.255.0.0 [sUCCEEDED]
. 2016.09.02 18:07:22 - OpenVPN > Notified TAP-Windows driver to set a DHCP IP/netmask of 10.4.78.180/255.255.0.0 on interface {8BAF6344-A1E9-49CA-826E-4FB22A4F6D35} [DHCP-serv: 10.4.255.254, lease-time: 31536000]
. 2016.09.02 18:07:22 - OpenVPN > Successful ARP Flush on interface [42] {8BAF6344-A1E9-49CA-826E-4FB22A4F6D35}
. 2016.09.02 18:07:27 - OpenVPN > TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up
. 2016.09.02 18:07:27 - OpenVPN > C:\WINDOWS\system32\route.exe ADD 213.152.161.132 MASK 255.255.255.255 192.168.0.1
. 2016.09.02 18:07:27 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=50 and dwForwardType=4
. 2016.09.02 18:07:27 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.09.02 18:07:27 - OpenVPN > C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.09.02 18:07:27 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
. 2016.09.02 18:07:27 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.09.02 18:07:27 - OpenVPN > C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.09.02 18:07:27 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
. 2016.09.02 18:07:27 - OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2016.09.02 18:07:27 - Starting Management Interface
. 2016.09.02 18:07:27 - OpenVPN > Initialization Sequence Completed
I 2016.09.02 18:07:28 - DNS leak protection with packet filtering enabled.
I 2016.09.02 18:07:28 - DNS of a network adapter forced (TAP-Windows Adapter V9, from automatic (10.4.0.1) to 10.4.0.1)
I 2016.09.02 18:07:28 - Flushing DNS
I 2016.09.02 18:07:29 - Checking route
W 2016.09.02 18:08:19 - The operation has timed out
! 2016.09.02 18:08:19 - Disconnecting
. 2016.09.02 18:08:19 - Management - Send 'signal SIGTERM'
. 2016.09.02 18:08:19 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM'
. 2016.09.02 18:08:19 - OpenVPN > SIGTERM received, sending exit notification to peer
. 2016.09.02 18:08:19 - OpenVpn Management > >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info
. 2016.09.02 18:08:19 - OpenVpn Management > SUCCESS: signal SIGTERM thrown
. 2016.09.02 18:08:24 - OpenVPN > C:\WINDOWS\system32\route.exe DELETE 213.152.161.132 MASK 255.255.255.255 192.168.0.1
. 2016.09.02 18:08:24 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.09.02 18:08:24 - OpenVPN > C:\WINDOWS\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.09.02 18:08:24 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.09.02 18:08:24 - OpenVPN > C:\WINDOWS\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 10.4.0.1
. 2016.09.02 18:08:24 - OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2016.09.02 18:08:24 - OpenVPN > Closing TUN/TAP interface
. 2016.09.02 18:08:24 - OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting
. 2016.09.02 18:08:24 - Connection terminated.
I 2016.09.02 18:08:24 - DNS of a network adapter restored to original settings (TAP-Windows Adapter V9, to automatic)
I 2016.09.02 18:08:25 - DNS leak protection with packet filtering disabled.
I 2016.09.02 18:08:25 - Cancel requested.
I 2016.09.02 18:08:25 - IPv6 restored with packet filtering.
! 2016.09.02 18:08:25 - Session terminated.
 

 

Thanks!

[LZ1 672]

Hello!

 

In the advanced settings, you can try to disable either one or both of DNS checking and Air tunnel check .

 

Perhaps try other protocols too?

 

Sent to you from me with datalove

[dragonbuggle 0]

OK, so I disabled the DNS check and the route check and it now connects. Thanks!

 

Are there downsides to having these switches disabled?

 

My main use for a VPN is for use in public settings so having some extra setup at home is not as big an issue, but I like to know what problems I might create!

[OpenSourcerer 1435]

I like to know what problems I might create!

 

These checks are there to verify whether your connection works as intended.

If DNS checks fail, anyone between you and the AirVPN server may see your DNS queries and therefore the sites you connect to.

If route checks fail, your traffic might not go through the tunnel at all.

 

It's a good practice to check ipleak.net for example for possible problems every now and then, when these checks are disabled.