Gotcha.
IDK man this is not working at all.
I set my IP address to my routers IP and physical IP and still no luck.
Is there an openVPN GUI client for OpenSUSE Leap 42.1 KDE?
Can you be more specific?
Is it still refusing to start? What error message do you get?
Is there an openVPN GUI client for OpenSUSE Leap 42.1 KDE?
NetworkManager does support openVPN.
Just switch to it in YaST and set up your client connection in the desktop’s network applet. (click on the “connection editor” icon in the upper right corner to add a connection)
**linux-069u:~ #** systemctl status openvpn@client
openvpn@client.service - OpenVPN tunneling daemon instance using /etc/openvpn/client.conf
Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled)
Active: inactive (dead)
>:(
Not sure which one to click in Yast. Is it under network services? Can you go into detail please. I don’t have a desktop network applet.
Ok in Yast > system > Services Manager openVPN@myconfig was inactive along with openVPN@ and openVPN@server.
When I activated I clicked show details in the bottom right hand corner and it gave me this:
openvpn@myconfig.service - OpenVPN tunneling daemon instance using /etc/openvpn/myconfig.conf Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled) Active: failed (Result: exit-code) since Thu 2016-02-18 08:58:01 EST; 1min 52s ago Process: 9458 ExecStart=/usr/sbin/openvpn --daemon --suppress-timestamps --writepid /var/run/openvpn/%i.pid --cd /etc/openvpn/ --config %i.conf (code=exited, status=1/FAILURE)
Feb 18 08:58:01 linux-069u openvpn[9458]: Options error: In [CMD-LINE]:1: Error opening configuration file: myconfig.confFeb 18 08:58:01 linux-069u openvpn[9458]: Use --help for more information.Feb 18 08:58:01 linux-069u systemd[1]: Failed to start OpenVPN tunneling daemon instance using /etc/openvpn/myconfig.conf.
I doubt that has to do anything with my problem.
Did you restart it after your config changes?
systemctl restart openvpn@client
Not sure which one to click in Yast. Is it under network services? Can you go into detail please. I don’t have a desktop network applet.
Go into YaST->System->Network Settings->Global Options and switch from “Wicked Service” to “NetworkManager Service”. Then a desktop network applet should appear automatically.
Why does it say “myconfig.conf” now?
Your config file is named “client.conf”.
Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled) Active: failed (Result: exit-code) since Thu 2016-02-18 08:58:01 EST; 1min 52s ago Process: 9458 ExecStart=/usr/sbin/openvpn --daemon --suppress-timestamps --writepid /var/run/openvpn/%i.pid --cd /etc/openvpn/ --config %i.conf (code=exited, status=1/FAILURE)
Feb 18 08:58:01 linux-069u openvpn[9458]: Options error: In [CMD-LINE]:1: Error opening configuration file: myconfig.confFeb 18 08:58:01 linux-069u openvpn[9458]: Use --help for more information.Feb 18 08:58:01 linux-069u systemd[1]: Failed to start OpenVPN tunneling daemon instance using /etc/openvpn/myconfig.conf.
[QUOTE]I doubt that has to do anything with my problem.
This instance tries to open the config file myconfig.conf which doesn’t exist. Why is it even enabled?
Disable it again.
Please post the output of:
systemctl | grep openvpn
**linux-069u:~ #** systemctl | grep openvpn
**openvpn**@client.service loaded fai
led failed OpenVPN tunneling daemon instance using /etc/**openvpn**/client.conf
**openvpn**@myconfig.service loaded fai
led failed OpenVPN tunneling daemon instance using /etc/**openvpn**/myconfig.conf
**openvpn**@server.service loaded act
ive running OpenVPN tunneling daemon instance using /etc/**openvpn**/server.conf
system-**openvpn**.slice loaded act
ive active system-**openvpn**.slice
Go into YaST->System->Network Settings->Global Options and switch from "Wicked Service" to "NetworkManager Service". Then a desktop network applet should appear automatically.
Heres my config in conection editor VPN tab:
Gateway: my IP address
CA File: ca.crt
Certificate: client1.crt
Key: client1.key
Should I edit anything else in the other tabs because I tried to connect and the connection failed.
If you want to run me through this step-by-step I’m here.
**linux-069u:~ #** systemctl status system-openvpn.slice
system-openvpn.slice
Loaded: loaded
Active: **active** since Thu 2016-02-18 22:18:05 EST; 1h 51min ago
CGroup: /system.slice/system-openvpn.slice
└─openvpn@server.service
└─1161 /usr/sbin/openvpn --daemon --suppress-timestamps --writepid /var/run/openvpn/server.pid --cd /...
Feb 18 22:18:28 linux-069u openvpn[1161]: **do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0**
Feb 18 22:18:28 linux-069u openvpn[1161]: **/bin/ip link set dev tun0 up mtu 1500**
Feb 18 22:18:28 linux-069u openvpn[1161]: **/bin/ip addr add dev tun0 local 10.8.0.1 peer 10.8.0.2**
Feb 18 22:18:28 linux-069u openvpn[1161]: **/bin/ip route add 10.8.0.0/24 via 10.8.0.2**
Feb 18 22:18:28 linux-069u openvpn[1161]: **UDPv4 link local (bound): [undef]**
Feb 18 22:18:28 linux-069u openvpn[1161]: **UDPv4 link remote: [undef]**
Feb 18 22:18:28 linux-069u openvpn[1161]: **MULTI: multi_init called, r=256 v=256**
Feb 18 22:18:28 linux-069u openvpn[1161]: **IFCONFIG POOL: base=10.8.0.4 size=62, ipv6=0**
Feb 18 22:18:28 linux-069u openvpn[1161]: **IFCONFIG POOL LIST**
Feb 18 22:18:28 linux-069u openvpn[1161]: **Initialization Sequence Completed**
Is this helpful?
So you still have the myconfig.conf in there.
Stop and disable it, it won’t work without an actuall config file named myconfig.conf.
systemctl stop **openvpn**@myconfig.service
systemctl disable **openvpn**@myconfig.service
It shouldn’t have any influence, but who knows. And at least it caused confusion already in this thread… 
Then try to restart the correct one and post the status:
systemctl restart openvpn@client
systemctl status openvpn@client
And maybe also post the current client.conf
You do seem to have a server running successfully though.
Is this on purpose?
I cannot really as I never used openvpn myself.
And the connection editor even crashes when I try to create an openvpn connection here on my 13.2 system with KDE4…
I don’t think so.
Well I stopped and disabled the myconfig.service, but It’s still there:
**linux-069u:~ #** systemctl | grep openvpn
**openvpn**@client.service loaded failed failed OpenVPN tunneling daemon instance using /etc/**ope**
nvpn/client.conf
**openvpn**@myconfig.service loaded failed failed OpenVPN tunneling daemon instance using /etc/**ope**
nvpn/myconfig.conf
**openvpn**@server.service loaded active running OpenVPN tunneling daemon instance using /etc/**ope**
nvpn/server.conf
system-**openvpn**.slice loaded active active system-**openvpn**.slice
**linux-069u:~ #** systemctl status openvpn@client
openvpn@client.service - OpenVPN tunneling daemon instance using /etc/openvpn/client.conf
Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled)
Active: **failed** (Result: exit-code) since Fri 2016-02-19 06:56:26 EST; 4s ago
Process: 3120 ExecStart=/usr/sbin/openvpn --daemon --suppress-timestamps --writepid /var/run/openvpn/%i.pid --cd /e
tc/openvpn/ --config %i.conf (code=exited, status=0/SUCCESS)
Main PID: 3121 (code=exited, status=1/FAILURE)
**linux-069u:~ #** systemctl status openvpn@client
openvpn@client.service - OpenVPN tunneling daemon instance using /etc/openvpn/client.conf
Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled)
Active: **failed** (Result: exit-code) since Fri 2016-02-19 06:56:26 EST; 17min ago
Main PID: 3121 (code=exited, status=1/FAILURE)
Feb 19 06:56:26 linux-069u openvpn[3120]: **OpenVPN 2.3.8 x86_64-suse-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Aug 4 2015**
Ok.
“systemctl reset-failed” should get rid of it then.
**linux-069u:~ #** systemctl status openvpn@client openvpn@client.service - OpenVPN tunneling daemon instance using /etc/openvpn/client.conf Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled) Active: **failed** (Result: exit-code) since Fri 2016-02-19 06:56:26 EST; 4s ago Process: 3120 ExecStart=/usr/sbin/openvpn --daemon --suppress-timestamps --writepid /var/run/openvpn/%i.pid --cd /e tc/openvpn/ --config %i.conf (code=exited, status=0/SUCCESS) Main PID: 3121 (code=exited, status=1/FAILURE) Feb 19 06:56:26 linux-069u openvpn[3120]: **OpenVPN 2.3.8 x86_64-suse-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Aug 4 2015**
Are you sure it is not working?
The process seems to have been started successfully (it says “(code=exited, status=0/SUCCESS)”).
Maybe the failed state is just bogus? In that case, “systemctl reset-failed” should fix that too I suppose.
Still doesn’t work btw look at this after I ran systemctl reset-failed :
**linux-069u:~ #** systemctl | grep openvpn
**openvpn**@server.service loaded active running
OpenVPN tunneling daemon instance using /etc/**ope**nvpn/server.conf
system-**openvpn**.slice
Now where did my client.conf go?
The server is running and active, but my client.conf won’t execute. Culd the server be looking at another .conf to execute besides the client.conf?
If so how can I change that?
My server config:
#################################################
# 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 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"
# 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
# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC # Blowfish (default)
;cipher AES-128-CBC # AES
;cipher DES-EDE3-CBC # Triple-DES
# Enable compression on the VPN link.
# 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 nobody
# 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
It’s state was “failed”, so reset-failed probably removed it from systemd’s list.
Restart it and it should show up again:
systemctl restart openvpn@client
The server is running and active, but my client.conf won’t execute. Culd the server be looking at another .conf to execute besides the client.conf?
The openvpn@server only uses server.conf, not anything else. And it should not cause problems with the (independent) client.
I just find it strange that you have a client and a server on the same machine. What exactly are you trying to achieve?
If this is for testing purposes and you try to connect the client to your own server, try to disable the firewall as a test. It will block port 1194 by default, which would of course cause the client to not be able to connect. This might also be a problem when trying to connect to the same machine, as you specify the explicit IP address, 192.168.1.2. (localhost or 127.0.0.1 would circumvent the firewall)
systemctl stop SuSEfirewall2
**linux-069u:~ #** systemctl status openvpn@client -l
openvpn@client.service - OpenVPN tunneling daemon instance using /etc/openvpn/client.conf
Loaded: loaded (/usr/lib/systemd/system/openvpn@.service; enabled)
Active: **failed** (Result: exit-code) since Fri 2016-02-19 09:32:15 EST; 1min 22s ago
Process: 6991 ExecStart=/usr/sbin/openvpn --daemon --suppress-timestamps --writepid /var/run/openvpn/%i.pid --cd /etc/openvpn/ --config %i.conf (code=exited, status=0/SUCCESS)
Main PID: 6992 (code=exited, status=1/FAILURE)
Feb 19 09:32:15 linux-069u openvpn[6991]: **OpenVPN 2.3.8 x86_64-suse-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH] [IPv6] built on Aug 4 2015**
Feb 19 09:32:15 linux-069u openvpn[6991]: **library versions: OpenSSL 1.0.1i-fips 6 Aug 2014, LZO 2.08**
Feb 19 09:32:15 linux-069u openvpn[6992]: **Cannot load certificate file /etc/openvpn/client1.crt: error:0906D06C:PEM routines:PEM_read_bio:no start line: error:140AD009:SSL routine**
s:SSL_CTX_use_certificate_file:PEM lib
Feb 19 09:32:15 linux-069u openvpn[6992]: **Exiting due to fatal error**
For now I just want to connect to the internet through a VPN. I don’t really want a VPN server. If I need a VPN server on my system to connect through to VPN then fine.
Why did you configure/start a server then?
And you specified 192.168.1.2 (port 1194) as address to connect to for the client.
Is this really the VPN server through which you want to connect to the Internet?
I somehow suspect that this is your own system.
/sbin/ifconfig should tell.
It seems you have a basic misconception here about VPN.
Maybe you should explain more details about how exactly you are connected to the Internet and what VPN service you want to use, i.e. what exactly you are trying to achieve.
As indicated, it might be easier with NetworkManager then.
In this regard:
That’s wrong. You’d need the VPN server’s address there.
Unless you want to connect to your own VPN server running on your system. But this is apparently not what you want.
I figured I can connect to the internet through a VPN on my system without a server IP.
From what you tell me the you need to connect to a server IP so that your connected to a VPN.
No yeah I want to connect to a VPN server and that server is on my computer.
That’s the only way how I’ll be to connect to a VPN from what your telling me.
If that I won’t have a VPN server on my system since I just want a client VPN connection.
Get what I’m saying?
So the server is on my system and I’m connection my system as a client on the server.
My IP is the servers address is the server is on my system.