[Closed] Want to route traffic through my openvpn server

friedolin

I did:

sysctl -w net.ipv4.ip_forward=1
iptables -A FORWARD -o eth0 -i tun0 -s 192.168.161.0/24 -m conntrack --ctstate NEW -j ACCEPT
iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

serverconfig:


multihome

port 11194


proto udp


dev tun2



ca '/var/lib/zentyal/CA/cacert.pem'


cert '/var/lib/zentyal/CA/certs/0B38374B274FC0DA.pem'


key '/var/lib/zentyal/CA/private/vpn-server2.pem'

crl-verify /var/lib/zentyal/CA/crl/latest.pem


dh /etc/openvpn/ebox-dh1024.pem


server 192.168.161.0 255.255.255.0

ifconfig-pool-persist '/etc/openvpn/server2.d/server2-ipp.txt'


client-to-client
keepalive 10 120



comp-lzo


user nobody


group nogroup


persist-key
persist-tun


writepid /var/run/openvpn.server2.pid


status '/var/log/openvpn/status-server2.log'


log-append  '/var/log/openvpn/server2.log'

verb 3



push "redirect-gateway def1"
push "dhcp-option DNS 192.168.1.1"

client-config-dir /etc/openvpn/server2.d/client-config.d


push "route 192.168.1.0 255.255.255.0"

clientconfig:

client

dev tun

proto udp

remote  abc.de 11194
float

remote-random
resolv-retry infinite

nobind

persist-key
persist-tun


ca   "cacert.pem"
cert "0B38374B274FC0DE.pem"
key  "vpn-test.pem"

tls-remote vpn-server2

comp-lzo

verb 3

explicit-exit-notify 3

Connecting to the openvpnserver works.
I can surf in the internet before and after connecting.
But:
When I go to http://www.whatismyip.com/
Its before and after the same IP, even when I connect outside my LAN.

I want that when I'm connected to a hotspot outside, that all my traffic goes through my openvpn server.
My serverconfig can not totally be changed, because its generated by zentyal.

friedolin

both logs happend when connecting from LAN-PC to same LAN-Server, so extern IP would be the same. I could make my mobilephone to an accesspoint, and connect, if that would be wished.

Sometimes when connecting to one of my openvpn servers, the client tests routes and waits for routes, even if I log in as administrator. This only happens on my laptop with Win8.1 .Other PCs Win7 / opensuse don't have this problem. I have to retry several times, that this route testing or waiting does'nt happen.

server:

Sat Dec  7 14:13:11 2013 192.168.1.1:61465 TLS: Initial packet from [AF_INET]192.168.1.1:61465 (via [AF_INET]192.168.1.10%eth0), sid=7c3c2c4e aff58faf
Sat Dec  7 14:13:18 2013 192.168.1.1:61465 CRL CHECK OK: C=de, ST=Sachsen, L=Leipzig, O=alexserver, CN=Certification Authority Certificate
Sat Dec  7 14:13:18 2013 192.168.1.1:61465 VERIFY OK: depth=1, C=de, ST=Sachsen, L=Leipzig, O=alexserver, CN=Certification Authority Certificate
Sat Dec  7 14:13:18 2013 192.168.1.1:61465 CRL CHECK OK: C=de, ST=Sachsen, L=Leipzig, O=alexserver, CN=vpn-test
Sat Dec  7 14:13:18 2013 192.168.1.1:61465 VERIFY OK: depth=0, C=de, ST=Sachsen, L=Leipzig, O=alexserver, CN=vpn-test
Sat Dec  7 14:13:22 2013 192.168.1.1:61465 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Dec  7 14:13:22 2013 192.168.1.1:61465 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Dec  7 14:13:22 2013 192.168.1.1:61465 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Dec  7 14:13:22 2013 192.168.1.1:61465 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Dec  7 14:13:22 2013 192.168.1.1:61465 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sat Dec  7 14:13:22 2013 192.168.1.1:61465 [vpn-test] Peer Connection Initiated with [AF_INET]192.168.1.1:61465 (via [AF_INET]192.168.1.10%eth0)
Sat Dec  7 14:13:22 2013 vpn-test/192.168.1.1:61465 MULTI_sva: pool returned IPv4=192.168.161.14, IPv6=(Not enabled)
Sat Dec  7 14:13:22 2013 vpn-test/192.168.1.1:61465 MULTI: Learn: 192.168.161.14 -> vpn-test/192.168.1.1:61465
Sat Dec  7 14:13:22 2013 vpn-test/192.168.1.1:61465 MULTI: primary virtual IP for vpn-test/192.168.1.1:61465: 192.168.161.14
Sat Dec  7 14:13:24 2013 vpn-test/192.168.1.1:61465 PUSH: Received control message: 'PUSH_REQUEST'
Sat Dec  7 14:13:24 2013 vpn-test/192.168.1.1:61465 send_push_reply(): safe_cap=940
Sat Dec  7 14:13:24 2013 vpn-test/192.168.1.1:61465 SENT CONTROL [vpn-test]: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 192.168.1.1,route 192.168.1.0 255.255.255.0,route 192.168.161.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 192.168.161.14 192.168.161.13' (status=1)

