Ich besitze einen gefreetzten Speedport W701v und betreibe OpenVPN im tap Modus. Hier die Config des Servers:
Hier ist die Config des XP-Clients:
Die Verbindung kommt problemlos zwischen Server und Client zustande. Hier der Log:
Mein Problem besteht allerdings darin, dass ich weder den Server, noch den Client anpingen kann. Ein Ping vom Client an 192.168.200.1 ist nicht möglich. Vom Server an 192.168.200.100 funktioniert ebenso nicht.
Ich bin ein wenig ratlos. Kann mir hier jemand einen Tipp geben?
Code:
proto tcp-server
dev tap
ca /tmp/flash/ca.crt
cert /tmp/flash/box.crt
key /tmp/flash/box.key
dh /tmp/flash/dh.pem
tls-server
tls-auth /tmp/flash/static.key 0
port 1194
mode server
ifconfig-pool 192.168.200.100 192.168.200.150
push "route 192.168.200.0 255.255.255.0"
push "route-gateway 192.168.200.1 "
ifconfig 192.168.200.1 255.255.255.0
push "route-gateway 192.168.200.1"
push "route 192.168.178.0 255.255.255.0"
max-clients 5
tun-mtu 1500
mssfix
verb 3
daemon
cipher AES-128-CBC
comp-lzo
keepalive 10 120Hier ist die Config des XP-Clients:
Code:
remote server 11194
proto tcp-client
dev tap
tls-client
ns-cert-type server
ca "C:\\Programme\\OpenVPN\\keys\\ca.crt"
cert "C:\\Programme\\OpenVPN\\keys\\client2.crt"
key "C:\\Programme\\OpenVPN\\keys\\client2.key"
tls-auth "C:\\Programme\\OpenVPN\\keys\\static.key" 1
tun-mtu 1500
mssfix
nobind
comp-lzo
cipher AES-128-CBC
pull
verb 3Die Verbindung kommt problemlos zwischen Server und Client zustande. Hier der Log:
Code:
Wed Apr 15 14:22:30 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Oct 1 2006
Wed Apr 15 14:22:30 2009 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Wed Apr 15 14:22:30 2009 Control Channel Authentication: using 'C:\Programme\OpenVPN\keys\static.key' as a OpenVPN static key file
Wed Apr 15 14:22:30 2009 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 15 14:22:30 2009 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 15 14:22:30 2009 LZO compression initialized
Wed Apr 15 14:22:30 2009 Control Channel MTU parms [ L:1592 D:168 EF:68 EB:0 ET:0 EL:0 ]
Wed Apr 15 14:22:30 2009 Data Channel MTU parms [ L:1592 D:1450 EF:60 EB:135 ET:32 EL:0 AF:3/1 ]
Wed Apr 15 14:22:30 2009 Local Options hash (VER=V4): '29f6c8b2'
Wed Apr 15 14:22:30 2009 Expected Remote Options hash (VER=V4): '3d4363c6'
Wed Apr 15 14:22:30 2009 Attempting to establish TCP connection with 127.0.0.1:11194
Wed Apr 15 14:22:30 2009 TCP connection established with 127.0.0.1:11194
Wed Apr 15 14:22:30 2009 TCPv4_CLIENT link local: [undef]
Wed Apr 15 14:22:30 2009 TCPv4_CLIENT link remote: 127.0.0.1:11194
Wed Apr 15 14:22:30 2009 TLS: Initial packet from 127.0.0.1:11194, sid=e2d1d45e 128aaecb
Wed Apr 15 14:22:32 2009 VERIFY OK: nsCertType=SERVER
Wed Apr 15 14:22:35 2009 Data Channel Encrypt: Cipher 'AES-128-CBC' initialized with 128 bit key
Wed Apr 15 14:22:35 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 15 14:22:35 2009 Data Channel Decrypt: Cipher 'AES-128-CBC' initialized with 128 bit key
Wed Apr 15 14:22:35 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Apr 15 14:22:35 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Apr 15 14:22:35 2009 [server.no-ip-org] Peer Connection Initiated with 127.0.0.1:11194
Wed Apr 15 14:22:36 2009 SENT CONTROL [server.no-ip-org]: 'PUSH_REQUEST' (status=1)
Wed Apr 15 14:22:37 2009 PUSH: Received control message: 'PUSH_REPLY,route 192.168.200.0 255.255.255.0,route-gateway 192.168.200.1 ,route-gateway 192.168.200.1,route 192.168.178.0 255.255.255.0,ping 10,ping-restart 120,ifconfig 192.168.200.100 255.255.255.0'
Wed Apr 15 14:22:37 2009 OPTIONS IMPORT: timers and/or timeouts modified
Wed Apr 15 14:22:37 2009 OPTIONS IMPORT: --ifconfig/up options modified
Wed Apr 15 14:22:37 2009 OPTIONS IMPORT: route options modified
Wed Apr 15 14:22:37 2009 TAP-WIN32 device [LAN-Verbindung 3] opened: \\.\Global\{F85D9F28-842B-4694-99B8-06BBBA44C95E}.tap
Wed Apr 15 14:22:37 2009 TAP-Win32 Driver Version 8.4
Wed Apr 15 14:22:37 2009 TAP-Win32 MTU=1500
Wed Apr 15 14:22:37 2009 Notified TAP-Win32 driver to set a DHCP IP/netmask of 192.168.200.100/255.255.255.0 on interface {F85D9F28-842B-4694-99B8-06BBBA44C95E} [DHCP-serv: 192.168.200.0, lease-time: 31536000]
Wed Apr 15 14:22:37 2009 Successful ARP Flush on interface [2] {F85D9F28-842B-4694-99B8-06BBBA44C95E}
Wed Apr 15 14:22:37 2009 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Wed Apr 15 14:22:37 2009 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 15 14:22:38 2009 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Wed Apr 15 14:22:38 2009 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 15 14:22:39 2009 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Wed Apr 15 14:22:39 2009 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 15 14:22:41 2009 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Wed Apr 15 14:22:41 2009 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 15 14:22:42 2009 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Wed Apr 15 14:22:42 2009 Route: Waiting for TUN/TAP interface to come up...
Wed Apr 15 14:22:42 2009 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Wed Apr 15 14:22:42 2009 route ADD 192.168.200.0 MASK 255.255.255.0 192.168.200.1
Wed Apr 15 14:22:43 2009 Route addition via IPAPI succeeded
Wed Apr 15 14:22:43 2009 route ADD 192.168.178.0 MASK 255.255.255.0 192.168.200.1
Wed Apr 15 14:22:43 2009 Route addition via IPAPI succeeded
Wed Apr 15 14:22:43 2009 Initialization Sequence CompletedMein Problem besteht allerdings darin, dass ich weder den Server, noch den Client anpingen kann. Ein Ping vom Client an 192.168.200.1 ist nicht möglich. Vom Server an 192.168.200.100 funktioniert ebenso nicht.
Ich bin ein wenig ratlos. Kann mir hier jemand einen Tipp geben?
