[Resolved] RTNETLINK answers: File exists

Need help configuring your VPN? Just post here and you'll get that help.
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Locked
GonzaloS
OpenVpn Newbie
Posts: 1
Joined: Wed Mar 28, 2018 11:59 pm

[Resolved] RTNETLINK answers: File exists

Post by GonzaloS » Thu Mar 29, 2018 12:15 am

Hi,

I set up OpenVPN in Debian 9 and I am getting the following error in the clients' log. (I look at the different solutions that I found on the Internet but none solved the problem):
RTNETLINK answers: File exists
Wed Mar 28 19:51:55 2018 ERROR: Linux route add command failed: external program exited with error status: 2
The /openvpn/server.conf:

Code: Select all

#################################################
# Sample OpenVPN 2.0 config file for            #
# multi-client server.                          #
#                                               #
# This file is for the server side              #
# of a many-clients <-> one-server              #
# OpenVPN configuration.                        #
#                                               #
# OpenVPN also supports                         #
# single-machine <-> single-machine             #
# configurations (See the Examples page         #
# on the web site for more info).               #
#                                               #
# This config should work on Windows            #
# or Linux/BSD systems.  Remember on            #
# Windows to quote pathnames and use            #
# double backslashes, e.g.:                     #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
#                                               #
# Comments are preceded with '#' or ';'         #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# 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 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.crt
key server.key  # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names.  This is recommended
# only for testing purposes.  For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
#   openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
tls-auth ta.key 0 # This file is secret
key-direction 0

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
# Note that 2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC
auth SHA256

# Enable compression on the VPN link and push the
# option to the client (2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"

# For compression compatible with older clients use comp-lzo
# If you enable it here, you must also
# enable it in the client config file.
;comp-lzo

# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100

# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nogroup

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it.  Use one
# or the other (but not both).
;log         openvpn.log
;log-append  openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

# Notify the client that when the server restarts so it
# can automatically reconnect.
explicit-exit-notify 1
And the client logs are:

Code: Select all

