Linearer Modus

Klebestreifen · 03.01.2017 05:13

Hallöle,
ich brauch mal eure Hilfe beim konfigurieren meines OpenVPN Servers. Ich hoffe jemand kann mir da mal unter die Ärmchen greifen.

Es ist folgendes geplant:

Alle Clients und auch der Server sind im VPN sichtbar! (Auch SMB!)
Die IP Adressen, die vom VPN-Server zugewiesen werden sollen 192.168.222.2-255 sein. Wen Ihr meint, dass das für ein VPN ungeeignet ist, dann mich bitte aufklären!
Der öffentliche Traffic der User soll NICHT über den VPN laufen! Das heißt, Surfen und Downloads laufen noch über die IP des Users, und werden nicht getunnelt!
Es soll keine Firewall innerhalb durch den VPN Server geben, da mit alle Verbindungen unbeeinträchtigt laufen, auch wenn es unsicher ist. Wer eben einmal drin ist, ist erstmal wirklich drin.

Die Erstellung der Keys und Zertifikate bekomme ich hin. Nur mit den anlegen der Konfigurationen tuh ich mich schwer (inkl. Clients).

Ich hoffe mann kann das umsetzen! Wen OpenVPN dafür absolut ungeeignet ist, brauch ich mal einen Guid, wie ich das eurer Meinung nach am besten umsetzen könnte.

hier ma' das was ich bis her einigermaßen hin bekam:

Code:

#################################################

# 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).

# and

# Diffie hellman parameters.

# Generate your own with:

#   openssl dhparam -out dh2048.pem 2048

ca ./easy-rsa2/keys/ca.crt 

cert ./easy-rsa2/keys/server.crt   # Network topology 

key ./easy-rsa2/keys/server.key    # Diese Datei geheim halten.# Should be subnet (addressing via IP)

dh ./easy-rsa2/keys/dh2048.pem     # Diffie-Hellman-Parameter

# 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 192.168.210.1 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 200

# It's a good idea to reduce the OpenVPN

# daemon's privileges after initialization.

#

# You can uncomment this out on

# non-Windows systems.

;user openvpn

;group openvpn

# 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

03.01.2017 12:41

Du hast sowohl tun als auch tap deaktiviert. Mach das
;dev tun
zu
dev tun

Bei der Server-Zeile musst du das als Netz angeben statt als IP. Mach mal aus
server 192.168.210.1 255.255.255.0
ein
server 192.168.210.0 255.255.255.0

Anschließend den Dienst komplett neu starten. Der Rest sieht ok aus.

Für die Clients tuts die Beispiel-Config, die du unter /usr/share/doc/openvpn/examples/sample-config-files/client.conf findest. Pass dort den Servernamen sowie die Pfade zu den Client-Zertifikaten an und verteil sie zusammen mit ca.crt, clietname.crt und clientname.key an die Clients.

Falls es noch nicht klappt, geb kurz Bescheid. Ich hab damals meine Abschlussarbeit für die IHK über OpenVPN geschrieben und kann dir gerne weitergehend helfen.

Klebestreifen · 03.01.2017 22:42

(03.01.2017 12:41)mrshadowtux schrieb: Du hast sowohl tun als auch tap deaktiviert. Mach das
;dev tun
zu
dev tun

Bei der Server-Zeile musst du das als Netz angeben statt als IP. Mach mal aus
server 192.168.210.1 255.255.255.0
ein
server 192.168.210.0 255.255.255.0

Anschließend den Dienst komplett neu starten. Der Rest sieht ok aus.

Für die Clients tuts die Beispiel-Config, die du unter /usr/share/doc/openvpn/examples/sample-config-files/client.conf findest. Pass dort den Servernamen sowie die Pfade zu den Client-Zertifikaten an und verteil sie zusammen mit ca.crt, clietname.crt und clientname.key an die Clients.

Falls es noch nicht klappt, geb kurz Bescheid. Ich hab damals meine Abschlussarbeit für die IHK über OpenVPN geschrieben und kann dir gerne weitergehend helfen.

Geht noch nicht. hängt es damit zusammen, dass ich einen V-Server verwende??? Hab alles gemacht was du sagtest. Das Problem liegt nun darin, dass ich keine Verbindung bekomme....

Code:

Tue Jan 03 18:10:53 2017 OpenVPN 2.4.0 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 27 2016

Tue Jan 03 18:10:53 2017 Windows version 6.2 (Windows 8 or greater) 64bit

Tue Jan 03 18:10:53 2017 library versions: OpenSSL 1.0.2i  22 Sep 2016, LZO 2.09

Tue Jan 03 18:10:53 2017 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340

Tue Jan 03 18:10:53 2017 Need hold release from management interface, waiting...

Tue Jan 03 18:10:53 2017 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340

Tue Jan 03 18:10:53 2017 MANAGEMENT: CMD 'state on'

Tue Jan 03 18:10:53 2017 MANAGEMENT: CMD 'log all on'

Tue Jan 03 18:10:53 2017 MANAGEMENT: CMD 'hold off'

