Jump to content
Not connected, Your IP: 18.188.110.150
AirVPN
Sign in to follow this  
Followers 0
dcodelanyto

ANSWERED Internet connectivity problem via air vpn client

By dcodelanyto, ... in Troubleshooting and Problems

Recommended Posts

dcodelanyto    0

dcodelanyto
Posted ...

air vpn logs

 

5/23/2013 - 11:42 PM    AirVPN client version: 1.7    
5/23/2013 - 11:42 PM    Reading options from C:\Documents and Settings\VirtualUser\Application Data\AirVPN\Air\1.0.0.0\AirVPN.xml    
5/23/2013 - 11:42 PM    OpenVPN bundle version: OpenVPN 2.2.2    
5/23/2013 - 11:42 PM    OpenVPN current version: OpenVPN 2.2.2    
5/23/2013 - 11:42 PM    Ready.    
5/23/2013 - 11:42 PM    Login...    
5/23/2013 - 11:42 PM    Login success.    
5/23/2013 - 11:43 PM    Contacting service...    
5/23/2013 - 11:43 PM    Connecting...    
5/23/2013 - 11:43 PM    OpenVPN 2.2.2 Win32-MSVC++ [sSL] [LZO2] [PKCS11] built on Dec 15 2011    
5/23/2013 - 11:43 PM    NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables    
5/23/2013 - 11:43 PM    LZO compression initialized    
5/23/2013 - 11:43 PM    Control Channel MTU parms [ L:1558 D:138 EF:38 EB:0 ET:0 EL:0 ]    
5/23/2013 - 11:43 PM    Socket Buffers: R=[8192->8192] S=[8192->8192]    
5/23/2013 - 11:43 PM    Data Channel MTU parms [ L:1558 D:1450 EF:58 EB:135 ET:0 EL:0 AF:3/1 ]    
5/23/2013 - 11:43 PM    Local Options hash (VER=V4): '22188c5b'    
5/23/2013 - 11:43 PM    Expected Remote Options hash (VER=V4): 'a8f55717'    
5/23/2013 - 11:43 PM    UDPv4 link local: [undef]    
5/23/2013 - 11:43 PM    UDPv4 link remote: 95.211.169.3:443    
5/23/2013 - 11:43 PM    TLS: Initial packet from 95.211.169.3:443, sid=92af3452 debdddb9    
5/23/2013 - 11:43 PM    VERIFY OK: depth=1, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=airvpn.org_CA/emailAddress=info@airvpn.org    
5/23/2013 - 11:43 PM    VERIFY OK: nsCertType=SERVER    
5/23/2013 - 11:43 PM    VERIFY OK: depth=0, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=server/emailAddress=info@airvpn.org    
5/23/2013 - 11:43 PM    Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key    
5/23/2013 - 11:43 PM    Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication    
5/23/2013 - 11:43 PM    Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key    
5/23/2013 - 11:43 PM    Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication    
5/23/2013 - 11:43 PM    Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA    
5/23/2013 - 11:43 PM    [server] Peer Connection Initiated with 95.211.169.3:443    
5/23/2013 - 11:43 PM    SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)    
5/23/2013 - 11:43 PM    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.42 10.4.0.41'    
5/23/2013 - 11:43 PM    OPTIONS IMPORT: timers and/or timeouts modified    
5/23/2013 - 11:43 PM    OPTIONS IMPORT: LZO parms modified    
5/23/2013 - 11:43 PM    OPTIONS IMPORT: --ifconfig/up options modified    
5/23/2013 - 11:43 PM    OPTIONS IMPORT: route options modified    
5/23/2013 - 11:43 PM    OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified    
5/23/2013 - 11:43 PM    ROUTE default_gateway=192.168.1.1    
5/23/2013 - 11:43 PM    TAP-WIN32 device [Local Area Connection 3] opened: \\.\Global\{EF18466E-C8E0-491C-BB14-4085CF2A7674}.tap    
5/23/2013 - 11:43 PM    TAP-Win32 Driver Version 9.9     
5/23/2013 - 11:43 PM    TAP-Win32 MTU=1500    
5/23/2013 - 11:43 PM    Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.4.0.42/255.255.255.252 on interface {EF18466E-C8E0-491C-BB14-4085CF2A7674} [DHCP-serv: 10.4.0.41, lease-time: 31536000]    
5/23/2013 - 11:43 PM    Successful ARP Flush on interface [3] {EF18466E-C8E0-491C-BB14-4085CF2A7674}    
5/23/2013 - 11:43 PM    TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up    
5/23/2013 - 11:43 PM    C:\WINDOWS\system32\route.exe ADD 95.211.169.3 MASK 255.255.255.255 192.168.1.1    
5/23/2013 - 11:43 PM    Route addition via IPAPI succeeded [adaptive]    
5/23/2013 - 11:43 PM    C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.4.0.41    
5/23/2013 - 11:43 PM    Route addition via IPAPI succeeded [adaptive]    
5/23/2013 - 11:43 PM    C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.4.0.41    
5/23/2013 - 11:43 PM    Route addition via IPAPI succeeded [adaptive]    
5/23/2013 - 11:43 PM    C:\WINDOWS\system32\route.exe ADD 10.4.0.1 MASK 255.255.255.255 10.4.0.41    
5/23/2013 - 11:43 PM    Route addition via IPAPI succeeded [adaptive]    
5/23/2013 - 11:43 PM    Initialization Sequence Completed    
5/23/2013 - 11:43 PM    Starting Management Interface...    
5/23/2013 - 11:43 PM    Checking...    
5/23/2013 - 11:44 PM    Retrieve statistics...    
5/23/2013 - 11:44 PM    Connected.    
5/24/2013 - 12:43 AM    TLS: soft reset sec=0 bytes=2593769/0 pkts=5674/0    
5/24/2013 - 12:43 AM    VERIFY OK: depth=1, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=airvpn.org_CA/emailAddress=info@airvpn.org    
5/24/2013 - 12:43 AM    VERIFY OK: nsCertType=SERVER    
5/24/2013 - 12:43 AM    VERIFY OK: depth=0, /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=server/emailAddress=info@airvpn.org    
5/24/2013 - 12:43 AM    Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key    
5/24/2013 - 12:43 AM    Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication    
5/24/2013 - 12:43 AM    Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key    
5/24/2013 - 12:43 AM    Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication    
5/24/2013 - 12:43 AM    Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA    
 

