Das geht jetzt ganz fix, pass auf:

Alle Schlüssel für den Client zen auf unser Gateway in den Ordner

/etc/openvpn/zen bitte.

Dann stoppen wir unsere laufenden Openvpnserver und entfernen die Konfigurationsdateien:

root@gateway:/etc/openvpn# systemctl stop [email protected]
root@gateway:/etc/openvpn# systemctl disable [email protected]
root@gateway:/etc/openvpn# systemctl stop [email protected]
root@gateway:/etc/openvpn# systemctl disable [email protected]
root@gateway:/etc/openvpn# mv server.conf server.conf.old
root@gateway:/etc/openvpn# mv ios.conf ios.conf.old

Nun in der Datei /etc/shorewall/rules die Ports dazu schliessen und

ACCEPT fw net udp 1190

den Port für unseren neuen Client öffnen.

Soweit vorhanden alle Einträge für die alten Zonen vpn und ios entfernen, ebenso in der Datei interfaces und zones.
Natürlich können die alten Server auch weiterlaufen wenn gewünscht….dann ist aber darauf zu achten, daß die Portnummern zur Liste hinzugefügt werden und, genau, jeder Port nur einmal vergeben sein darf!
Jetzt Shorewall neustarten und die neue client.conf erstellen:

root@gateway:/etc/openvpn# nano 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 85.xx.xx.xx 1190
;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 nogroup


# 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/zen/ca.crt
cert /etc/openvpn/zen/zen.crt
key /etc/openvpn/zen/zen.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/zen/ta.key 1


# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
# 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 SHA512


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


auth-nocache


# Set log file verbosity.
verb 3


# Silence repeating messages
;mute 20

Einem ersten Test auf dem zweiten Fenster steht wieder nichts mehr im Wege, ein

systemctl daemon-reload
systemctl enable [email protected]
systemctl start [email protected]

und unser Client ist verbunden, nur darf er noch nichts.

Aber das Prinzip ist wieder klar, fi1 und fi2 bekommen ebenso ein Gateway wie zen, ho bekommt je nach Hardware und System eine angepasste Konfiguration. Ein LinuxLaptop einen Openvpnclient wie hier besprochen, ein MacBook eine Tunnelblick client.ovpn und bei Windows hab ich keine Ahnung. Also alle anderen Clients ebenso eingebunden und dann geht es an die Regeln:

next > wieder: Regeln, Regeln, Regeln