client:

Sat Dec 07 14:13:10 2013 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013
Enter Management Password:
Sat Dec 07 14:13:10 2013 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25341
Sat Dec 07 14:13:10 2013 Need hold release from management interface, waiting...
Sat Dec 07 14:13:10 2013 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25341
Sat Dec 07 14:13:10 2013 MANAGEMENT: CMD 'state on'
Sat Dec 07 14:13:10 2013 MANAGEMENT: CMD 'log all on'
Sat Dec 07 14:13:10 2013 MANAGEMENT: CMD 'hold off'
Sat Dec 07 14:13:10 2013 MANAGEMENT: CMD 'hold release'
Sat Dec 07 14:13:11 2013 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sat Dec 07 14:13:11 2013 MANAGEMENT: >STATE:1386421991,RESOLVE,,,
Sat Dec 07 14:13:13 2013 UDPv4 link local: [undef]
Sat Dec 07 14:13:13 2013 UDPv4 link remote: [AF_INET]146.52.76.93:11194
Sat Dec 07 14:13:13 2013 MANAGEMENT: >STATE:1386421993,WAIT,,,
Sat Dec 07 14:13:13 2013 MANAGEMENT: >STATE:1386421993,AUTH,,,
Sat Dec 07 14:13:13 2013 TLS: Initial packet from [AF_INET]146.52.76.93:11194, sid=1049a5b9 9805d1f6
Sat Dec 07 14:13:13 2013 VERIFY OK: depth=1, /C=de/ST=Sachsen/L=Leipzig/O=alexserver/CN=Certification_Authority_Certificate
Sat Dec 07 14:13:13 2013 VERIFY X509NAME OK: /C=de/ST=Sachsen/L=Leipzig/O=alexserver/CN=vpn-server2
Sat Dec 07 14:13:13 2013 VERIFY OK: depth=0, /C=de/ST=Sachsen/L=Leipzig/O=alexserver/CN=vpn-server2
Sat Dec 07 14:13:24 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Dec 07 14:13:24 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Dec 07 14:13:24 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Dec 07 14:13:24 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Dec 07 14:13:24 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sat Dec 07 14:13:24 2013 [vpn-server2] Peer Connection Initiated with [AF_INET]146.52.76.93:11194
Sat Dec 07 14:13:25 2013 MANAGEMENT: >STATE:1386422005,GET_CONFIG,,,
Sat Dec 07 14:13:26 2013 SENT CONTROL [vpn-server2]: 'PUSH_REQUEST' (status=1)
Sat Dec 07 14:13:26 2013 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 192.168.1.1,route 192.168.1.0 255.255.255.0,route 192.168.161.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 192.168.161.14 192.168.161.13'
Sat Dec 07 14:13:26 2013 OPTIONS IMPORT: timers and/or timeouts modified
Sat Dec 07 14:13:26 2013 OPTIONS IMPORT: --ifconfig/up options modified
Sat Dec 07 14:13:26 2013 OPTIONS IMPORT: route options modified
Sat Dec 07 14:13:26 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Dec 07 14:13:26 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sat Dec 07 14:13:26 2013 MANAGEMENT: >STATE:1386422006,ASSIGN_IP,,192.168.161.14,
Sat Dec 07 14:13:26 2013 open_tun, tt->ipv6=0
Sat Dec 07 14:13:26 2013 TAP-WIN32 device [LAN-Verbindung] opened: \\.\Global\{14D1B0D0-39B1-4E35-8ABA-4D792A46EF0D}.tap
Sat Dec 07 14:13:26 2013 TAP-Windows Driver Version 9.9 
Sat Dec 07 14:13:26 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.161.14/255.255.255.252 on interface {14D1B0D0-39B1-4E35-8ABA-4D792A46EF0D} [DHCP-serv: 192.168.161.13, lease-time: 31536000]
Sat Dec 07 14:13:26 2013 Successful ARP Flush on interface [26] {14D1B0D0-39B1-4E35-8ABA-4D792A46EF0D}
Sat Dec 07 14:13:32 2013 TEST ROUTES: 3/3 succeeded len=2 ret=1 a=0 u/d=up
Sat Dec 07 14:13:32 2013 C:\WINDOWS\system32\route.exe ADD 146.52.76.93 MASK 255.255.255.255 192.168.1.1
Sat Dec 07 14:13:32 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sat Dec 07 14:13:32 2013 Route addition via IPAPI succeeded [adaptive]
Sat Dec 07 14:13:32 2013 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 192.168.161.13
Sat Dec 07 14:13:32 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sat Dec 07 14:13:32 2013 Route addition via IPAPI succeeded [adaptive]
Sat Dec 07 14:13:32 2013 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 192.168.161.13
Sat Dec 07 14:13:32 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sat Dec 07 14:13:32 2013 Route addition via IPAPI succeeded [adaptive]
Sat Dec 07 14:13:32 2013 MANAGEMENT: >STATE:1386422012,ADD_ROUTES,,,
Sat Dec 07 14:13:32 2013 C:\WINDOWS\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 192.168.161.13
Sat Dec 07 14:13:32 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sat Dec 07 14:13:32 2013 Route addition via IPAPI succeeded [adaptive]
Sat Dec 07 14:13:32 2013 C:\WINDOWS\system32\route.exe ADD 192.168.161.0 MASK 255.255.255.0 192.168.161.13
Sat Dec 07 14:13:33 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sat Dec 07 14:13:33 2013 Route addition via IPAPI succeeded [adaptive]
Sat Dec 07 14:13:33 2013 Initialization Sequence Completed
Sat Dec 07 14:13:33 2013 MANAGEMENT: >STATE:1386422013,CONNECTED,SUCCESS,192.168.161.14,146.52.76.93