Tue Jan 03 18:10:53 2017 MANAGEMENT: CMD 'hold release'

Tue Jan 03 18:10:53 2017 MANAGEMENT: >STATE:1483463453,RESOLVE,,,,,,

Tue Jan 03 18:10:53 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:10:53 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:10:53 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:10:53 2017 MANAGEMENT: >STATE:1483463453,TCP_CONNECT,,,,,,

Tue Jan 03 18:12:54 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:12:54 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:12:54 2017 MANAGEMENT: >STATE:1483463574,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:12:54 2017 Restart pause, 5 second(s)

Tue Jan 03 18:12:59 2017 MANAGEMENT: >STATE:1483463579,RESOLVE,,,,,,

Tue Jan 03 18:12:59 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:12:59 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:12:59 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:12:59 2017 MANAGEMENT: >STATE:1483463579,TCP_CONNECT,,,,,,

Tue Jan 03 18:14:59 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:14:59 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:14:59 2017 MANAGEMENT: >STATE:1483463699,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:14:59 2017 Restart pause, 5 second(s)

Tue Jan 03 18:15:04 2017 MANAGEMENT: >STATE:1483463704,RESOLVE,,,,,,

Tue Jan 03 18:15:04 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:15:04 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:15:04 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:15:04 2017 MANAGEMENT: >STATE:1483463704,TCP_CONNECT,,,,,,

Tue Jan 03 18:17:04 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:17:04 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:17:04 2017 MANAGEMENT: >STATE:1483463824,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:17:04 2017 Restart pause, 5 second(s)

Tue Jan 03 18:17:09 2017 MANAGEMENT: >STATE:1483463829,RESOLVE,,,,,,

Tue Jan 03 18:17:09 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:17:09 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:17:09 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:17:09 2017 MANAGEMENT: >STATE:1483463829,TCP_CONNECT,,,,,,

Tue Jan 03 18:19:10 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:19:10 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:19:10 2017 MANAGEMENT: >STATE:1483463950,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:19:10 2017 Restart pause, 5 second(s)

Tue Jan 03 18:19:15 2017 MANAGEMENT: >STATE:1483463955,RESOLVE,,,,,,

Tue Jan 03 18:19:15 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:19:15 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:19:15 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:19:15 2017 MANAGEMENT: >STATE:1483463955,TCP_CONNECT,,,,,,

Tue Jan 03 18:21:15 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:21:15 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:21:15 2017 MANAGEMENT: >STATE:1483464075,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:21:15 2017 Restart pause, 10 second(s)

Tue Jan 03 18:21:25 2017 MANAGEMENT: >STATE:1483464085,RESOLVE,,,,,,

Tue Jan 03 18:21:25 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:21:25 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:21:25 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:21:25 2017 MANAGEMENT: >STATE:1483464085,TCP_CONNECT,,,,,,

Tue Jan 03 18:23:26 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:23:26 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:23:26 2017 MANAGEMENT: >STATE:1483464206,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:23:26 2017 Restart pause, 20 second(s)

Tue Jan 03 18:23:46 2017 MANAGEMENT: >STATE:1483464226,RESOLVE,,,,,,

Tue Jan 03 18:23:46 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:23:46 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:23:46 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:23:46 2017 MANAGEMENT: >STATE:1483464226,TCP_CONNECT,,,,,,

Tue Jan 03 18:25:46 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:25:46 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:25:46 2017 MANAGEMENT: >STATE:1483464346,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:25:46 2017 Restart pause, 40 second(s)

Tue Jan 03 18:26:26 2017 MANAGEMENT: >STATE:1483464386,RESOLVE,,,,,,

Tue Jan 03 18:26:26 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:26:26 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:26:26 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:26:26 2017 MANAGEMENT: >STATE:1483464386,TCP_CONNECT,,,,,,

Tue Jan 03 18:28:27 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:28:27 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:28:27 2017 MANAGEMENT: >STATE:1483464507,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:28:27 2017 Restart pause, 80 second(s)

Tue Jan 03 18:29:47 2017 MANAGEMENT: >STATE:1483464587,RESOLVE,,,,,,

Tue Jan 03 18:29:47 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:29:47 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:29:47 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:29:47 2017 MANAGEMENT: >STATE:1483464587,TCP_CONNECT,,,,,,

Tue Jan 03 18:31:47 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:31:47 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:31:47 2017 MANAGEMENT: >STATE:1483464707,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:31:47 2017 Restart pause, 160 second(s)

Tue Jan 03 18:34:27 2017 MANAGEMENT: >STATE:1483464867,RESOLVE,,,,,,

Tue Jan 03 18:34:27 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:34:27 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:34:27 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:34:27 2017 MANAGEMENT: >STATE:1483464867,TCP_CONNECT,,,,,,

Tue Jan 03 18:36:27 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:36:27 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:36:27 2017 MANAGEMENT: >STATE:1483464987,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:36:27 2017 Restart pause, 300 second(s)

Tue Jan 03 18:41:27 2017 MANAGEMENT: >STATE:1483465287,RESOLVE,,,,,,

