achim50
13.01.16, 07:50
Hallo zusammen,
ich versuche das Netzwerk hinter einem Client zu erreichen,um dessen Netzwerkdrucker / Freigaben zu nutzen.
Der Windows-Client baut die Verbindung per OpenVPN mit einem Windows-Server auf.
Das Routen klappt leider nicht.
Der Server steht in einem Rechenzentrum und das Routen "versuche" ich per client-config-dir !
( oder ist es einfacher das Routen per Fritzbox zu machen welche beim Client steht )
Client Netz ist das 192.168.10.0
Ich vermute das es an diesem Fehler liegt weil der Netzwerkadapter nicht aktiv ist, was auch immer das heißen soll.
( Das ganze Log poste ich unten )
Tue Jan 12 14:23:09 2016 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 0.0.0.0 192.168.15.1 METRIC 512
Tue Jan 12 14:23:09 2016 Warning: route gateway is not reachable on any active network adapters: 192.168.15.1
Tue Jan 12 14:23:09 2016 Route addition via IPAPI failed [adaptive]
Tue Jan 12 14:23:09 2016 Route addition fallback to route.exe
Tue Jan 12 14:23:09 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\Sys tem32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.178.1 p=0 i=12 t=4 pr=3 a=5906 h=0 m=10/0/0/0/0
0.0.0.0 0.0.0.0 192.168.15.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=522/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
192.168.178.0 255.255.255.0 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
192.168.178.31 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
192.168.178.255 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 0.0.0.0 p=0 i=26 t=3 pr=3 a=6222 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 192.168.178.31 p=0 i=12 t=3 pr=3 a=6219 h=0 m=266/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 0.0.0.0 p=0 i=26 t=3 pr=3 a=6222 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=6219 h=0 m=266/0/0/0/0
SYSTEM ADAPTER LIST
Hier die Server.conf:
Zertifikate
dh "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\dh1024.pem"
ca "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\Server01.crt"
key "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\Server01.key"
Server und Netzwerk
local 178.XX.XX.XX #LAN-Adresse des Servers
port 1194
proto udp
dev tap
server 192.168.15.0 255.255.255.0 #Subnetz
client-config-dir "C:\\Program Files\\OpenVPN\\vpn"
ifconfig-pool-persist ipp.txt
comp-lzo
persist-key
persist-tun
keepalive 10 120
Log
status "C:\\Program Files\\OpenVPN\\log\\openvpn-status.log"
log "C:\\Program Files\\OpenVPN\\log\\openvpn.log"
log-append "C:\\Program Files\\OpenVPN\\log\\openvpn.log"
verb 3
und hier die vom Client:
Zertifikate
ca "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\Client01.crt"
key "C:\\Program Files\\OpenVPN\\config\\Client01.key"
Client-Setup
client
dev tap
proto udp
remote 178.xx.xx.xx 1194 #Hostname anpassen
resolv-retry infinite
nobind
persist-key
persist-tun
route-metric 512
route 0.0.0.0 0.0.0.0
comp-lzo
verb 3
Das Log vom Client mit dem Fehler:
Tue Jan 12 14:22:28 2016 OpenVPN 2.3.10 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Jan 4 2016
Tue Jan 12 14:22:28 2016 Windows version 6.1 (Windows 7)
Tue Jan 12 14:22:28 2016 library versions: OpenSSL 1.0.1q 3 Dec 2015, LZO 2.09
Enter Management Password:
Tue Jan 12 14:22:28 2016 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Tue Jan 12 14:22:28 2016 Need hold release from management interface, waiting...
Tue Jan 12 14:22:29 2016 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Tue Jan 12 14:22:29 2016 MANAGEMENT: CMD 'state on'
Tue Jan 12 14:22:29 2016 MANAGEMENT: CMD 'log all on'
Tue Jan 12 14:22:29 2016 MANAGEMENT: CMD 'hold off'
Tue Jan 12 14:22:29 2016 MANAGEMENT: CMD 'hold release'
Tue Jan 12 14:22:29 2016 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 12 14:22:29 2016 Socket Buffers: R=[8192->8192] S=[8192->8192]
Tue Jan 12 14:22:29 2016 UDPv4 link local: [undef]
Tue Jan 12 14:22:29 2016 UDPv4 link remote: [AF_INET]178.XX.XX.XX:1194
Tue Jan 12 14:22:29 2016 MANAGEMENT: >STATE:1452604949,WAIT,,,
Tue Jan 12 14:22:29 2016 MANAGEMENT: >STATE:1452604949,AUTH,,,
Tue Jan 12 14:22:29 2016 TLS: Initial packet from [AF_INET]178.XX.XX.XX:1194, sid=8abc4756 b1418de9
Tue Jan 12 14:22:30 2016 VERIFY OK: depth=1, C=DE, ST=LU, L=XXXXX, O=XXXXXVPN, OU="IT & Networking", CN=server.XXXX.de, name="VPN_Key_XXXX", emailAddress=info@xx.de
Tue Jan 12 14:22:30 2016 VERIFY OK: depth=0, C=DE, ST=LU, L=XXXXX, O=XXXXXVPN, OU="IT & Networking", CN=server.XXXX.de, name="VPN_Key_XXXX", emailAddress=info@xx.de
Tue Jan 12 14:22:31 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 12 14:22:31 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 12 14:22:31 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 12 14:22:31 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 12 14:22:31 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Tue Jan 12 14:22:31 2016 [server.XXXX.de] Peer Connection Initiated with [AF_INET]178.XX.XX.XX:1194
Tue Jan 12 14:22:32 2016 MANAGEMENT: >STATE:1452604952,GET_CONFIG,,,
Tue Jan 12 14:22:33 2016 SENT CONTROL [server.XXXX.de]: 'PUSH_REQUEST' (status=1)
Tue Jan 12 14:22:34 2016 PUSH: Received control message: 'PUSH_REPLY,route-gateway 192.168.15.1,ping 10,ping-restart 120,ifconfig 192.168.15.2 255.255.255.0'
Tue Jan 12 14:22:34 2016 OPTIONS IMPORT: timers and/or timeouts modified
Tue Jan 12 14:22:34 2016 OPTIONS IMPORT: --ifconfig/up options modified
Tue Jan 12 14:22:34 2016 OPTIONS IMPORT: route-related options modified
Tue Jan 12 14:22:34 2016 ROUTE_GATEWAY 192.168.178.1/255.255.255.0 I=12 HWADDR=00:0c:29:ff:30:1a
Tue Jan 12 14:22:34 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Tue Jan 12 14:22:34 2016 MANAGEMENT: >STATE:1452604954,ASSIGN_IP,,192.168.15.2,
Tue Jan 12 14:22:34 2016 open_tun, tt->ipv6=0
Tue Jan 12 14:22:34 2016 TAP-WIN32 device [LAN-Verbindung 3] opened: \\.\Global\{8C99E531-62E0-4FCE-9EA9-61565FF1878F}.tap
Tue Jan 12 14:22:34 2016 TAP-Windows Driver Version 9.21
Tue Jan 12 14:22:34 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.15.2/255.255.255.0 on interface {8C99E531-62E0-4FCE-9EA9-61565FF1878F} [DHCP-serv: 192.168.15.0, lease-time: 31536000]
Tue Jan 12 14:22:34 2016 Successful ARP Flush on interface [26] {8C99E531-62E0-4FCE-9EA9-61565FF1878F}
Tue Jan 12 14:22:39 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:39 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:44 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:44 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:45 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:45 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:46 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:46 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:47 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:47 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:48 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:48 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:49 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:49 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:50 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:50 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:51 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:51 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:52 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:52 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:53 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:53 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:54 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:54 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:55 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:55 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:56 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:56 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:57 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:57 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:58 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:58 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:59 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:59 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:00 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:00 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:01 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:01 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:02 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:02 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:03 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:03 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:04 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:04 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:05 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:05 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:06 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:06 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:08 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:08 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:09 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:09 2016 MANAGEMENT: >STATE:1452604989,ADD_ROUTES,,,
Tue Jan 12 14:23:09 2016 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 0.0.0.0 192.168.15.1 METRIC 512
Tue Jan 12 14:23:09 2016 Warning: route gateway is not reachable on any active network adapters: 192.168.15.1
Tue Jan 12 14:23:09 2016 Route addition via IPAPI failed [adaptive]
Tue Jan 12 14:23:09 2016 Route addition fallback to route.exe
Tue Jan 12 14:23:09 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\Sys tem32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.178.1 p=0 i=12 t=4 pr=3 a=5906 h=0 m=10/0/0/0/0
0.0.0.0 0.0.0.0 192.168.15.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=522/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
192.168.178.0 255.255.255.0 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
192.168.178.31 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
192.168.178.255 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 0.0.0.0 p=0 i=26 t=3 pr=3 a=6222 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 192.168.178.31 p=0 i=12 t=3 pr=3 a=6219 h=0 m=266/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 0.0.0.0 p=0 i=26 t=3 pr=3 a=6222 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=6219 h=0 m=266/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Windows Adapter V9
Index = 26
GUID = {8C99E531-62E0-4FCE-9EA9-61565FF1878F}
IP = 0.0.0.0/0.0.0.0
MAC = 00:ff:8c:99:e5:31
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 0.0.0.0/255.255.255.255
DHCP LEASE OBTAINED = Tue Jan 12 14:23:09 2016
DHCP LEASE EXPIRES = Tue Jan 12 14:23:09 2016
DNS SERV =
TAP-Win32 Adapter OAS
Index = 23
GUID = {5A56AF30-8D6C-45D3-AF13-7842678CEC8F}
IP = 0.0.0.0/0.0.0.0
MAC = 00:ff:5a:56:af:30
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Jan 12 14:23:09 2016
DHCP LEASE EXPIRES = Tue Jan 12 14:23:09 2016
DNS SERV =
Bluetooth-Gerät (PAN)
Index = 15
GUID = {24E70D18-8779-4F0B-96F5-2792A44B794B}
IP = 0.0.0.0/0.0.0.0
MAC = 5c:f9:38:99:e7:93
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Jan 12 14:23:09 2016
DHCP LEASE EXPIRES = Tue Jan 12 14:23:09 2016
DNS SERV =
Intel(R) PRO/1000 MT-Netzwerkverbindung
Index = 12
GUID = {BF898205-6D24-4EB9-B28B-C290FB745879}
IP = 192.168.178.31/255.255.255.0
MAC = 00:0c:29:ff:30:1a
GATEWAY = 192.168.178.1/255.255.255.255 192.168.15.1/255.255.255.255
DHCP SERV = 192.168.178.1/255.255.255.255
DHCP LEASE OBTAINED = Tue Jan 12 12:44:43 2016
DHCP LEASE EXPIRES = Fri Jan 22 12:44:43 2016
DNS SERV = 192.168.178.1/255.255.255.255
Tue Jan 12 14:23:09 2016 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Tue Jan 12 14:23:09 2016 MANAGEMENT: >STATE:1452604989,CONNECTED,ERROR,192.168.15.2,178. XX.XX.XX
Tue Jan 12 14:24:28 2016 C:\Windows\system32\route.exe DELETE 0.0.0.0 MASK 0.0.0.0 192.168.15.1
Tue Jan 12 14:24:28 2016 Warning: route gateway is not reachable on any active network adapters: 192.168.15.1
Tue Jan 12 14:24:28 2016 Route deletion via IPAPI failed [adaptive]
Tue Jan 12 14:24:28 2016 Route deletion fallback to route.exe
Tue Jan 12 14:24:28 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\Sys tem32\Wbem
Tue Jan 12 14:24:28 2016 Closing TUN/TAP interface
Tue Jan 12 14:24:28 2016 SIGTERM[hard,] received, process exiting
Tue Jan 12 14:24:28 2016 MANAGEMENT: >STATE:1452605068,EXITING,SIGTERM,,
ich versuche das Netzwerk hinter einem Client zu erreichen,um dessen Netzwerkdrucker / Freigaben zu nutzen.
Der Windows-Client baut die Verbindung per OpenVPN mit einem Windows-Server auf.
Das Routen klappt leider nicht.
Der Server steht in einem Rechenzentrum und das Routen "versuche" ich per client-config-dir !
( oder ist es einfacher das Routen per Fritzbox zu machen welche beim Client steht )
Client Netz ist das 192.168.10.0
Ich vermute das es an diesem Fehler liegt weil der Netzwerkadapter nicht aktiv ist, was auch immer das heißen soll.
( Das ganze Log poste ich unten )
Tue Jan 12 14:23:09 2016 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 0.0.0.0 192.168.15.1 METRIC 512
Tue Jan 12 14:23:09 2016 Warning: route gateway is not reachable on any active network adapters: 192.168.15.1
Tue Jan 12 14:23:09 2016 Route addition via IPAPI failed [adaptive]
Tue Jan 12 14:23:09 2016 Route addition fallback to route.exe
Tue Jan 12 14:23:09 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\Sys tem32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.178.1 p=0 i=12 t=4 pr=3 a=5906 h=0 m=10/0/0/0/0
0.0.0.0 0.0.0.0 192.168.15.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=522/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
192.168.178.0 255.255.255.0 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
192.168.178.31 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
192.168.178.255 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 0.0.0.0 p=0 i=26 t=3 pr=3 a=6222 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 192.168.178.31 p=0 i=12 t=3 pr=3 a=6219 h=0 m=266/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 0.0.0.0 p=0 i=26 t=3 pr=3 a=6222 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=6219 h=0 m=266/0/0/0/0
SYSTEM ADAPTER LIST
Hier die Server.conf:
Zertifikate
dh "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\dh1024.pem"
ca "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\Server01.crt"
key "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\Server01.key"
Server und Netzwerk
local 178.XX.XX.XX #LAN-Adresse des Servers
port 1194
proto udp
dev tap
server 192.168.15.0 255.255.255.0 #Subnetz
client-config-dir "C:\\Program Files\\OpenVPN\\vpn"
ifconfig-pool-persist ipp.txt
comp-lzo
persist-key
persist-tun
keepalive 10 120
Log
status "C:\\Program Files\\OpenVPN\\log\\openvpn-status.log"
log "C:\\Program Files\\OpenVPN\\log\\openvpn.log"
log-append "C:\\Program Files\\OpenVPN\\log\\openvpn.log"
verb 3
und hier die vom Client:
Zertifikate
ca "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\Client01.crt"
key "C:\\Program Files\\OpenVPN\\config\\Client01.key"
Client-Setup
client
dev tap
proto udp
remote 178.xx.xx.xx 1194 #Hostname anpassen
resolv-retry infinite
nobind
persist-key
persist-tun
route-metric 512
route 0.0.0.0 0.0.0.0
comp-lzo
verb 3
Das Log vom Client mit dem Fehler:
Tue Jan 12 14:22:28 2016 OpenVPN 2.3.10 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Jan 4 2016
Tue Jan 12 14:22:28 2016 Windows version 6.1 (Windows 7)
Tue Jan 12 14:22:28 2016 library versions: OpenSSL 1.0.1q 3 Dec 2015, LZO 2.09
Enter Management Password:
Tue Jan 12 14:22:28 2016 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Tue Jan 12 14:22:28 2016 Need hold release from management interface, waiting...
Tue Jan 12 14:22:29 2016 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Tue Jan 12 14:22:29 2016 MANAGEMENT: CMD 'state on'
Tue Jan 12 14:22:29 2016 MANAGEMENT: CMD 'log all on'
Tue Jan 12 14:22:29 2016 MANAGEMENT: CMD 'hold off'
Tue Jan 12 14:22:29 2016 MANAGEMENT: CMD 'hold release'
Tue Jan 12 14:22:29 2016 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Tue Jan 12 14:22:29 2016 Socket Buffers: R=[8192->8192] S=[8192->8192]
Tue Jan 12 14:22:29 2016 UDPv4 link local: [undef]
Tue Jan 12 14:22:29 2016 UDPv4 link remote: [AF_INET]178.XX.XX.XX:1194
Tue Jan 12 14:22:29 2016 MANAGEMENT: >STATE:1452604949,WAIT,,,
Tue Jan 12 14:22:29 2016 MANAGEMENT: >STATE:1452604949,AUTH,,,
Tue Jan 12 14:22:29 2016 TLS: Initial packet from [AF_INET]178.XX.XX.XX:1194, sid=8abc4756 b1418de9
Tue Jan 12 14:22:30 2016 VERIFY OK: depth=1, C=DE, ST=LU, L=XXXXX, O=XXXXXVPN, OU="IT & Networking", CN=server.XXXX.de, name="VPN_Key_XXXX", emailAddress=info@xx.de
Tue Jan 12 14:22:30 2016 VERIFY OK: depth=0, C=DE, ST=LU, L=XXXXX, O=XXXXXVPN, OU="IT & Networking", CN=server.XXXX.de, name="VPN_Key_XXXX", emailAddress=info@xx.de
Tue Jan 12 14:22:31 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 12 14:22:31 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 12 14:22:31 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 12 14:22:31 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 12 14:22:31 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Tue Jan 12 14:22:31 2016 [server.XXXX.de] Peer Connection Initiated with [AF_INET]178.XX.XX.XX:1194
Tue Jan 12 14:22:32 2016 MANAGEMENT: >STATE:1452604952,GET_CONFIG,,,
Tue Jan 12 14:22:33 2016 SENT CONTROL [server.XXXX.de]: 'PUSH_REQUEST' (status=1)
Tue Jan 12 14:22:34 2016 PUSH: Received control message: 'PUSH_REPLY,route-gateway 192.168.15.1,ping 10,ping-restart 120,ifconfig 192.168.15.2 255.255.255.0'
Tue Jan 12 14:22:34 2016 OPTIONS IMPORT: timers and/or timeouts modified
Tue Jan 12 14:22:34 2016 OPTIONS IMPORT: --ifconfig/up options modified
Tue Jan 12 14:22:34 2016 OPTIONS IMPORT: route-related options modified
Tue Jan 12 14:22:34 2016 ROUTE_GATEWAY 192.168.178.1/255.255.255.0 I=12 HWADDR=00:0c:29:ff:30:1a
Tue Jan 12 14:22:34 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Tue Jan 12 14:22:34 2016 MANAGEMENT: >STATE:1452604954,ASSIGN_IP,,192.168.15.2,
Tue Jan 12 14:22:34 2016 open_tun, tt->ipv6=0
Tue Jan 12 14:22:34 2016 TAP-WIN32 device [LAN-Verbindung 3] opened: \\.\Global\{8C99E531-62E0-4FCE-9EA9-61565FF1878F}.tap
Tue Jan 12 14:22:34 2016 TAP-Windows Driver Version 9.21
Tue Jan 12 14:22:34 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.15.2/255.255.255.0 on interface {8C99E531-62E0-4FCE-9EA9-61565FF1878F} [DHCP-serv: 192.168.15.0, lease-time: 31536000]
Tue Jan 12 14:22:34 2016 Successful ARP Flush on interface [26] {8C99E531-62E0-4FCE-9EA9-61565FF1878F}
Tue Jan 12 14:22:39 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:39 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:44 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:44 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:45 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:45 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:46 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:46 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:47 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:47 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:48 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:48 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:49 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:49 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:50 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:50 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:51 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:51 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:52 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:52 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:53 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:53 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:54 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:54 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:55 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:55 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:56 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:56 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:57 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:57 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:58 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:58 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:22:59 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:22:59 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:00 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:00 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:01 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:01 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:02 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:02 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:03 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:03 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:04 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:04 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:05 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:05 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:06 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:06 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:08 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:08 2016 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 12 14:23:09 2016 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Tue Jan 12 14:23:09 2016 MANAGEMENT: >STATE:1452604989,ADD_ROUTES,,,
Tue Jan 12 14:23:09 2016 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 0.0.0.0 192.168.15.1 METRIC 512
Tue Jan 12 14:23:09 2016 Warning: route gateway is not reachable on any active network adapters: 192.168.15.1
Tue Jan 12 14:23:09 2016 Route addition via IPAPI failed [adaptive]
Tue Jan 12 14:23:09 2016 Route addition fallback to route.exe
Tue Jan 12 14:23:09 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\Sys tem32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.178.1 p=0 i=12 t=4 pr=3 a=5906 h=0 m=10/0/0/0/0
0.0.0.0 0.0.0.0 192.168.15.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=522/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
192.168.178.0 255.255.255.0 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
192.168.178.31 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
192.168.178.255 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=5906 h=0 m=266/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 0.0.0.0 p=0 i=26 t=3 pr=3 a=6222 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 192.168.178.31 p=0 i=12 t=3 pr=3 a=6219 h=0 m=266/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=9450 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 0.0.0.0 p=0 i=26 t=3 pr=3 a=6222 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 192.168.178.31 p=0 i=12 t=3 pr=3 a=6219 h=0 m=266/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Windows Adapter V9
Index = 26
GUID = {8C99E531-62E0-4FCE-9EA9-61565FF1878F}
IP = 0.0.0.0/0.0.0.0
MAC = 00:ff:8c:99:e5:31
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 0.0.0.0/255.255.255.255
DHCP LEASE OBTAINED = Tue Jan 12 14:23:09 2016
DHCP LEASE EXPIRES = Tue Jan 12 14:23:09 2016
DNS SERV =
TAP-Win32 Adapter OAS
Index = 23
GUID = {5A56AF30-8D6C-45D3-AF13-7842678CEC8F}
IP = 0.0.0.0/0.0.0.0
MAC = 00:ff:5a:56:af:30
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Jan 12 14:23:09 2016
DHCP LEASE EXPIRES = Tue Jan 12 14:23:09 2016
DNS SERV =
Bluetooth-Gerät (PAN)
Index = 15
GUID = {24E70D18-8779-4F0B-96F5-2792A44B794B}
IP = 0.0.0.0/0.0.0.0
MAC = 5c:f9:38:99:e7:93
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Jan 12 14:23:09 2016
DHCP LEASE EXPIRES = Tue Jan 12 14:23:09 2016
DNS SERV =
Intel(R) PRO/1000 MT-Netzwerkverbindung
Index = 12
GUID = {BF898205-6D24-4EB9-B28B-C290FB745879}
IP = 192.168.178.31/255.255.255.0
MAC = 00:0c:29:ff:30:1a
GATEWAY = 192.168.178.1/255.255.255.255 192.168.15.1/255.255.255.255
DHCP SERV = 192.168.178.1/255.255.255.255
DHCP LEASE OBTAINED = Tue Jan 12 12:44:43 2016
DHCP LEASE EXPIRES = Fri Jan 22 12:44:43 2016
DNS SERV = 192.168.178.1/255.255.255.255
Tue Jan 12 14:23:09 2016 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Tue Jan 12 14:23:09 2016 MANAGEMENT: >STATE:1452604989,CONNECTED,ERROR,192.168.15.2,178. XX.XX.XX
Tue Jan 12 14:24:28 2016 C:\Windows\system32\route.exe DELETE 0.0.0.0 MASK 0.0.0.0 192.168.15.1
Tue Jan 12 14:24:28 2016 Warning: route gateway is not reachable on any active network adapters: 192.168.15.1
Tue Jan 12 14:24:28 2016 Route deletion via IPAPI failed [adaptive]
Tue Jan 12 14:24:28 2016 Route deletion fallback to route.exe
Tue Jan 12 14:24:28 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\Sys tem32\Wbem
Tue Jan 12 14:24:28 2016 Closing TUN/TAP interface
Tue Jan 12 14:24:28 2016 SIGTERM[hard,] received, process exiting
Tue Jan 12 14:24:28 2016 MANAGEMENT: >STATE:1452605068,EXITING,SIGTERM,,