friedolin

the client with that described problems:
logs before where when connected inside LAN, this is when connected via Mobilephone as Access Point.

Sat Dec 07 14:34:05 2013 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013
Enter Management Password:
Sat Dec 07 14:34:05 2013 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25341
Sat Dec 07 14:34:05 2013 Need hold release from management interface, waiting...
Sat Dec 07 14:34:05 2013 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25341
Sat Dec 07 14:34:05 2013 MANAGEMENT: CMD 'state on'
Sat Dec 07 14:34:05 2013 MANAGEMENT: CMD 'log all on'
Sat Dec 07 14:34:05 2013 MANAGEMENT: CMD 'hold off'
Sat Dec 07 14:34:05 2013 MANAGEMENT: CMD 'hold release'
Sat Dec 07 14:34:06 2013 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sat Dec 07 14:34:06 2013 MANAGEMENT: >STATE:1386423246,RESOLVE,,,
Sat Dec 07 14:34:06 2013 UDPv4 link local: [undef]
Sat Dec 07 14:34:06 2013 UDPv4 link remote: [AF_INET]146.52.76.93:11194
Sat Dec 07 14:34:06 2013 MANAGEMENT: >STATE:1386423246,WAIT,,,
Sat Dec 07 14:34:06 2013 MANAGEMENT: >STATE:1386423246,AUTH,,,
Sat Dec 07 14:34:06 2013 TLS: Initial packet from [AF_INET]146.52.76.93:11194, sid=e0d956c4 71151eac
Sat Dec 07 14:34:07 2013 VERIFY OK: depth=1, /C=de/ST=Sachsen/L=Leipzig/O=alexserver/CN=Certification_Authority_Certificate
Sat Dec 07 14:34:07 2013 VERIFY X509NAME OK: /C=de/ST=Sachsen/L=Leipzig/O=alexserver/CN=vpn-server2
Sat Dec 07 14:34:07 2013 VERIFY OK: depth=0, /C=de/ST=Sachsen/L=Leipzig/O=alexserver/CN=vpn-server2
Sat Dec 07 14:34:08 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Dec 07 14:34:08 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Dec 07 14:34:08 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Dec 07 14:34:08 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Dec 07 14:34:08 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sat Dec 07 14:34:08 2013 [vpn-server2] Peer Connection Initiated with [AF_INET]146.52.76.93:11194
Sat Dec 07 14:34:09 2013 MANAGEMENT: >STATE:1386423249,GET_CONFIG,,,
Sat Dec 07 14:34:10 2013 SENT CONTROL [vpn-server2]: 'PUSH_REQUEST' (status=1)
Sat Dec 07 14:34:14 2013 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 192.168.1.1,route 192.168.1.0 255.255.255.0,route 192.168.161.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 192.168.161.14 192.168.161.13'
Sat Dec 07 14:34:14 2013 OPTIONS IMPORT: timers and/or timeouts modified
Sat Dec 07 14:34:14 2013 OPTIONS IMPORT: --ifconfig/up options modified
Sat Dec 07 14:34:14 2013 OPTIONS IMPORT: route options modified
Sat Dec 07 14:34:14 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Dec 07 14:34:15 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sat Dec 07 14:34:15 2013 MANAGEMENT: >STATE:1386423255,ASSIGN_IP,,192.168.161.14,
Sat Dec 07 14:34:15 2013 open_tun, tt->ipv6=0
Sat Dec 07 14:34:15 2013 TAP-WIN32 device [LAN-Verbindung] opened: \\.\Global\{14D1B0D0-39B1-4E35-8ABA-4D792A46EF0D}.tap
Sat Dec 07 14:34:15 2013 TAP-Windows Driver Version 9.9 
Sat Dec 07 14:34:15 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 192.168.161.14/255.255.255.252 on interface {14D1B0D0-39B1-4E35-8ABA-4D792A46EF0D} [DHCP-serv: 192.168.161.13, lease-time: 31536000]
Sat Dec 07 14:34:15 2013 Successful ARP Flush on interface [26] {14D1B0D0-39B1-4E35-8ABA-4D792A46EF0D}
Sat Dec 07 14:34:20 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:20 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:25 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:25 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:26 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:26 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:28 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:28 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:29 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:29 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:30 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:30 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:31 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:31 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:33 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:33 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:34 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:34 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:36 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:36 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:37 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:37 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:38 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:38 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:39 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:39 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:40 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:40 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:42 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:42 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:43 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:43 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:44 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:44 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:45 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:45 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:47 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:47 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:48 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:48 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:49 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:49 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:51 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Dec 07 14:34:51 2013 C:\WINDOWS\system32\route.exe ADD 146.52.76.93 MASK 255.255.255.255 192.168.43.1
Sat Dec 07 14:34:51 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=25 and dwForwardType=4
Sat Dec 07 14:34:51 2013 Route addition via IPAPI succeeded [adaptive]
Sat Dec 07 14:34:51 2013 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 192.168.161.13
Sat Dec 07 14:34:51 2013 Warning: route gateway is not reachable on any active network adapters: 192.168.161.13
Sat Dec 07 14:34:51 2013 Route addition via IPAPI failed [adaptive]
Sat Dec 07 14:34:51 2013 Route addition fallback to route.exe
Sat Dec 07 14:34:51 2013 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sat Dec 07 14:34:51 2013 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 192.168.161.13
Sat Dec 07 14:34:51 2013 Warning: route gateway is not reachable on any active network adapters: 192.168.161.13
Sat Dec 07 14:34:51 2013 Route addition via IPAPI failed [adaptive]
Sat Dec 07 14:34:51 2013 Route addition fallback to route.exe
Sat Dec 07 14:34:51 2013 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sat Dec 07 14:34:51 2013 MANAGEMENT: >STATE:1386423291,ADD_ROUTES,,,
Sat Dec 07 14:34:51 2013 C:\WINDOWS\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 192.168.161.13
Sat Dec 07 14:34:51 2013 Warning: route gateway is not reachable on any active network adapters: 192.168.161.13
Sat Dec 07 14:34:51 2013 Route addition via IPAPI failed [adaptive]
Sat Dec 07 14:34:51 2013 Route addition fallback to route.exe
Sat Dec 07 14:34:51 2013 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sat Dec 07 14:34:51 2013 C:\WINDOWS\system32\route.exe ADD 192.168.161.0 MASK 255.255.255.0 192.168.161.13
Sat Dec 07 14:34:51 2013 Warning: route gateway is not reachable on any active network adapters: 192.168.161.13
Sat Dec 07 14:34:51 2013 Route addition via IPAPI failed [adaptive]
Sat Dec 07 14:34:51 2013 Route addition fallback to route.exe
Sat Dec 07 14:34:51 2013 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.43.1 p=0 i=3 t=4 pr=3 a=71 h=0 m=25/0/0/0/0
0.0.0.0 128.0.0.0 192.168.161.13 p=0 i=3 t=4 pr=3 a=1 h=0 m=26/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=157355 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=2 a=157355 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=2 a=157355 h=0 m=306/0/0/0/0
128.0.0.0 128.0.0.0 192.168.161.13 p=0 i=3 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
146.52.76.93 255.255.255.255 192.168.43.1 p=0 i=3 t=4 pr=3 a=1 h=0 m=25/0/0/0/0
192.168.1.0 255.255.255.0 192.168.161.13 p=0 i=3 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
192.168.43.0 255.255.255.0 192.168.43.166 p=0 i=3 t=3 pr=2 a=71 h=0 m=281/0/0/0/0
192.168.43.166 255.255.255.255 192.168.43.166 p=0 i=3 t=3 pr=2 a=71 h=0 m=281/0/0/0/0
192.168.43.255 255.255.255.255 192.168.43.166 p=0 i=3 t=3 pr=2 a=71 h=0 m=281/0/0/0/0
192.168.161.0 255.255.255.0 192.168.161.13 p=0 i=3 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=157355 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 192.168.43.166 p=0 i=3 t=3 pr=2 a=157344 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=157355 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 192.168.43.166 p=0 i=3 t=3 pr=2 a=157344 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Windows Adapter V9
  Index = 26
  GUID = {14D1B0D0-39B1-4E35-8ABA-4D792A46EF0D}
  IP = 0.0.0.0/0.0.0.0 
  MAC = 00:ff:14:d1:b0:d0
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV =  
  DHCP LEASE OBTAINED = Sat Dec 07 14:34:52 2013
  DHCP LEASE EXPIRES  = Sat Dec 07 14:34:52 2013
  DNS SERV =  