Tue Jan 03 18:41:27 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:41:27 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:41:27 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:41:27 2017 MANAGEMENT: >STATE:1483465287,TCP_CONNECT,,,,,,

Tue Jan 03 18:43:28 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:43:28 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:43:28 2017 MANAGEMENT: >STATE:1483465408,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:43:28 2017 Restart pause, 300 second(s)

Tue Jan 03 18:48:28 2017 MANAGEMENT: >STATE:1483465708,RESOLVE,,,,,,

Tue Jan 03 18:48:28 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:48:28 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:48:28 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:48:28 2017 MANAGEMENT: >STATE:1483465708,TCP_CONNECT,,,,,,

Tue Jan 03 18:50:29 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:50:29 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:50:29 2017 MANAGEMENT: >STATE:1483465829,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:50:29 2017 Restart pause, 300 second(s)

Tue Jan 03 18:55:29 2017 MANAGEMENT: >STATE:1483466129,RESOLVE,,,,,,

Tue Jan 03 18:55:29 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 18:55:29 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 18:55:29 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 18:55:29 2017 MANAGEMENT: >STATE:1483466129,TCP_CONNECT,,,,,,

Tue Jan 03 18:57:29 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 18:57:29 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 18:57:29 2017 MANAGEMENT: >STATE:1483466249,RECONNECTING,init_instance,,,,,

Tue Jan 03 18:57:29 2017 Restart pause, 300 second(s)

Tue Jan 03 19:02:29 2017 MANAGEMENT: >STATE:1483466549,RESOLVE,,,,,,

Tue Jan 03 19:02:29 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:02:29 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:02:29 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:02:29 2017 MANAGEMENT: >STATE:1483466549,TCP_CONNECT,,,,,,

Tue Jan 03 19:04:30 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 19:04:30 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 19:04:30 2017 MANAGEMENT: >STATE:1483466670,RECONNECTING,init_instance,,,,,

Tue Jan 03 19:04:30 2017 Restart pause, 300 second(s)

Tue Jan 03 19:09:30 2017 MANAGEMENT: >STATE:1483466970,RESOLVE,,,,,,

Tue Jan 03 19:09:30 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:09:30 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:09:30 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:09:30 2017 MANAGEMENT: >STATE:1483466970,TCP_CONNECT,,,,,,

Tue Jan 03 19:11:31 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 19:11:31 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 19:11:31 2017 MANAGEMENT: >STATE:1483467091,RECONNECTING,init_instance,,,,,

Tue Jan 03 19:11:31 2017 Restart pause, 300 second(s)

Tue Jan 03 19:16:31 2017 MANAGEMENT: >STATE:1483467391,RESOLVE,,,,,,

Tue Jan 03 19:16:31 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:16:31 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:16:31 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:16:31 2017 MANAGEMENT: >STATE:1483467391,TCP_CONNECT,,,,,,

Tue Jan 03 19:18:32 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 19:18:32 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 19:18:32 2017 MANAGEMENT: >STATE:1483467512,RECONNECTING,init_instance,,,,,

Tue Jan 03 19:18:32 2017 Restart pause, 300 second(s)

Tue Jan 03 19:23:32 2017 MANAGEMENT: >STATE:1483467812,RESOLVE,,,,,,

Tue Jan 03 19:23:32 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:23:32 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:23:32 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:23:32 2017 MANAGEMENT: >STATE:1483467812,TCP_CONNECT,,,,,,

Tue Jan 03 19:25:33 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 19:25:33 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 19:25:33 2017 MANAGEMENT: >STATE:1483467933,RECONNECTING,init_instance,,,,,

Tue Jan 03 19:25:33 2017 Restart pause, 300 second(s)

Tue Jan 03 19:30:33 2017 MANAGEMENT: >STATE:1483468233,RESOLVE,,,,,,

Tue Jan 03 19:30:33 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:30:33 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:30:33 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:30:33 2017 MANAGEMENT: >STATE:1483468233,TCP_CONNECT,,,,,,

Tue Jan 03 19:32:33 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 19:32:33 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 19:32:33 2017 MANAGEMENT: >STATE:1483468353,RECONNECTING,init_instance,,,,,

Tue Jan 03 19:32:33 2017 Restart pause, 300 second(s)

Tue Jan 03 19:37:33 2017 MANAGEMENT: >STATE:1483468653,RESOLVE,,,,,,

Tue Jan 03 19:37:33 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:37:33 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:37:33 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:37:33 2017 MANAGEMENT: >STATE:1483468653,TCP_CONNECT,,,,,,

Tue Jan 03 19:39:33 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 19:39:33 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 19:39:33 2017 MANAGEMENT: >STATE:1483468773,RECONNECTING,init_instance,,,,,

Tue Jan 03 19:39:33 2017 Restart pause, 300 second(s)

Tue Jan 03 19:44:33 2017 MANAGEMENT: >STATE:1483469073,RESOLVE,,,,,,

Tue Jan 03 19:44:33 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:44:33 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:44:33 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:44:33 2017 MANAGEMENT: >STATE:1483469073,TCP_CONNECT,,,,,,

