Hallo zusammen,

ich habe folgendes Problem:

Ich möchte auf meinem Desktop PC bzw. Laptop eine OpenVPN Verbindung zu einem OpenVPN Server, welcher im Internet steht, herstellen. Der OpenVPN Server läuft auf Port 1194. Leider funktioniert das ganze nicht, soweit ich das sehe scheitert es an UPD in Kombination mit Port 1194.

Der Log vom OpenVPN Client (in diesem Fall Viscosity, erziele aber mit dem OpenVPN das gleiche Ergebniss & selbige Fehlermeldung) sieht wie folgt aus:

Jan 31 12:02:13: Status auf Verbinde geändert
Jan 31 12:02:13: Viscosity Windows 1.7.14 (1595)
Jan 31 12:02:14: Betriebsystem ist Microsoft Windows 10 Pro
Jan 31 12:02:14: Betriebsystem ist .NET Framework Version 4.7.03056.461808
Jan 31 12:02:14: Aktivieren des Netzwerkadapters...
Jan 31 12:02:14: OpenVPN 2.4.6 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [AEAD] built on Jan 21 2019
Jan 31 12:02:14: library versions: OpenSSL 1.0.2q  20 Nov 2018, LZO 2.09
Jan 31 12:02:19: Checking remote host "xxxxxx.xx" is reachable...
Jan 31 12:02:19: Server reachable. Connecting to xxx.xx.xxx.xx.
Jan 31 12:02:20: WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Jan 31 12:02:21: TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xx.xxx.xx:1194
Jan 31 12:02:21: UDP link local: (not bound)
Jan 31 12:02:21: UDP link remote: [AF_INET]xxx.xx.xxx.xx:1194
Jan 31 12:03:20: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Jan 31 12:03:20: TLS Error: TLS handshake failed
Jan 31 12:03:20: SIGUSR1[soft,tls-error] received, process restarting
Jan 31 12:03:20: Status auf Verbinde geändert
Jan 31 12:03:31: Checking remote host "xxxxxx.xx" is reachable...
Jan 31 12:03:31: Server reachable. Connecting to xxx.xx.xxx.xx.

Das OpenVPN Server & Client prinzipiell richtig geconft sind, habe ich in sofern überprüft, als ich bei einem Kollegen zuhause am DSL Anschluss (mit ner Fritzbox statt nem Speedport Hybrid) mich erfolgreich verbinden kann.

Die Config vom OpenVPN Client sieht wie folgt aus:

##############################################
# 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
;; Erst wird IPv6 probiert, und IPv4 als Fallback genutzt.
;;proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote xxxxxxxxx.xx 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 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 startssl-ca.crt

# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server".  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 nsCertType
# field set to "server".  The build-key-server
# script in the easy-rsa folder will do this.
;ns-cert-type server

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

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
cipher AES-256-CBC

# 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

auth-user-pass

Zu meinem sonstigen Setup:

- Speedport Hybrid (WLAN aktiviert)

- UniFi Switch8 60W

Ich habe es sowohl unter Windows mit Viscosity und dem offizielen OpenVPN Client probiert, als auch unter Debian mit dem offizielen OpenVPN Client.

Ich habs über WLAN und über LAN probiert. Ich habe auch testweise im Speedport Hybird mal auf "nur DSL" umgeschalten, hatte aber keine Auswirkungen.

Infos zu meinem Speedport Hybrid:

Datum / Uhrzeit
31.01.2019 12:16:05
DSL Downstream
109341  kbit/s
DSL Upstream
38372  kbit/s
Firmware-Version
050124.04.00.005
Boot-Code-Version
BROADCOMV1.00
 LTE -Firmware-Version
H1331.11.994.13.113d
DSL-Modem-Code-Version
B2pv6F039w1.d24m
 DECT -Basisstation-Version
3.56.7
Hardware-Version
VER.B

Ich bin echt bisschen verzweifelt, weil ich nicht so genau weiß, wie ich das Problem lösen kann. Der freue ich mich über jede Antwort & bedanke mich schonmal für Euere Bemühungen.

Grüße,

Felix