Virtueller Microsoft-Adapter für direktes WiFi
  Index = 16
  GUID = {595362E7-5A60-4D1E-B7D1-A35373E641AB}
  IP = 0.0.0.0/0.0.0.0 
  MAC = 92:4c:e5:24:07:55
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV =  
  DHCP LEASE OBTAINED = Sat Dec 07 14:34:52 2013
  DHCP LEASE EXPIRES  = Sat Dec 07 14:34:52 2013
  DNS SERV =  
Von Microsoft gehosteter, virtueller Netzwerkadapter
  Index = 15
  GUID = {FD3C29E4-1C8D-4231-8402-53D808DC9FC8}
  IP = 0.0.0.0/0.0.0.0 
  MAC = 90:4c:e5:24:07:55
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV =  
  DHCP LEASE OBTAINED = Sat Dec 07 14:34:52 2013
  DHCP LEASE EXPIRES  = Sat Dec 07 14:34:52 2013
  DNS SERV =  
Bluetooth-Gerät (PAN)
  Index = 6
  GUID = {5B180241-889C-448F-8583-1A3D7B20B467}
  IP = 0.0.0.0/0.0.0.0 
  MAC = 00:27:13:49:6c:ef
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV =  
  DHCP LEASE OBTAINED = Sat Dec 07 14:34:52 2013
  DHCP LEASE EXPIRES  = Sat Dec 07 14:34:52 2013
  DNS SERV =  
