Jump to content
Not connected, Your IP: 35.173.57.84
assddg

OpenVPN connected but no traffic, Ubuntu 14.04

Recommended Posts

Hey.

 

I'm running OpenVPN 2.3.2 on Ubuntu server 14.04 in a VirtualBox 5.0.14 instance on a Win-64 box to connect to AirVPN using the config file generated from the AirVPN site.

 

The VirtualBox instance is bridged to my host NIC using a PCnet-FAST III driver in Ubuntu.

 

Set to auto-start with the AirVPN config file as the default in /etc/openvpn so I control it with service stop / start.

 

The tunnel will work for somewhere between 1 and 6 hours and then it will remain established but no traffic will move through it. 

 

I've tried adding 

 

keepalive 10 60

 

 to the config but no change.

 

I've anecdotally seen that it could be related to interruption in the internet connection.

 

How can I either a. get the openvpn service to withstand internet connectivity interruptions or b. cron a script to test and if fail restart the openvpn service.

 

FYI I'm reasonably strong technically but my Linux skill is newbie.

Share this post


Link to post

This is the ifconfig after the tunnel's been established for 6 hours.  Notice the TX dropped.

 

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet addr:air.vpn.ip.add  P-t-P:air.vpn.ip.add  Mask:255.255.0.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:3883803 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5679001 errors:0 dropped:2410603 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:3234669343 (3.2 GB)  TX bytes:3964299033 (3.9 GB)

 

Share this post


Link to post

Apart from asking why you are still running a nearly six year old distribution, when that happens it would be nice to know whether the routes are still there. Something like route would help, unless of course you can enter ip r (the new network tool for IP configuration).

Then, OpenVPN logs. Don't just point at the mist, give us the zombie. :)
Then, VirtualBox version. I hope it's not as old as the distro.

b) should be rather easy. Ping something every minute or so, and if it gets the timeout error code, pkill -15 openvpn && (sudo) openvpn /path/to/the/config.ovpn. This is workaround stuff, I'd rather look at why it's doing that exactly, so let's first gather some intel through logs. :)


Four simple things:
There's a guide to AirVPN. Before you ask questions, take 30 minutes of your time to go through it.

Amazon IPs are not dangerous here. It's the fallback DNS.
Running TOR exits is discouraged. They're subject to restrictions on the internet and harm all AirVPN users.

Furthermore, I propose that your paranoia is to be destroyed. If you overdo privacy, you'll be unique among the mass again.

 

XMPP: gigan3rd@xmpp.airvpn.org or join our lounge@conference.xmpp.airvpn.org

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

×
×
  • Create New...