Wed Mar 28 19:18:54 2018 OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017
Wed Mar 28 19:18:54 2018 library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.08
Wed Mar 28 19:18:54 2018 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Mar 28 19:18:54 2018 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Mar 28 19:18:54 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]serverIP:1194
Wed Mar 28 19:18:54 2018 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Mar 28 19:18:54 2018 UDP link local: (not bound)
Wed Mar 28 19:18:54 2018 UDP link remote: [AF_INET]serverIP:1194
Wed Mar 28 19:18:54 2018 NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Wed Mar 28 19:18:55 2018 TLS: Initial packet from [AF_INET]serverIP:1194, sid=fbac1e22 104c70ad
Wed Mar 28 19:18:55 2018 VERIFY OK: depth=1, C=US, ST=CA, L=SanFrancisco, O=Fort-Funston, OU=MyConnection, CN=Fort-Funston CA, name=server, emailAddress=email@testing.com
Wed Mar 28 19:18:55 2018 Validating certificate key usage
Wed Mar 28 19:18:55 2018 ++ Certificate has key usage  00a0, expects 00a0
Wed Mar 28 19:18:55 2018 VERIFY KU OK
Wed Mar 28 19:18:55 2018 Validating certificate extended key usage
Wed Mar 28 19:18:55 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Wed Mar 28 19:18:55 2018 VERIFY EKU OK
Wed Mar 28 19:18:55 2018 VERIFY OK: depth=0, C=US, ST=CA, L=SanFrancisco, O=Fort-Funston, OU=MyConnection, CN=server, name=server, emailAddress=email@testing.com
Wed Mar 28 19:18:55 2018 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Wed Mar 28 19:18:55 2018 [server] Peer Connection Initiated with [AF_INET]serverIP:1194
Wed Mar 28 19:18:56 2018 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 28 19:18:56 2018 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM'
Wed Mar 28 19:18:56 2018 OPTIONS IMPORT: timers and/or timeouts modified
Wed Mar 28 19:18:56 2018 OPTIONS IMPORT: --ifconfig/up options modified
Wed Mar 28 19:18:56 2018 OPTIONS IMPORT: route options modified
Wed Mar 28 19:18:56 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Mar 28 19:18:56 2018 OPTIONS IMPORT: peer-id set
Wed Mar 28 19:18:56 2018 OPTIONS IMPORT: adjusting link_mtu to 1624
Wed Mar 28 19:18:56 2018 OPTIONS IMPORT: data channel crypto options modified
Wed Mar 28 19:18:56 2018 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed Mar 28 19:18:56 2018 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed Mar 28 19:18:56 2018 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=wlan0 HWADDR=f4:06:69:54:86:84
Wed Mar 28 19:18:56 2018 TUN/TAP device tun0 opened
Wed Mar 28 19:18:56 2018 TUN/TAP TX queue length set to 100
Wed Mar 28 19:18:56 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Wed Mar 28 19:18:56 2018 /sbin/ip link set dev tun0 up mtu 1500
Wed Mar 28 19:18:56 2018 /sbin/ip addr add dev tun0 local 10.8.0.6 peer 10.8.0.5
Wed Mar 28 19:18:56 2018 /sbin/ip route add serverIP/32 via 192.168.1.1
RTNETLINK answers: File exists
Wed Mar 28 19:18:56 2018 ERROR: Linux route add command failed: external program exited with error status: 2
Wed Mar 28 19:18:56 2018 /sbin/ip route add 0.0.0.0/1 via 10.8.0.5
Wed Mar 28 19:18:56 2018 /sbin/ip route add 128.0.0.0/1 via 10.8.0.5
Wed Mar 28 19:18:56 2018 /sbin/ip route add 10.8.0.1/32 via 10.8.0.5
Wed Mar 28 19:18:57 2018 GID set to nogroup
Wed Mar 28 19:18:57 2018 UID set to nobody
Wed Mar 28 19:18:57 2018 Initialization Sequence Completed
^CWed Mar 28 19:19:00 2018 event_wait : Interrupted system call (code=4)
Wed Mar 28 19:19:00 2018 /sbin/ip route del 10.8.0.1/32
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:19:00 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Wed Mar 28 19:19:00 2018 /sbin/ip route del serverIP/32
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:19:00 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Wed Mar 28 19:19:00 2018 /sbin/ip route del 0.0.0.0/1
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:19:00 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Wed Mar 28 19:19:00 2018 /sbin/ip route del 128.0.0.0/1
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:19:00 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Wed Mar 28 19:19:00 2018 Closing TUN/TAP interface
Wed Mar 28 19:19:00 2018 /sbin/ip addr del dev tun0 local 10.8.0.6 peer 10.8.0.5
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:19:00 2018 Linux ip addr del failed: external program exited with error status: 2
Wed Mar 28 19:19:00 2018 SIGINT[hard,] received, process exiting
root@Gon-Debian:~# openvpn client1.ovpn 
Wed Mar 28 19:51:52 2018 OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017
Wed Mar 28 19:51:52 2018 library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.08
Wed Mar 28 19:51:52 2018 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Mar 28 19:51:52 2018 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Mar 28 19:51:52 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]serverIP:1194
Wed Mar 28 19:51:52 2018 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Mar 28 19:51:52 2018 UDP link local: (not bound)
Wed Mar 28 19:51:52 2018 UDP link remote: [AF_INET]serverIP:1194
Wed Mar 28 19:51:52 2018 NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Wed Mar 28 19:51:53 2018 TLS: Initial packet from [AF_INET]serverIP:1194, sid=293c0e3b ab2e0a01
Wed Mar 28 19:51:53 2018 VERIFY OK: depth=1, C=US, ST=CA, L=SanFrancisco, O=Fort-Funston, OU=MyConnection, CN=Fort-Funston CA, name=server, emailAddress=email@testing.com
Wed Mar 28 19:51:53 2018 Validating certificate key usage
Wed Mar 28 19:51:53 2018 ++ Certificate has key usage  00a0, expects 00a0
Wed Mar 28 19:51:53 2018 VERIFY KU OK
Wed Mar 28 19:51:53 2018 Validating certificate extended key usage
Wed Mar 28 19:51:53 2018 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Wed Mar 28 19:51:53 2018 VERIFY EKU OK
Wed Mar 28 19:51:53 2018 VERIFY OK: depth=0, C=US, ST=CA, L=SanFrancisco, O=Fort-Funston, OU=MyConnection, CN=server, name=server, emailAddress=email@testing.com
Wed Mar 28 19:51:53 2018 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Wed Mar 28 19:51:53 2018 [server] Peer Connection Initiated with [AF_INET]serverIP:1194
Wed Mar 28 19:51:54 2018 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Mar 28 19:51:55 2018 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM'
Wed Mar 28 19:51:55 2018 OPTIONS IMPORT: timers and/or timeouts modified
Wed Mar 28 19:51:55 2018 OPTIONS IMPORT: --ifconfig/up options modified
Wed Mar 28 19:51:55 2018 OPTIONS IMPORT: route options modified
Wed Mar 28 19:51:55 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Mar 28 19:51:55 2018 OPTIONS IMPORT: peer-id set
Wed Mar 28 19:51:55 2018 OPTIONS IMPORT: adjusting link_mtu to 1624
Wed Mar 28 19:51:55 2018 OPTIONS IMPORT: data channel crypto options modified
Wed Mar 28 19:51:55 2018 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed Mar 28 19:51:55 2018 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed Mar 28 19:51:55 2018 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=wlan0 HWADDR=f4:06:69:54:86:84
Wed Mar 28 19:51:55 2018 TUN/TAP device tun0 opened
Wed Mar 28 19:51:55 2018 TUN/TAP TX queue length set to 100
Wed Mar 28 19:51:55 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Wed Mar 28 19:51:55 2018 /sbin/ip link set dev tun0 up mtu 1500
Wed Mar 28 19:51:55 2018 /sbin/ip addr add dev tun0 local 10.8.0.6 peer 10.8.0.5
Wed Mar 28 19:51:55 2018 /sbin/ip route add serverIP/32 via 192.168.1.1
RTNETLINK answers: File exists
Wed Mar 28 19:51:55 2018 ERROR: Linux route add command failed: external program exited with error status: 2
Wed Mar 28 19:51:55 2018 /sbin/ip route add 0.0.0.0/1 via 10.8.0.5
Wed Mar 28 19:51:55 2018 /sbin/ip route add 128.0.0.0/1 via 10.8.0.5
Wed Mar 28 19:51:55 2018 /sbin/ip route add 10.8.0.1/32 via 10.8.0.5
Wed Mar 28 19:51:55 2018 GID set to nogroup
Wed Mar 28 19:51:55 2018 UID set to nobody
Wed Mar 28 19:51:55 2018 Initialization Sequence Completed
^CWed Mar 28 19:52:20 2018 event_wait : Interrupted system call (code=4)
Wed Mar 28 19:52:20 2018 /sbin/ip route del 10.8.0.1/32
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:52:20 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Wed Mar 28 19:52:20 2018 /sbin/ip route del serverIP/32
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:52:20 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Wed Mar 28 19:52:20 2018 /sbin/ip route del 0.0.0.0/1
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:52:20 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Wed Mar 28 19:52:20 2018 /sbin/ip route del 128.0.0.0/1
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:52:20 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Wed Mar 28 19:52:20 2018 Closing TUN/TAP interface
Wed Mar 28 19:52:20 2018 /sbin/ip addr del dev tun0 local 10.8.0.6 peer 10.8.0.5
RTNETLINK answers: Operation not permitted
Wed Mar 28 19:52:20 2018 Linux ip addr del failed: external program exited with error status: 2
Wed Mar 28 19:52:20 2018 SIGINT[hard,] received, process exiting
Any idea where the problem may be?

Thank you very much

moqjdn
OpenVpn Newbie
Posts: 1
Joined: Wed Apr 18, 2018 3:47 pm

Re: RTNETLINK answers: File exists

Post by moqjdn » Wed Apr 18, 2018 4:09 pm

I get the same error

Code: Select all

Wed Apr 18 17:20:53 2018 /sbin/ip route add <VPN IP>/32 via 192.168.1.1
RTNETLINK answers: File exists
Wed Apr 18 17:20:53 2018 ERROR: Linux route add command failed: external program exited with error status: 2
Any help would be appreciated.

User avatar
TinCanTech
OpenVPN Protagonist
Posts: 4865
Joined: Fri Jun 03, 2016 1:17 pm

Re: RTNETLINK answers: File exists

Post by TinCanTech » Wed Apr 18, 2018 4:21 pm

In almost a month this thread recieved only 70 views .. because everybody knows that it means the route you are trying to add already exists.

For further help Please see:
HOWTO: Request Help !

*closed*

Locked