Marvell Yukon 88E8042-PCI-E-Fast-Ethernet-Controller
  Index = 4
  GUID = {49334CD9-C929-4598-B52D-F15B1D629015}
  IP = 0.0.0.0/0.0.0.0 
  MAC = 18:a9:05:ce:c9:50
  GATEWAY = 0.0.0.0/255.255.255.255 
  DHCP SERV =  
  DHCP LEASE OBTAINED = Sat Dec 07 14:34:52 2013
  DHCP LEASE EXPIRES  = Sat Dec 07 14:34:52 2013
  DNS SERV =  
Broadcom 802.11g-Netzwerkadapter
  Index = 3
  GUID = {9040DAAF-097B-4337-9007-2703DC7DBD67}
  IP = 192.168.43.166/255.255.255.0 
  MAC = 90:4c:e5:24:07:55
  GATEWAY = 192.168.43.1/255.255.255.255 
  DHCP SERV = 192.168.43.1/255.255.255.255 
  DHCP LEASE OBTAINED = Sat Dec 07 14:33:40 2013
  DHCP LEASE EXPIRES  = Sat Dec 07 15:33:40 2013
  DNS SERV = 192.168.43.1/255.255.255.255 
Sat Dec 07 14:34:52 2013 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Sat Dec 07 14:34:52 2013 MANAGEMENT: >STATE:1386423292,CONNECTED,ERROR,192.168.161.14,146.52.76.93
Sat Dec 07 14:35:10 2013 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #9 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