Tue Jan 03 19:46:34 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 19:46:34 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 19:46:34 2017 MANAGEMENT: >STATE:1483469194,RECONNECTING,init_instance,,,,,

Tue Jan 03 19:46:34 2017 Restart pause, 300 second(s)

Tue Jan 03 19:51:34 2017 MANAGEMENT: >STATE:1483469494,RESOLVE,,,,,,

Tue Jan 03 19:51:34 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:51:34 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:51:34 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:51:34 2017 MANAGEMENT: >STATE:1483469494,TCP_CONNECT,,,,,,

Tue Jan 03 19:53:34 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 19:53:34 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 19:53:34 2017 MANAGEMENT: >STATE:1483469614,RECONNECTING,init_instance,,,,,

Tue Jan 03 19:53:34 2017 Restart pause, 300 second(s)

Tue Jan 03 19:58:34 2017 MANAGEMENT: >STATE:1483469914,RESOLVE,,,,,,

Tue Jan 03 19:58:34 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 19:58:34 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 19:58:34 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 19:58:34 2017 MANAGEMENT: >STATE:1483469914,TCP_CONNECT,,,,,,

Tue Jan 03 20:00:34 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:00:34 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:00:34 2017 MANAGEMENT: >STATE:1483470034,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:00:34 2017 Restart pause, 300 second(s)

Tue Jan 03 20:05:34 2017 MANAGEMENT: >STATE:1483470334,RESOLVE,,,,,,

Tue Jan 03 20:05:34 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 20:05:34 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 20:05:34 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 20:05:34 2017 MANAGEMENT: >STATE:1483470334,TCP_CONNECT,,,,,,

Tue Jan 03 20:07:35 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:07:35 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:07:35 2017 MANAGEMENT: >STATE:1483470455,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:07:35 2017 Restart pause, 300 second(s)

Tue Jan 03 20:12:35 2017 MANAGEMENT: >STATE:1483470755,RESOLVE,,,,,,

Tue Jan 03 20:12:35 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 20:12:35 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 20:12:35 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 20:12:35 2017 MANAGEMENT: >STATE:1483470755,TCP_CONNECT,,,,,,

Tue Jan 03 20:14:36 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:14:36 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:14:36 2017 MANAGEMENT: >STATE:1483470876,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:14:36 2017 Restart pause, 300 second(s)

Tue Jan 03 20:19:36 2017 MANAGEMENT: >STATE:1483471176,RESOLVE,,,,,,

Tue Jan 03 20:19:36 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 20:19:36 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 20:19:36 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 20:19:36 2017 MANAGEMENT: >STATE:1483471176,TCP_CONNECT,,,,,,

Tue Jan 03 20:21:37 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:21:37 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:21:37 2017 MANAGEMENT: >STATE:1483471297,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:21:37 2017 Restart pause, 300 second(s)

Tue Jan 03 20:26:37 2017 MANAGEMENT: >STATE:1483471597,RESOLVE,,,,,,

Tue Jan 03 20:26:38 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 20:26:38 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 20:26:38 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 20:26:38 2017 MANAGEMENT: >STATE:1483471598,TCP_CONNECT,,,,,,

Tue Jan 03 20:28:38 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:28:38 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:28:38 2017 MANAGEMENT: >STATE:1483471718,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:28:38 2017 Restart pause, 300 second(s)

Tue Jan 03 20:33:38 2017 MANAGEMENT: >STATE:1483472018,RESOLVE,,,,,,

Tue Jan 03 20:33:38 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 20:33:38 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 20:33:38 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 20:33:38 2017 MANAGEMENT: >STATE:1483472018,TCP_CONNECT,,,,,,

Tue Jan 03 20:35:39 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:35:39 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:35:39 2017 MANAGEMENT: >STATE:1483472139,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:35:39 2017 Restart pause, 300 second(s)

Tue Jan 03 20:40:39 2017 MANAGEMENT: >STATE:1483472439,RESOLVE,,,,,,

Tue Jan 03 20:40:39 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 20:40:39 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 20:40:39 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 20:40:39 2017 MANAGEMENT: >STATE:1483472439,TCP_CONNECT,,,,,,

Tue Jan 03 20:42:39 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:42:39 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:42:39 2017 MANAGEMENT: >STATE:1483472559,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:42:39 2017 Restart pause, 300 second(s)

Tue Jan 03 20:47:39 2017 MANAGEMENT: >STATE:1483472859,RESOLVE,,,,,,

Tue Jan 03 20:47:39 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 20:47:39 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 20:47:39 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 20:47:39 2017 MANAGEMENT: >STATE:1483472859,TCP_CONNECT,,,,,,

Tue Jan 03 20:49:40 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:49:40 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:49:40 2017 MANAGEMENT: >STATE:1483472980,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:49:40 2017 Restart pause, 300 second(s)

Tue Jan 03 20:54:40 2017 MANAGEMENT: >STATE:1483473280,RESOLVE,,,,,,

