Posted: Sat Dec 27, 2014 15:32 Post subject: Probleme mit nvpn auf TP-Link TL-WR1043ND V2
Hallo,
ich habe auf meinem TP-Link Router folgende firmware drauf und bekomme nvpn dort nicht zum rennen: DD-WRT v24-sp2 (12/22/14) std - build 25697
Bei login am PC mit openvpn ist alles perfekt und ich erhalte diesen log:
Code:
Sat Dec 27 16:05:31 2014 OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Dec 15 2011
Sat Dec 27 16:05:44 2014 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sat Dec 27 16:05:44 2014 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sat Dec 27 16:05:44 2014 LZO compression initialized
Sat Dec 27 16:05:44 2014 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
Sat Dec 27 16:05:44 2014 Socket Buffers: R=[8192->8192] S=[8192->8192]
Sat Dec 27 16:05:45 2014 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Sat Dec 27 16:05:45 2014 Local Options hash (VER=V4): '41690919'
Sat Dec 27 16:05:45 2014 Expected Remote Options hash (VER=V4): '530fdded'
Sat Dec 27 16:05:45 2014 UDPv4 link local: [undef]
Sat Dec 27 16:05:45 2014 UDPv4 link remote: xxx.x.xxx.xxx:1194
Sat Dec 27 16:05:45 2014 TLS: Initial packet from xxx.x.xxx.xxx:1194, sid=f3249868 35a18f75
Sat Dec 27 16:05:45 2014 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sat Dec 27 16:05:50 2014 VERIFY OK: depth=1, /C=NV/ST=NV/L=nVPN/O=nVpn/CN=nVpn_CA/emailAddress=support@nvpn.net
Sat Dec 27 16:05:50 2014 VERIFY OK: depth=0, /C=NV/ST=NV/L=nVPN/O=nVpn/CN=server/emailAddress=support@nvpn.net
Sat Dec 27 16:05:51 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Dec 27 16:05:51 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Dec 27 16:05:51 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Dec 27 16:05:51 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Dec 27 16:05:51 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sat Dec 27 16:05:51 2014 [server] Peer Connection Initiated with xxx.x.xxx.xxx:1194
Sat Dec 27 16:05:53 2014 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Sat Dec 27 16:05:57 2014 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route xx.xxx.xxx.x,topology net30,ping 10,ping-restart 120,ifconfig xx.xxx.xxx.xx xx.xxx.xxx.x'
Sat Dec 27 16:05:57 2014 OPTIONS IMPORT: timers and/or timeouts modified
Sat Dec 27 16:05:57 2014 OPTIONS IMPORT: --ifconfig/up options modified
Sat Dec 27 16:05:57 2014 OPTIONS IMPORT: route options modified
Sat Dec 27 16:05:57 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Dec 27 16:05:57 2014 ROUTE default_gateway=192.168.178.1
Sat Dec 27 16:05:57 2014 TAP-WIN32 device [LAN-Verbindung 2] opened: \\.\Global\{B9CAB2A4-5A87-4042-82AB-796DAE5D9E43}.tap
Sat Dec 27 16:05:57 2014 TAP-Win32 Driver Version 9.9
Sat Dec 27 16:05:57 2014 TAP-Win32 MTU=1500
Sat Dec 27 16:05:57 2014 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.175.230.10/255.255.255.252 on interface {B9CAB2A4-5A87-4042-82AB-796DAE5D9E43} [DHCP-serv: xx.xxx.xxx.x, lease-time: 31536000]
Sat Dec 27 16:05:57 2014 Successful ARP Flush on interface [28] {B9CAB2A4-5A87-4042-82AB-796DAE5D9E43}
Sat Dec 27 16:06:02 2014 TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up
Sat Dec 27 16:06:02 2014 C:\WINDOWS\system32\route.exe ADD xxx.x.xxx.xxx MASK 255.255.255.255 192.168.178.1
Sat Dec 27 16:06:02 2014 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=10 and dwForwardType=4
Sat Dec 27 16:06:02 2014 Route addition via IPAPI succeeded [adaptive]
Sat Dec 27 16:06:02 2014 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 xx.xxx.xxx.x
Sat Dec 27 16:06:02 2014 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sat Dec 27 16:06:02 2014 Route addition via IPAPI succeeded [adaptive]
Sat Dec 27 16:06:02 2014 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 xx.xxx.xxx.x
Sat Dec 27 16:06:02 2014 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sat Dec 27 16:06:02 2014 Route addition via IPAPI succeeded [adaptive]
Sat Dec 27 16:06:02 2014 C:\WINDOWS\system32\route.exe ADD 10.175.230.1 MASK 255.255.255.255 xx.xxx.xxx.x
Sat Dec 27 16:06:02 2014 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sat Dec 27 16:06:02 2014 Route addition via IPAPI succeeded [adaptive]
Sat Dec 27 16:06:02 2014 Initialization Sequence Completed
Sat Dec 27 15:51:15 2014 OpenVPN 2.3.6 mips-unknown-linux-gnu [SSL (OpenSSL)] [L
Sat Dec 27 15:51:15 2014 library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.08
Sat Dec 27 15:51:15 2014 WARNING: file '/tmp/nvpn/auth.txt' is group or others a
Sat Dec 27 15:51:15 2014 WARNING: No server certificate verification method has
Sat Dec 27 15:51:15 2014 NOTE: starting with OpenVPN 2.1, '--script-security 2'
Sat Dec 27 15:51:16 2014 UDPv4 link local: [undef]
Sat Dec 27 15:51:16 2014 UDPv4 link remote: [AF_INET]xxx.x.xxx.xxx:1194
Sat Dec 27 15:51:16 2014 WARNING: this configuration may cache passwords in memo
Sat Dec 27 15:51:22 2014 [server] Peer Connection Initiated with [AF_INET]185.5.
Sat Dec 27 15:51:24 2014 TUN/TAP device tun0 opened
Sat Dec 27 15:51:24 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sat Dec 27 15:51:24 2014 /sbin/ifconfig tun0 xx.xxx.xxx.xx pointopoint xx.xxx.xx
Sat Dec 27 15:51:24 2014 WARNING: External program may not be called unless '--s
Sat Dec 27 15:51:24 2014 WARNING: Failed running command (--route-up): external
Sat Dec 27 15:51:24 2014 Initialization Sequence Completed
Was habe ich falsch gemacht, dass die direkt am Router angeschlossenen Geräte nicht über nvpn laufen?
Versuch macht kluch.......
Ich habe es hinbekommen, mein Fehler war, dass der Zweitrouter im Modus Router und nicht als gateway gelaufen war. Mit dieser Einstellung und anderem IP Bereich geht nun alles, wie es soll.
Mit dieser Einstellung und anderem IP Bereich geht nun alles, wie es soll.
Anderer IP-Bereich ist gar nicht nötig - Du kannst ruhig beide Router in einem Netz lassen
Angenommen, dein DSL-Router hat die 192.168.1.1 und der DD-WRT die 192.168.1.2, sieht das so aus :
Wenn Du dann über VPN ins Netz willst, nimmst Du die 192.168.1.2 und um direkt rein zu gehen die 192.168.1.1
Z.B. bei meinem TV hab ich die 2 drin, damit die Youtube-App nicht ständig nur Gema-Warnungen zeigt - normales surfen am PC läuft über die 1, das VPN ist ja doch nicht ganz so schnell wie die Inet-Leitung an sich