EDIT:

YES, I tried several times, that this problem with

Sat Dec 07 14:34:36 2013 Route: Waiting for TUN/TAP interface to come up...
Sat Dec 07 14:34:37 2013 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down

dont happen, and now my traffic is routed through the vpn.

It works!

friedolin

I have another question.

I want, that some clients have a static IP.
I googled for that, but I wonder why the server don't need to limit die Range for dhcp.

I mean:
In my router I can set dhcp for 192.168.3.100 - 192.168.3.254
So that I can make static IPs like 192.168.3.55 between 1 and 99.

Is that not needed for openvpn to limit the range of dhcp clients and static IP clients?

friedolin

When I use

ifconfig-push 10.8.1.1 10.8.1.2

then 10.8.1.1 will be the IP of the client.
But why do I need to set 10.8.1.2 for the server?
Is'nt the server IP set already in den server config file?

someone at a dfiferent place in the internet wrote

and on the HowTo you find an example

ccd/sysadmin1

ifconfig-push 10.8.1.1 10.8.1.2

which gives the client address 10.8.1.1 and the server end
of the tunnel 10.8.1.2

But I dont understand what is meant with "and the server end
of the tunnel "

Has the server more than one openvpn-IP (tun)?

Openvpn manpage:

--ifconfig-push local remote-netmask

but is'nt a netmask this:?
255.255.255.0 ? oder /24 ?