Tue Jan 03 20:54:40 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 20:54:40 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 20:54:40 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 20:54:40 2017 MANAGEMENT: >STATE:1483473280,TCP_CONNECT,,,,,,

Tue Jan 03 20:56:40 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 20:56:40 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 20:56:40 2017 MANAGEMENT: >STATE:1483473400,RECONNECTING,init_instance,,,,,

Tue Jan 03 20:56:40 2017 Restart pause, 300 second(s)

Tue Jan 03 21:01:40 2017 MANAGEMENT: >STATE:1483473700,RESOLVE,,,,,,

Tue Jan 03 21:01:40 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:01:40 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:01:40 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:01:40 2017 MANAGEMENT: >STATE:1483473700,TCP_CONNECT,,,,,,

Tue Jan 03 21:03:40 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:03:40 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:03:40 2017 MANAGEMENT: >STATE:1483473820,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:03:40 2017 Restart pause, 300 second(s)

Tue Jan 03 21:08:40 2017 MANAGEMENT: >STATE:1483474120,RESOLVE,,,,,,

Tue Jan 03 21:08:40 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:08:40 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:08:40 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:08:40 2017 MANAGEMENT: >STATE:1483474120,TCP_CONNECT,,,,,,

Tue Jan 03 21:10:40 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:10:40 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:10:40 2017 MANAGEMENT: >STATE:1483474240,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:10:40 2017 Restart pause, 300 second(s)

Tue Jan 03 21:15:40 2017 MANAGEMENT: >STATE:1483474540,RESOLVE,,,,,,

Tue Jan 03 21:15:40 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:15:40 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:15:40 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:15:40 2017 MANAGEMENT: >STATE:1483474540,TCP_CONNECT,,,,,,

Tue Jan 03 21:17:40 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:17:40 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:17:40 2017 MANAGEMENT: >STATE:1483474660,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:17:40 2017 Restart pause, 300 second(s)

Tue Jan 03 21:22:40 2017 MANAGEMENT: >STATE:1483474960,RESOLVE,,,,,,

Tue Jan 03 21:22:40 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:22:40 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:22:40 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:22:40 2017 MANAGEMENT: >STATE:1483474960,TCP_CONNECT,,,,,,

Tue Jan 03 21:24:41 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:24:41 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:24:41 2017 MANAGEMENT: >STATE:1483475081,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:24:41 2017 Restart pause, 300 second(s)

Tue Jan 03 21:29:41 2017 MANAGEMENT: >STATE:1483475381,RESOLVE,,,,,,

Tue Jan 03 21:29:41 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:29:41 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:29:41 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:29:41 2017 MANAGEMENT: >STATE:1483475381,TCP_CONNECT,,,,,,

Tue Jan 03 21:31:41 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:31:41 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:31:41 2017 MANAGEMENT: >STATE:1483475501,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:31:41 2017 Restart pause, 300 second(s)

Tue Jan 03 21:36:41 2017 MANAGEMENT: >STATE:1483475801,RESOLVE,,,,,,

Tue Jan 03 21:36:41 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:36:41 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:36:41 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:36:41 2017 MANAGEMENT: >STATE:1483475801,TCP_CONNECT,,,,,,

Tue Jan 03 21:38:41 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:38:41 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:38:41 2017 MANAGEMENT: >STATE:1483475921,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:38:41 2017 Restart pause, 300 second(s)

Tue Jan 03 21:43:41 2017 MANAGEMENT: >STATE:1483476221,RESOLVE,,,,,,

Tue Jan 03 21:43:41 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:43:41 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:43:41 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:43:41 2017 MANAGEMENT: >STATE:1483476221,TCP_CONNECT,,,,,,

Tue Jan 03 21:45:42 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:45:42 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:45:42 2017 MANAGEMENT: >STATE:1483476342,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:45:42 2017 Restart pause, 300 second(s)

Tue Jan 03 21:50:42 2017 MANAGEMENT: >STATE:1483476642,RESOLVE,,,,,,

Tue Jan 03 21:50:42 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:50:42 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:50:42 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:50:42 2017 MANAGEMENT: >STATE:1483476642,TCP_CONNECT,,,,,,

Tue Jan 03 21:52:42 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:52:42 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:52:42 2017 MANAGEMENT: >STATE:1483476762,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:52:42 2017 Restart pause, 300 second(s)

Tue Jan 03 21:57:42 2017 MANAGEMENT: >STATE:1483477062,RESOLVE,,,,,,

Tue Jan 03 21:57:42 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 21:57:42 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 21:57:42 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 21:57:42 2017 MANAGEMENT: >STATE:1483477062,TCP_CONNECT,,,,,,

Tue Jan 03 21:59:42 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 21:59:42 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 21:59:42 2017 MANAGEMENT: >STATE:1483477182,RECONNECTING,init_instance,,,,,

Tue Jan 03 21:59:42 2017 Restart pause, 300 second(s)

Tue Jan 03 22:04:42 2017 MANAGEMENT: >STATE:1483477482,RESOLVE,,,,,,