Share this post

Link to post

Staff    9973

Staff
Posted ...

Hello!

 

The logs are just fine and the connection goes through swiftly, no apparent problems are showed.

 

Please check the updated step 13 rules and add the rules, if you wish to have the new primary frontend available (your connections will work anyway, the old frontend server remains available).

 

 

13) If you use the Air client, add rules to allow communications with IP 95.211.138.143 and 212.117.180.25 (our frontend servers), In and Out
Allow TCP or UDP In/Out From IP 95.211.138.143 To MAC Any Where Source Port Is Any And Destination Port Is Any
Allow TCP or UDP In/Out From MAC Any To IP 95.211.138.143 Where Source Port Is Any And Destination Port Is Any
Allow TCP or UDP In/Out From IP 212.117.180.25 To MAC Any Where Source Port Is Any And Destination Port Is Any
Allow TCP or UDP In/Out From MAC Any To IP 212.117.180.25 Where Source Port Is Any And Destination Port Is Any

 

Kind regards

Share this post

Link to post

dcodelanyto    0

dcodelanyto
Posted ...

Thanks for your quick reply and perhaps i am now past the point of air vpn client set up, but i believe that the ping test below shows that general internet traffic is not functioning. suggestions?

 



Pinging 127.0.0.1 with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Ping statistics for 127.0.0.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms


Pinging airvpn.org [85.17.207.151] with 32 bytes of data:

Reply from 85.17.207.151: bytes=32 time=2604ms TTL=59
Reply from 85.17.207.151: bytes=32 time=170ms TTL=59
Reply from 85.17.207.151: bytes=32 time=167ms TTL=59
Reply from 85.17.207.151: bytes=32 time=166ms TTL=59

Ping statistics for 85.17.207.151:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 166ms, Maximum = 2604ms, Average = 776ms


Ping request could not find host www.google.com. Please check the name and try again.

Ping request could not find host www.yahoo.com. Please check the name and try again.
 

Share this post

Link to post

Staff    9973

Staff
Posted ...

Hello!

 

It appears to be a DNS issue, what happens if you set 10.4.0.1 as primary DNS in your physical network card?

 

Kind regards

Share this post

Link to post

dcodelanyto    0

dcodelanyto
Posted ...

confirmed. Setting DNS as you suggest restores my ability to hit the webs.

 

non functioning settings were

Preferred DNS server: 87.118.104.203
Alternate DNS server: 62.141.58.13

 

thanks,

Share this post

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  
Followers 0
Go To Topic Listing
×
×
  • Create New...