Arch Linux

barchiesi

Member

Registered: 2011-11-04

Posts: 15

Openvpn not connecting to VPN at boot

I am having problems connecting to a VPN at boot. journalctl reports the following errors every 5s forever

Feb 18 11:25:15 david-laptop openvpn@client[418]: RESOLVE: Cannot resolve host address: barchie.si: Name or service not known
Feb 18 11:25:20 david-laptop openvpn@client[418]: RESOLVE: Cannot resolve host address: barchie.si: Name or service not known
Feb 18 11:25:25 david-laptop openvpn@client[418]: RESOLVE: Cannot resolve host address: barchie.si: Name or service not known
Feb 18 11:25:30 david-laptop openvpn@client[418]: RESOLVE: Cannot resolve host address: barchie.si: Name or service not known
Feb 18 11:25:35 david-laptop openvpn@client[418]: RESOLVE: Cannot resolve host address: barchie.si: Name or service not known
Feb 18 11:25:40 david-laptop openvpn@client[418]: RESOLVE: Cannot resolve host address: barchie.si: Name or service not known

If I restart the openvpn@client.service then it connects fine. The error message is written even when I am effectively connected to the internet.

Here is the systemd unit file:

[Unit]
Description=OpenVPN connection to %i
Requires=network.target
After=network.target

[Service]
Type=forking
ExecStart=/usr/bin/openvpn --cd /etc/openvpn --config /etc/openvpn/%i.conf --daemon openvpn@%i --writepid /run/openvpn@%i.pid
PIDFile=/run/openvpn@%i.pid

[Install]
WantedBy=multi-user.target

And here is my /etc/openvpn/client.conf:

##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server.     #
#                                            #
# This configuration can be used by multiple #
# clients, however each client should have   #
# its own cert and key files.                #
#                                            #
# On Windows, you might want to rename this  #
# file so it has a .ovpn extension           #
##############################################

# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client

# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one.  On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap

# Are we connecting to a TCP or
# UDP server?  Use the same setting as
# on the server.
;proto tcp
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote barchie.si 1194
;remote my-server-2 1194

# Choose a random host from the remote
# list for load-balancing.  Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server.  Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

# Downgrade privileges after initialization (non-Windows only)
user nobody
group nobody

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here.  See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets.  Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description.  It's best to use
# a separate .crt/.key file pair
# for each client.  A single ca
# file can be used for all clients.
ca /etc/openvpn/keys/ca.crt
cert /etc/openvpn/keys/david-laptop.crt
key /etc/openvpn/keys/david-laptop.key

# Verify server certificate by checking that the
# certicate has the correct key usage set.
# This is an important precaution to protect against
# a potential attack discussed here:
#  http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the keyUsage set to
#   digitalSignature, keyEncipherment
# and the extendedKeyUsage to
#   serverAuth
# EasyRSA can do this for you.
remote-cert-tls server

# If a tls-auth key is used on the server
# then every client must also have the key.
tls-auth /etc/openvpn/keys/ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20

Thanks in advance for all the help

GI Jack

Member

Registered: 2010-12-29

Posts: 92

Re: Openvpn not connecting to VPN at boot

try replacing "network" in the systemd unit file with whatever you use to connect to the network. if you are using netctl, type netctl status <profilename> to get your systemd unit.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: Openvpn not connecting to VPN at boot

Not a Sysadmin issue, moving to NC...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438