Tue Jan 03 22:04:42 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 22:04:42 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 22:04:42 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 22:04:42 2017 MANAGEMENT: >STATE:1483477482,TCP_CONNECT,,,,,,

Tue Jan 03 22:06:43 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 22:06:43 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 22:06:43 2017 MANAGEMENT: >STATE:1483477603,RECONNECTING,init_instance,,,,,

Tue Jan 03 22:06:43 2017 Restart pause, 300 second(s)

Tue Jan 03 22:11:43 2017 MANAGEMENT: >STATE:1483477903,RESOLVE,,,,,,

Tue Jan 03 22:11:43 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 22:11:43 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 22:11:43 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 22:11:43 2017 MANAGEMENT: >STATE:1483477903,TCP_CONNECT,,,,,,

Tue Jan 03 22:13:43 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 22:13:43 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 22:13:43 2017 MANAGEMENT: >STATE:1483478023,RECONNECTING,init_instance,,,,,

Tue Jan 03 22:13:43 2017 Restart pause, 300 second(s)

Tue Jan 03 22:18:43 2017 MANAGEMENT: >STATE:1483478323,RESOLVE,,,,,,

Tue Jan 03 22:18:43 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 22:18:43 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 22:18:43 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 22:18:43 2017 MANAGEMENT: >STATE:1483478323,TCP_CONNECT,,,,,,

Tue Jan 03 22:20:43 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 22:20:43 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 22:20:43 2017 MANAGEMENT: >STATE:1483478443,RECONNECTING,init_instance,,,,,

Tue Jan 03 22:20:43 2017 Restart pause, 300 second(s)

Tue Jan 03 22:25:43 2017 MANAGEMENT: >STATE:1483478743,RESOLVE,,,,,,

Tue Jan 03 22:25:43 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 22:25:43 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 22:25:43 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 22:25:43 2017 MANAGEMENT: >STATE:1483478743,TCP_CONNECT,,,,,,

Tue Jan 03 22:27:44 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Tue Jan 03 22:27:44 2017 SIGUSR1[connection failed(soft),init_instance] received, process restarting

Tue Jan 03 22:27:44 2017 MANAGEMENT: >STATE:1483478864,RECONNECTING,init_instance,,,,,

Tue Jan 03 22:27:44 2017 Restart pause, 300 second(s)

server.conf:

Code:

#################################################

# 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).

# and

# Diffie hellman parameters.

# Generate your own with:

#   openssl dhparam -out dh2048.pem 2048

ca ./easy-rsa2/keys/ca.crt 

cert ./easy-rsa2/keys/server.crt   # Network topology 

key ./easy-rsa2/keys/server.key    # Diese Datei geheim halten.# Should be subnet (addressing via IP)

dh ./easy-rsa2/keys/dh2048.pem     # Diffie-Hellman-Parameter

# 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 192.168.222.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 200

# It's a good idea to reduce the OpenVPN

# daemon's privileges after initialization.

#

# You can uncomment this out on

# non-Windows systems.

;user openvpn

;group openvpn

# 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

client.ovpn:

Code:

##############################################

# 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 klebe-streifen.de 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 ca.crt

cert client.crt

key client.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 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

Ich habe in den "config"-Ordner des Client folgende Dateien binär übertragen:

ca.crt
client.crt
client.csr
client.key
client.ovpn

Die Dateien habe ich auf dem Server in eine .tar.gz gepackt und dann übertragen.

03.01.2017 22:53

Zitat:Tue Jan 03 18:12:54 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)

Sieht aus. als ob das ne Firewall wegdroppt. Am Server Port freigegeben und am Client mal ausgehend erlaubt?

Klebestreifen · 03.01.2017 23:04

(03.01.2017 22:53)mrshadowtux schrieb:
Zitat:Tue Jan 03 18:12:54 2017 TCP: connect to [AF_INET]81.169.232.7:1194 failed: Connection timed out (WSAETIMEDOUT)
Sieht aus. als ob das ne Firewall wegdroppt. Am Server Port freigegeben und am Client mal ausgehend erlaubt?

Client seitig sollte nichts im Weg stehen. Die Windows Firewall habe ich test weise abgeschaltet.
Am Server habe ich glaube keine eine Firewall, es sei denn, es wurde Werkseitig eine installiert.

Ab hier hängt sich der Log bis zum Time-Out auf:

Code:

Tue Jan 03 23:00:10 2017 OpenVPN 2.4.0 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 27 2016

Tue Jan 03 23:00:10 2017 Windows version 6.2 (Windows 8 or greater) 64bit

Tue Jan 03 23:00:10 2017 library versions: OpenSSL 1.0.2i  22 Sep 2016, LZO 2.09

Enter Management Password:

Tue Jan 03 23:00:10 2017 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340

Tue Jan 03 23:00:10 2017 Need hold release from management interface, waiting...

Tue Jan 03 23:00:10 2017 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340

Tue Jan 03 23:00:10 2017 MANAGEMENT: CMD 'state on'

Tue Jan 03 23:00:10 2017 MANAGEMENT: CMD 'log all on'

