Jump to content
Not connected, Your IP: 3.138.101.151
Sign in to follow this  
spitzer

ANSWERED Linux/Ubuntu Terminal help needed

Recommended Posts

I am trying to connect to AirVPN through the Terminal both in Linux Mint 16 and Ubuntu 14.04.  I followed the instructions here https://airvpn.org/topic/11431-using-airvpn-with-linux-from-terminal/?hl=linux.

 

It seems to connect ("Initialization Sequence Completed") however I cannot access any websites at this point.

 

$ sudo openvpn AirVPN_CA-Thabit_UDP-443.ovpn
Wed Apr 30 20:38:03 2014 OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Feb  4 2014
Wed Apr 30 20:38:03 2014 Control Channel Authentication: tls-auth using INLINE static key file
Wed Apr 30 20:38:03 2014 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 30 20:38:03 2014 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 30 20:38:03 2014 Socket Buffers: R=[212992->131072] S=[212992->131072]
Wed Apr 30 20:38:03 2014 UDPv4 link local: [undef]
Wed Apr 30 20:38:03 2014 UDPv4 link remote: [AF_INET]198.144.158.11:443
Wed Apr 30 20:38:03 2014 TLS: Initial packet from [AF_INET]198.144.158.11:443, sid=771fd979 1a95a41e
Wed Apr 30 20:38:03 2014 VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
Wed Apr 30 20:38:03 2014 Validating certificate key usage
Wed Apr 30 20:38:03 2014 ++ Certificate has key usage  00a0, expects 00a0
Wed Apr 30 20:38:03 2014 VERIFY KU OK
Wed Apr 30 20:38:03 2014 Validating certificate extended key usage
Wed Apr 30 20:38:03 2014 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Wed Apr 30 20:38:03 2014 VERIFY EKU OK
Wed Apr 30 20:38:03 2014 VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
Wed Apr 30 20:38:04 2014 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Wed Apr 30 20:38:04 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 30 20:38:04 2014 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Wed Apr 30 20:38:04 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 30 20:38:04 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 4096 bit RSA
Wed Apr 30 20:38:04 2014 [server] Peer Connection Initiated with [AF_INET]198.144.158.11:443
Wed Apr 30 20:38:06 2014 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Apr 30 20:38:06 2014 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.1.90 10.4.1.89'
Wed Apr 30 20:38:06 2014 OPTIONS IMPORT: timers and/or timeouts modified
Wed Apr 30 20:38:06 2014 OPTIONS IMPORT: LZO parms modified
Wed Apr 30 20:38:06 2014 OPTIONS IMPORT: --ifconfig/up options modified
Wed Apr 30 20:38:06 2014 OPTIONS IMPORT: route options modified
Wed Apr 30 20:38:06 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Apr 30 20:38:06 2014 ROUTE_GATEWAY 192.168.0.1/255.255.255.0 IFACE=eth0 HWADDR=00:23:5a:d2:70:91
Wed Apr 30 20:38:06 2014 TUN/TAP device tun0 opened
Wed Apr 30 20:38:06 2014 TUN/TAP TX queue length set to 100
Wed Apr 30 20:38:06 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Apr 30 20:38:06 2014 /sbin/ip link set dev tun0 up mtu 1500
Wed Apr 30 20:38:06 2014 /sbin/ip addr add dev tun0 local 10.4.1.90 peer 10.4.1.89
Wed Apr 30 20:38:06 2014 /sbin/ip route add xxx.xxx.xxx.xxx/32 via 192.168.0.1
Wed Apr 30 20:38:06 2014 /sbin/ip route add 0.0.0.0/1 via 10.4.1.89
Wed Apr 30 20:38:06 2014 /sbin/ip route add 128.0.0.0/1 via 10.4.1.89
Wed Apr 30 20:38:06 2014 /sbin/ip route add 10.4.0.1/32 via 10.4.1.89
Wed Apr 30 20:38:06 2014 Initialization Sequence Completed

Share this post


Link to post

Hello!

 

After the initialization sequence is completed, do not stop OpenVPN. Open a terminal, issue the following commands, copy everything and paste:

 

ping -c 2 google.com

ping -c 2 10.4.0.1

ping -c 2 8.8.8.8

traceroute google.com

 

Since the logs are perfect (note that we wiped out an IP address to preserve your privacy), the above is basically a test to determine whether the problem arises from DNS.

 

If it does, you might like to follow this guide (you'll need resolvconf installed): https://airvpn.org/topic/9608-how-to-accept-dns-push-on-linux-systems-with-resolvconf

 

Kind regards

Share this post


Link to post

Ok, seems to have been a DNS issue.  I had to add the update-resolv-conf script to the OpenVPN configuration file and everything works fine now.

 

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  

×
×
  • Create New...