OpenVPN and Android

To be honest I use OpenVPN quite rarely on my Android tablet, and it happens only when I need to access certain locations that tie me to a certain IP address. This type of connection could be more often used when the tabled would serve as an email reading device at a company  that would restrict email usage without a VPN.

So, today, I open my OpenVPN Connect app and try to connect. And I get this message:

Tun interface setup failed: tun_builder_error: one of ifconfig or ifconfig-ipv6 must be specified

2013-10-28 18.43.47

As a good guy the first thing I do is to google the message and what I get are only stupid answers like “brackets inside the config file are wrong”. I take a look in my config file, there are absolutely no brackets. WTF!?

Looking further in the config file I realise that I changed the config on the server, so that it would use a “tap” interface instead of a “tun” one. Ok, I change that in the tablet’s config file and try to connect again. Another error message:

Sorry, but the Android VPN API doesn’t currently allow TAP-based tunnels.

Sorry, but the Android VPN API doesn't currently allow TAP-based tunnels.

WTF again!

I ended up creating a new config on the server, to make the connection on a different port, using tun-based configuration, and reversed tablet’s configuration to using tun-based interface.

Working OpenVPN connection on Android tablet

And everything works! Magic!

4 thoughts on “OpenVPN and Android

  1. tdreyer1 October 31, 2013 at 12:44 pm

    I’m running into this same issue except my server config isn’t using a tap device. Would you be willing to post your server and client config files?

    • Emil November 1, 2013 at 1:43 pm

      So, the server is something like:
      port YOUR_PORT
      proto udp
      dev tun0
      ca ca.crt
      cert server.crt
      key server.key
      dh dh1024.pem
      ifconfig-pool-persist ipp.txt
      push “redirect-gateway def1 bypass-dhcp”
      push “dhcp-option DNS”
      keepalive 5 120
      status openvpn-status.log
      verb 3

      And the client:
      dev tun
      proto udp
      resolv-retry infinite
      ca ca.crt
      cert client.crt
      key client.key
      ns-cert-type server
      verb 3

      • tdreyer1 November 5, 2013 at 1:08 am

        Thanks, that did it! Changed a few of my settings to match yours and this connection oddity disappeared.

  2. caviru January 19, 2016 at 2:56 pm

    Thank you, i think solved mine too.

Leave a Reply

Please type the characters of this captcha image in the input box

Please type the characters of this captcha image in the input box
Name *
Email *