Tue Jan 03 23:00:10 2017 MANAGEMENT: CMD 'hold off'

Tue Jan 03 23:00:10 2017 MANAGEMENT: CMD 'hold release'

Tue Jan 03 23:00:10 2017 MANAGEMENT: >STATE:1483480810,RESOLVE,,,,,,

Tue Jan 03 23:00:10 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]81.169.232.7:1194

Tue Jan 03 23:00:10 2017 Socket Buffers: R=[65536->65536] S=[65536->65536]

Tue Jan 03 23:00:10 2017 Attempting to establish TCP connection with [AF_INET]81.169.232.7:1194 [nonblock]

Tue Jan 03 23:00:10 2017 MANAGEMENT: >STATE:1483480810,TCP_CONNECT,,,,,,

04.01.2017 00:08

Mach mal als Root:
modprobe tun
am Server. Wenn das scheitert, hast du einen OpenVZ-vServer und dein Anbieter hat dir das deaktiviert. Gib mir auch mal ne Ausgabe von
uname -a
dann kann ich das verifizieren.

***DosAmp*** · 04.01.2017 00:37

Was für ein Linux-System läuft am Server? Insbesondere bei einer RHEL/CentOS-Installation ist standardmäßig eine Firewall aktiv, in der OpenVPN erst freigeschalten werden muss.

Das OpenVPN-Log ist in der Regel als Teil des Syslogs (/var/log/syslog) zu finden, ansonsten im systemd-Journal (journalctl -b _COMM=openvpn).

Klebestreifen · 04.01.2017 00:47

(04.01.2017 00:08)mrshadowtux schrieb: Mach mal als Root:
modprobe tun
am Server. Wenn das scheitert, hast du einen OpenVZ-vServer und dein Anbieter hat dir das deaktiviert. Gib mir auch mal ne Ausgabe von
uname -a
dann kann ich das verifizieren.

Code:

root@h2516500:/etc/openvpn# modprobe tun

modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file '/lib/modules/4.4.0-042stab120.6/modules.builtin.bin'

modprobe: FATAL: Module tun not found in directory /lib/modules/4.4.0-042stab120.6

root@h2516500:/etc/openvpn# uname -a

Linux h2516500.stratoserver.net 4.4.0-042stab120.6 #1 SMP Thu Oct 27 16:59:03 MSK 2016 x86_64 x86_64 x86_64 GNU/Linux

(04.01.2017 00:37)DosAmp schrieb: Was für ein Linux-System läuft am Server? Insbesondere bei einer RHEL/CentOS-Installation ist standardmäßig eine Firewall aktiv, in der OpenVPN erst freigeschalten werden muss.

Das OpenVPN-Log ist in der Regel als Teil des Syslogs (/var/log/syslog) zu finden, ansonsten im systemd-Journal (journalctl -b _COMM=openvpn).

Ich benutze Ubuntu 16.4 x64

Code:

root@h2516500:/etc/openvpn# journalctl -b _COMM=openvpn

-- No entries --

root@h2516500:/etc/openvpn# cat /var/log/syslog

root@h2516500:/etc/openvpn# cd /var/log

root@h2516500:/var/log# ls -lah

total 5,2M

drwxrwxr-x  5 root   syslog 4,0K Jan  4 00:24 .

drwxr-xr-x 11 root   root   1,3K Dez 17 13:58 ..

-rw-r--r--  1 root   root      0 Jan  1 00:24 alternatives.log

-rw-r--r--  1 root   root   5,2K Dez 20 23:18 alternatives.log.1

drwxr-xr-x  2 root   root   4,0K Jan  1 00:24 apt

-rw-r--r--  1 root   root   2,2K Jan  3 00:59 aptitude

-rw-r-----  1 syslog adm    793K Jan  4 00:56 auth.log

-rw-r-----  1 syslog adm    755K Jan  2 00:24 auth.log.1

-rw-r-----  1 syslog adm     56K Dez 25 00:24 auth.log.2.gz

-rw-rw----  1 root   utmp   1,3M Jan  4 00:21 btmp

-rw-------  1 root   utmp   2,0M Dez 31 23:50 btmp.1

-rw-r-----  1 root   adm       1 Dez 17 13:58 dmesg

-rw-r--r--  1 root   root    19K Jan  3 01:05 dpkg.log

-rw-r--r--  1 root   root   149K Dez 20 22:53 dpkg.log.1

-rw-r--r--  1 root   root    32K Jan  3 02:57 faillog

-rw-r--r--  1 root   root      1 Dez 17 13:58 fontconfig.log

drwxr-xr-x  2 root   root    116 Dez 17 13:58 fsck

-rw-rw-r--  1 root   utmp   286K Jan  3 17:10 lastlog

-rw-r-----  1 syslog adm       0 Dez 25 00:24 mail.log

-rw-r-----  1 syslog adm    4,8K Dez 21 20:41 mail.log.1

-rw-r-----  1 syslog adm      95 Jan  4 00:56 syslog

-rw-r-----  1 syslog adm    3,2K Jan  4 00:24 syslog.1

-rw-r-----  1 syslog adm     953 Jan  3 00:24 syslog.2.gz

-rw-r-----  1 syslog adm     467 Jan  2 00:24 syslog.3.gz

-rw-r-----  1 syslog adm     749 Jan  1 00:24 syslog.4.gz

-rw-r-----  1 syslog adm     416 Dez 31 00:24 syslog.5.gz

-rw-r-----  1 syslog adm     412 Dez 30 00:24 syslog.6.gz

-rw-r-----  1 syslog adm     642 Dez 29 00:24 syslog.7.gz

drwxr-x---  2 root   adm    4,0K Dez 19 21:03 unattended-upgrades

-rw-rw-r--  1 root   utmp   6,0K Jan  3 18:15 wtmp

-rw-rw-r--  1 root   utmp    29K Dez 31 01:51 wtmp.1

-rw-------  1 root   root      0 Dez 20 22:47 yum.log

***DosAmp*** · 04.01.2017 13:28

(04.01.2017 00:47)Klebestreifen schrieb:
(04.01.2017 00:37)DosAmp schrieb: Das OpenVPN-Log ist in der Regel als Teil des Syslogs (/var/log/syslog) zu finden, ansonsten im systemd-Journal (journalctl -b _COMM=openvpn).

Ich benutze Ubuntu 16.4 x64

Code:

root@h2516500:/var/log# ls -lah … -rw-r----- 1 syslog adm 95 Jan 4 00:56 syslog -rw-r----- 1 syslog adm 3,2K Jan 4 00:24 syslog.1 -rw-r----- 1 syslog adm 953 Jan 3 00:24 syslog.2.gz -rw-r----- 1 syslog adm 467 Jan 2 00:24 syslog.3.gz -rw-r----- 1 syslog adm 749 Jan 1 00:24 syslog.4.gz -rw-r----- 1 syslog adm 416 Dez 31 00:24 syslog.5.gz -rw-r----- 1 syslog adm 412 Dez 30 00:24 syslog.6.gz -rw-r----- 1 syslog adm 642 Dez 29 00:24 syslog.7.gz

In dem Falle werden alle Einträge aus dem systemd-Journal in diese klassischen Logdateien weitergeleitet. Du siehst vermutlich bloß keine Einträge in "syslog", weil deine Logdateien anscheinend täglich zwischen 12 und 1 nachts von logrotate durchrotiert (syslog → syslog.1, syslog.1 → syslog.2.gz, …) und komprimiert werden. Für die komprimierten älteren Logs, die auf ".gz" enden, brauchst du, sofern relevant, zcat (z* = GZip-Komprimierung).
Außerdem hilft es, in der server.conf die "verb"osity von 3 auf 4 zu stellen (höhere Loglevel enthalten beim Betrieb als Daemon nur weniger nützliche Infos).

Die auf Ubuntu vorinstallierte Firewall "Uncomplicated FireWall" (Artikel ist älter, trifft im Kern aber noch so zu) ist standardmäßig deaktiviert. Du kannst das mit ufw überprüfen:

Code:

root@vieh:~# ufw status

Status: inactive

Außerdem richtig dumme Frage, aber läuft OpenVPN überhaupt?

Code:

root@vieh:~# service openvpn status

● openvpn.service - OpenVPN service

   Loaded: loaded (/lib/systemd/system/openvpn.service; enabled; vendor preset:)

   Active: inactive (dead)

(04.01.2017 00:47)Klebestreifen schrieb:

Code:

root@h2516500:/etc/openvpn# modprobe tun modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file '/lib/modules/4.4.0-042stab120.6/modules.builtin.bin' modprobe: FATAL: Module tun not found in directory /lib/modules/4.4.0-042stab120.6

Versuch mal depmod -a, um die fehlende Datei modules.builtin.bin (welche eine Liste von Modulen anzeigt, die fest in den Linux-Kernel kompiliert wurden) anzulegen. Wenn es danach nicht funktioniert, hat der installierte Kernel leider weder den tun/tap-Adapter eingebaut (insbesondere fehlt dann dessen Kernel-Schnittstelle /dev/net/tun) noch als Modul dabei.
In dem Falle müsste man recherchieren, ob und wie man bei Strato einen dafür passenden Kernel (z. B. den standardmäßigen "server"- oder "virtual"-Kernel) installieren darf/kann.

Klebestreifen · 04.01.2017 21:04

(04.01.2017 13:28)DosAmp schrieb: Wenn es danach nicht funktioniert, hat der installierte Kernel leider weder den tun/tap-Adapter eingebaut (insbesondere fehlt dann dessen Kernel-Schnittstelle /dev/net/tun) noch als Modul dabei.
In dem Falle müsste man recherchieren, ob und wie man bei Strato einen dafür passenden Kernel (z. B. den standardmäßigen "server"- oder "virtual"-Kernel) installieren darf/kann.

Genau das trifft zu.
Hebe ich andere Möglichkeiten ein Intranet-(VPN) einzurichten ohne diese Module?