OpenVPN - establishes connection but cannot access local net

barney_5uk

Until recently OpenVPN was working well. Since yesterday, there is a issue with connectivity within the private network. The OpenVPN connection is established, but the resources in the private network are inaccessable and without connectivity through the OpenVPN.
- this all worked well until yesterday
- there was no change in the network since this did not work anymore
- it looks like the routes are added as needed by OpenVPN but the resources in the private network still cannot get accessed from the OpenVPN connection.

I suspect this issue as a routing problem, however I have no idea what might wrong - as it is to be seen in the log from the established OpenVPN connection it looks like the routes are all created as they are needed.

The environment is Windows 2003 where the OpenVPN server is installed,
- there is also no internal Firewall established (the Firewall blocks external traffic but opens the port for OpenVPN - otherwise there wouldn't be the connection established at all).
- and the server (where also OpenVPN server is installed) connects external to internal (192.168.1.xxx) with 2 network cards with NAT enabled and the Firewall applied to the external connection.

192.168.1.xxx is the internal, private network while 10.8.0.xxx is the OpenVPN virtual network as created by default. It is, however, to note that the connected client gets "10.8.0.29" as his gateway where I think this should be 10.8.0.1 ?

Is there any idea what might be wrong ?

Kind Regards for any help

Bernard

server.ovpn
================
port 1194
proto udp
replay-window 64 60
dev tun
ca C:\\Programme\\OpenVPN\\easy-rsa\\keys\\ca.crt
cert C:\\Programme\\OpenVPN\\easy-rsa\\keys\\server1.crt
key C:\\Programme\\OpenVPN\\easy-rsa\\keys\\server1.key # This file should be kept secret
dh C:\\Programme\\OpenVPN\\easy-rsa\\keys\\dh1024.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 192.168.1.0 255.255.255.0"
push "dhcp-option DNS 192.168.1.115"
client-to-client
keepalive 10 120
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 3
route-method exe

The log from the established OpenVPN connection looks successfull
=================================================
Thu Jan 02 16:19:13 2014 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013
Thu Jan 02 16:19:13 2014 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Thu Jan 02 16:19:13 2014 Need hold release from management interface, waiting...
Thu Jan 02 16:19:13 2014 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Thu Jan 02 16:19:13 2014 MANAGEMENT: CMD 'state on'
Thu Jan 02 16:19:13 2014 MANAGEMENT: CMD 'log all on'
Thu Jan 02 16:19:13 2014 MANAGEMENT: CMD 'hold off'
Thu Jan 02 16:19:13 2014 MANAGEMENT: CMD 'hold release'
Thu Jan 02 16:19:13 2014 Socket Buffers: R=[8192->8192] S=[8192->8192]
Thu Jan 02 16:19:13 2014 MANAGEMENT: >STATE:1388675953,RESOLVE,,,
Thu Jan 02 16:19:13 2014 UDPv4 link local: [undef]
Thu Jan 02 16:19:13 2014 UDPv4 link remote: [AF_INET]70.50.200.115:1194
Thu Jan 02 16:19:13 2014 MANAGEMENT: >STATE:1388675953,WAIT,,,
Thu Jan 02 16:19:14 2014 MANAGEMENT: >STATE:1388675954,AUTH,,,
Thu Jan 02 16:19:14 2014 TLS: Initial packet from [AF_INET]70.50.200.115:1194, sid=144db412 0e5f81fb
Thu Jan 02 16:19:14 2014 VERIFY OK: depth=1, C=CY, ST=ST, L=Location, O=organization, OU=ca, CN=ca, emailAddress=email@organization.com
Thu Jan 02 16:19:14 2014 VERIFY OK: nsCertType=SERVER
Thu Jan 02 16:19:14 2014 VERIFY OK: depth=0, C=CY, ST=ST, L=Location, O=organization, OU=ca, CN=ca, emailAddress=email@organization.com
Thu Jan 02 16:19:14 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Jan 02 16:19:14 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jan 02 16:19:14 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Jan 02 16:19:14 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jan 02 16:19:14 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Thu Jan 02 16:19:14 2014 [server1] Peer Connection Initiated with [AF_INET]78.52.209.110:1194
Thu Jan 02 16:19:15 2014 MANAGEMENT: >STATE:1388675955,GET_CONFIG,,,
Thu Jan 02 16:19:16 2014 SENT CONTROL [server1]: 'PUSH_REQUEST' (status=1)
Thu Jan 02 16:19:17 2014 PUSH: Received control message: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,dhcp-option DNS 192.168.1.115,route 10.8.0.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.30 10.8.0.29'
Thu Jan 02 16:19:17 2014 OPTIONS IMPORT: timers and/or timeouts modified
Thu Jan 02 16:19:17 2014 OPTIONS IMPORT: --ifconfig/up options modified
Thu Jan 02 16:19:17 2014 OPTIONS IMPORT: route options modified
Thu Jan 02 16:19:17 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Jan 02 16:19:17 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Thu Jan 02 16:19:17 2014 MANAGEMENT: >STATE:1388675957,ASSIGN_IP,,10.8.0.30,
Thu Jan 02 16:19:17 2014 open_tun, tt->ipv6=0
Thu Jan 02 16:19:17 2014 TAP-WIN32 device [LAN-Verbindung 9] opened: \\.\Global\{08B52A79-29A1-44CE-9996-38C98412FF4F}.tap
Thu Jan 02 16:19:17 2014 TAP-Windows Driver Version 9.9
Thu Jan 02 16:19:17 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.30/255.255.255.252 on interface {08B52A79-29A1-44CE-9996-38C98412FF4F} [DHCP-serv: 10.8.0.29, lease-time: 31536000]
Thu Jan 02 16:19:17 2014 Successful ARP Flush on interface [5] {08B52A79-29A1-44CE-9996-38C98412FF4F}
Thu Jan 02 16:19:22 2014 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Thu Jan 02 16:19:22 2014 MANAGEMENT: >STATE:1388675962,ADD_ROUTES,,,
Thu Jan 02 16:19:22 2014 C:\WINDOWS\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 10.8.0.29
Thu Jan 02 16:19:22 2014 Route addition via IPAPI succeeded [adaptive]
Thu Jan 02 16:19:22 2014 C:\WINDOWS\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.29
Thu Jan 02 16:19:22 2014 Route addition via IPAPI succeeded [adaptive]
Thu Jan 02 16:19:22 2014 Initialization Sequence Completed
Thu Jan 02 16:19:22 2014 MANAGEMENT: >STATE:1388675962,CONNECTED,SUCCESS,10.8.0.30,70.50.200.115

and the added routes are established ("Active Routes")
===========================================================================
Aktive Routen:
Netzwerkziel Netzwerkmaske Gateway Schnittstelle Anzahl
0.0.0.0 0.0.0.0 192.168.1.2 192.168.1.89 25
10.8.0.0 255.255.255.0 10.8.0.29 10.8.0.30 1
10.8.0.28 255.255.255.252 10.8.0.30 10.8.0.30 30
10.8.0.30 255.255.255.255 127.0.0.1 127.0.0.1 30
10.255.255.255 255.255.255.255 10.8.0.30 10.8.0.30 30
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
169.254.0.0 255.255.0.0 192.168.1.89 192.168.1.89 20
192.168.1.0 255.255.255.0 192.168.1.89 192.168.1.89 25
192.168.1.0 255.255.255.0 10.8.0.29 10.8.0.30 1
192.168.1.89 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.1.255 255.255.255.255 192.168.1.89 192.168.1.89 25
224.0.0.0 240.0.0.0 10.8.0.30 10.8.0.30 30
224.0.0.0 240.0.0.0 192.168.1.89 192.168.1.89 25
255.255.255.255 255.255.255.255 10.8.0.30 4 1
255.255.255.255 255.255.255.255 10.8.0.30 2 1
255.255.255.255 255.255.255.255 10.8.0.30 10.8.0.30 1
255.255.255.255 255.255.255.255 192.168.1.89 192.168.1.89 1
Standardgateway: 192.168.1.2
===========================================================================

barney_5uk

Thanks. I will try this and report within the next minutes.

The Client configuration is as follows below. What also might be of note, all of that worked until recently. The connectivity issue probably appeared after a client which was connected remotely received from DHCP erratically the same IP adress as another device in the network had (that device was configured manually and I changed that devices' IP adress after that incident).
What is also to note are the log files from the connections - a connection which is not working includes the line
NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address LAN-Verbindung 9 dhcp
in the log, while a connection log from a working connection which was made in the past does not contain that line. ("Lan Verbindung 9" is the OpenVPN TAP adaptor).

Client configuration:
---------------------------------------------------
remote organization.dyndns.org 1194
client
dev tun
proto udp
replay-window 64 60
resolv-retry infinite
persist-key
persist-tun
ca C:\\Programme\\OpenVPN\\config\\ca.crt
cert C:\\Programme\\OpenVPN\\config\\client.crt
key C:\\Programme\\OpenVPN\\config\\client.key
nobind
ns-cert-type server
comp-lzo
verb 3

Client log from a not working connection
----------------------------------------------------
Tue Jan 07 09:26:03 2014 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013
Tue Jan 07 09:26:03 2014 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25341
Tue Jan 07 09:26:03 2014 Need hold release from management interface, waiting...
Tue Jan 07 09:26:04 2014 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25341
Tue Jan 07 09:26:04 2014 MANAGEMENT: CMD 'state on'
Tue Jan 07 09:26:04 2014 MANAGEMENT: CMD 'log all on'
Tue Jan 07 09:26:04 2014 MANAGEMENT: CMD 'hold off'
Tue Jan 07 09:26:04 2014 MANAGEMENT: CMD 'hold release'
Tue Jan 07 09:26:04 2014 Socket Buffers: R=[8192->8192] S=[8192->8192]
Tue Jan 07 09:26:04 2014 MANAGEMENT: >STATE:1389083164,RESOLVE,,,
Tue Jan 07 09:26:04 2014 UDPv4 link local: [undef]
Tue Jan 07 09:26:04 2014 UDPv4 link remote: [AF_INET]92.226.140.134:1194
Tue Jan 07 09:26:04 2014 MANAGEMENT: >STATE:1389083164,WAIT,,,
Tue Jan 07 09:26:04 2014 MANAGEMENT: >STATE:1389083164,AUTH,,,
Tue Jan 07 09:26:04 2014 TLS: Initial packet from [AF_INET]92.226.140.134:1194, sid=9efce134 c3a382d7
Tue Jan 07 09:26:04 2014 VERIFY OK: depth=1, C=CY ST=ST, L=Location, O=comlogos, OU=ca, CN=ca, emailAddress=mail@organization.com
Tue Jan 07 09:26:04 2014 VERIFY OK: nsCertType=SERVER
Tue Jan 07 09:26:04 2014 VERIFY OK: depth=0, C=CY, ST=ST, O=organization, OU=server, CN=server, emailAddress=mail@organization.com
Tue Jan 07 09:26:04 2014 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 07 09:26:04 2014 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 07 09:26:04 2014 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Tue Jan 07 09:26:04 2014 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Jan 07 09:26:04 2014 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Tue Jan 07 09:26:04 2014 [server1] Peer Connection Initiated with [AF_INET]92.226.140.134:1194
Tue Jan 07 09:26:05 2014 MANAGEMENT: >STATE:1389083165,GET_CONFIG,,,
Tue Jan 07 09:26:06 2014 SENT CONTROL [server1]: 'PUSH_REQUEST' (status=1)
Tue Jan 07 09:26:06 2014 PUSH: Received control message: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,dhcp-option DNS 192.168.1.115,route 10.8.0.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.34 10.8.0.33'
Tue Jan 07 09:26:06 2014 OPTIONS IMPORT: timers and/or timeouts modified
Tue Jan 07 09:26:06 2014 OPTIONS IMPORT: --ifconfig/up options modified
Tue Jan 07 09:26:06 2014 OPTIONS IMPORT: route options modified
Tue Jan 07 09:26:06 2014 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Tue Jan 07 09:26:06 2014 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Tue Jan 07 09:26:06 2014 MANAGEMENT: >STATE:1389083166,ASSIGN_IP,,10.8.0.34,
Tue Jan 07 09:26:06 2014 open_tun, tt->ipv6=0
Tue Jan 07 09:26:06 2014 TAP-WIN32 device [LAN-Verbindung 9] opened: \\.\Global\{08B52A79-29A1-44CE-9996-38C98412FF4F}.tap
Tue Jan 07 09:26:06 2014 TAP-Windows Driver Version 9.9
Tue Jan 07 09:26:07 2014 NETSH: C:\WINDOWS\system32\netsh.exe interface ip set address LAN-Verbindung 9 dhcp
Tue Jan 07 09:26:11 2014 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.34/255.255.255.252 on interface {08B52A79-29A1-44CE-9996-38C98412FF4F} [DHCP-serv: 10.8.0.33, lease-time: 31536000]
Tue Jan 07 09:26:11 2014 Successful ARP Flush on interface [5] {08B52A79-29A1-44CE-9996-38C98412FF4F}
Tue Jan 07 09:26:16 2014 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 07 09:26:16 2014 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 07 09:26:22 2014 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 07 09:26:22 2014 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 07 09:26:23 2014 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Tue Jan 07 09:26:23 2014 Route: Waiting for TUN/TAP interface to come up...
Tue Jan 07 09:26:24 2014 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Tue Jan 07 09:26:24 2014 MANAGEMENT: >STATE:1389083184,ADD_ROUTES,,,
Tue Jan 07 09:26:24 2014 C:\WINDOWS\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 10.8.0.33
Tue Jan 07 09:26:24 2014 Route addition via IPAPI succeeded [adaptive]
Tue Jan 07 09:26:24 2014 C:\WINDOWS\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.33
Tue Jan 07 09:26:24 2014 Route addition via IPAPI succeeded [adaptive]
Tue Jan 07 09:26:24 2014 Initialization Sequence Completed
Tue Jan 07 09:26:24 2014 MANAGEMENT: >STATE:1389083184,CONNECTED,SUCCESS,10.8.0.34,92.226.140.134

Client log from a connection as it worked until 2 weeks before
-----------------------------------------------------------------------------
Thu Dec 12 08:35:10 2013 OpenVPN 2.3.2 i686-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Aug 22 2013
Enter Management Password:
Thu Dec 12 08:35:10 2013 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Thu Dec 12 08:35:10 2013 Need hold release from management interface, waiting...
Thu Dec 12 08:35:10 2013 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Thu Dec 12 08:35:10 2013 MANAGEMENT: CMD 'state on'
Thu Dec 12 08:35:10 2013 MANAGEMENT: CMD 'log all on'
Thu Dec 12 08:35:10 2013 MANAGEMENT: CMD 'hold off'
Thu Dec 12 08:35:10 2013 MANAGEMENT: CMD 'hold release'
Thu Dec 12 08:35:10 2013 Socket Buffers: R=[65536->65536] S=[65536->65536]
Thu Dec 12 08:35:10 2013 MANAGEMENT: >STATE:1386833710,RESOLVE,,,
Thu Dec 12 08:35:10 2013 UDPv4 link local: [undef]
Thu Dec 12 08:35:10 2013 UDPv4 link remote: [AF_INET]92.227.23.209:1194
Thu Dec 12 08:35:10 2013 MANAGEMENT: >STATE:1386833710,WAIT,,,
Thu Dec 12 08:35:10 2013 MANAGEMENT: >STATE:1386833710,AUTH,,,
Thu Dec 12 08:35:10 2013 TLS: Initial packet from [AF_INET]92.227.23.209:1194, sid=2fabca22 2821f6c0
Thu Dec 12 08:35:10 2013 VERIFY OK: depth=1, C=CY, ST=ST, L=Location, O=organization, OU=ca, CN=ca, emailAddress=mail@organization.com
Thu Dec 12 08:35:10 2013 VERIFY OK: nsCertType=SERVER
Thu Dec 12 08:35:10 2013 VERIFY OK: depth=0, C=CY, ST=ST, O=organization, OU=server, CN=server, emailAddress=mail@organization.com
Thu Dec 12 08:35:10 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Dec 12 08:35:10 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Dec 12 08:35:10 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Dec 12 08:35:10 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Dec 12 08:35:10 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Thu Dec 12 08:35:10 2013 [server1] Peer Connection Initiated with [AF_INET]92.227.23.209:1194
Thu Dec 12 08:35:11 2013 MANAGEMENT: >STATE:1386833711,GET_CONFIG,,,
Thu Dec 12 08:35:13 2013 SENT CONTROL [server1]: 'PUSH_REQUEST' (status=1)
Thu Dec 12 08:35:13 2013 PUSH: Received control message: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,dhcp-option DNS 192.168.1.115,route 10.8.0.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.42 10.8.0.41'
Thu Dec 12 08:35:13 2013 OPTIONS IMPORT: timers and/or timeouts modified
Thu Dec 12 08:35:13 2013 OPTIONS IMPORT: --ifconfig/up options modified
Thu Dec 12 08:35:13 2013 OPTIONS IMPORT: route options modified
Thu Dec 12 08:35:13 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Dec 12 08:35:13 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Thu Dec 12 08:35:13 2013 MANAGEMENT: >STATE:1386833713,ASSIGN_IP,,10.8.0.42,
Thu Dec 12 08:35:13 2013 open_tun, tt->ipv6=0
Thu Dec 12 08:35:13 2013 TAP-WIN32 device [LAN-Verbindung] opened: \\.\Global\{6AFB1ECF-C518-4E9A-84CB-924378DB8951}.tap
Thu Dec 12 08:35:13 2013 TAP-Windows Driver Version 9.9
Thu Dec 12 08:35:13 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.42/255.255.255.252 on interface {6AFB1ECF-C518-4E9A-84CB-924378DB8951} [DHCP-serv: 10.8.0.41, lease-time: 31536000]
Thu Dec 12 08:35:13 2013 Successful ARP Flush on interface [18] {6AFB1ECF-C518-4E9A-84CB-924378DB8951}
Thu Dec 12 08:35:18 2013 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Thu Dec 12 08:35:18 2013 MANAGEMENT: >STATE:1386833718,ADD_ROUTES,,,
Thu Dec 12 08:35:18 2013 C:\WINDOWS\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 10.8.0.41
Thu Dec 12 08:35:18 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Thu Dec 12 08:35:18 2013 Route addition via IPAPI succeeded [adaptive]
Thu Dec 12 08:35:18 2013 C:\WINDOWS\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.41
Thu Dec 12 08:35:18 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Thu Dec 12 08:35:18 2013 Route addition via IPAPI succeeded [adaptive]
Thu Dec 12 08:35:18 2013 Initialization Sequence Completed
Thu Dec 12 08:35:18 2013 MANAGEMENT: >STATE:1386833718,CONNECTED,SUCCESS,10.8.0.42,92.227.23.209
Thu Dec 12 08:35:24 2013 C:\WINDOWS\system32\route.exe DELETE 10.8.0.0 MASK 255.255.255.0 10.8.0.41
Thu Dec 12 08:35:24 2013 Route deletion via IPAPI succeeded [adaptive]
Thu Dec 12 08:35:24 2013 C:\WINDOWS\system32\route.exe DELETE 192.168.1.0 MASK 255.255.255.0 10.8.0.41
Thu Dec 12 08:35:24 2013 Route deletion via IPAPI succeeded [adaptive]
Thu Dec 12 08:35:24 2013 Closing TUN/TAP interface
Thu Dec 12 08:35:24 2013 SIGTERM[hard,] received, process exiting
Thu Dec 12 08:35:24 2013 MANAGEMENT: >STATE:1386833724,EXITING,SIGTERM,,

barney_5uk

Again, thanks.

I have now added "topology subnet" to the server.ovpn file but this didn't change nothing. The issue is still as before.

I had also taken the steps (for the client side) as I found described in https://my.anuson.com/knowledgebase/61/OpenVPN-error-Warning-route-gateway-is-not-reachable-on-any-active-network-adapters.html but this didn't change nothing as well.

Kind Regards

Bernard

barney_5uk

Thanks again

My OpenVPN server is the LAN gateway. As far as I understand the manual I don't need a route from the LAN gateway to the OpenVPN subnet in that case - is this right?

Kind Regards

Bernard

barney_5uk

Thanks again

NAT is activated on the server and there isn't much I can configure there. DHCP is also working as well - if any of these would fail I should have issues with the clients in my network but that's all well and there are no issues other than that with OpenVPN.

The server however shows these two routes - is this correct ?
Target Mask Gateway Interface Metrics
10.8.0.0 255.255.255.252 10.8.0.1 10.8.0.1 30
10.8.0.1 255.255.255.255 127.0.0.1 127.0.0.1 30

Kind Regards

Bernard

barney_5uk

Thanks again

169.254.0.0 is negative. There isn't such an adress received by any nic. However, when I am connected to OpenVPN from an external site I receive that IP configuration while I and I am unable to ping the target LAN, nor 10.8.0.9. Note - 192.168.1.115 is the Server in the target LAN (ping to will also fail)

On remote site 1 I get this configuration from the local WLAN access:
DHCP . . . . . . . . . : Yes
Autoconfiguration . . . : Yes
IP-Adress. . . . . . . . . . . . : 192.168.1.95
Subnet mask. . . . . . . . . . . : 255.255.255.0
Standard gateway . . . . . . . . . : 192.168.1.2
DHCP-Server . . . . . . . . . . . : 192.168.1.2
DNS-Server. . . . . . . . . . . . : 192.168.0.1
192.168.1.2

on remote site 2 I receive that IP configuration from another WLAN:
DHCP . . . . . . . . . . : Yes
Autoconfiguration . . . : Yes
IP-Adress. . . . . . . . . . . . : 192.168.0.196
Subnet maske. . . . . . . . . . . : 255.255.255.0
Standard gateway . . . . . . . . . : 192.168.0.1
DHCP-Server . . . . . . . . . . . : 192.168.0.1
DNS-Server. . . . . . . . . . . . : 192.168.0.1

in both of these cases I receive that configuration for the OpenVPN TAP adaptor:
Ethernetadapter LAN-Verbindung 5 (that's the TAP Adaptor of OpenVPN)
DHCP . . . . . . . . . : Yes
Autoconfiguration . . . : Yes
IP-Adress. . . . . . . . . . . . : 10.8.0.10
Subnet mask. . . . . . . . . . . : 255.255.255.252
Standard gateway . . . . . . . . . :
DHCP-Server . . . . . . . . . . . : 10.8.0.9
DNS-Server. . . . . . . . . . . . : 192.168.1.115

barney_5uk

Thanks again

the issue appears for all of the clients. today I had two clients to test with, but none of them received anywhere an 169.254.x.x adress.

Kind regards

Bernard

barney_5uk

Thanks, here follows the ipconfig for the server.

192.168.1.115 is the LAN interface
192.168.10.115 is the external interface which is connected to the router on 192.168.10.1. The router is connected to the internet, opens port 1194 for OpenVPN and forwards that port to the server on 192.168.10.115. The server opens port 1194 for OpenVPN as well.

What is to mention, is, that the clients always get the status "connected" shown with the green icon but have no connectivity within the network. I have also made another test with a client which was placed within the LAN - connected local, and in that case the issue is the same.

Kind Regards

Bernard

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Dokumente und Einstellungen\Administrator>ipconfig /all

Windows-IP-Configuration
Host name . . . . . . . . . . . . : Server3
Primary DNS-Suffix . . . . . . . : comlogos.local
Node type. . . . . . . . . . . . : Unknown
IP-Routing . . . . . . : Yes
WINS-Proxy aktiviert . . . . . . : Yes
DNS-Suffix search list . . . . . . . : comlogos.local

Ethernet-Adapter LAN-Connection 11:
Verbindungsspezifisches DNS-Suffix:
Description . . . . . . . . . . : TAP-Windows Adapter V9
Physical Adress . . . . . . : 00-FF-8E-85-F8-C5
DHCP . . . . . . . . . : Yes
Autokonfiguration . . . : Yes
IP-Adress. . . . . . . . . . . . : 10.8.0.1
Subnet mask . . . . . . . . . . : 255.255.255.252
Standard gateway . . . . . . . . . :
DHCP-Server . . . . . . . . . . . : 10.8.0.2

PPP-Adapter RAS-Server-(Einwähl-)Schnittstelle:
Verbindungsspezifisches DNS-Suffix:
Description . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Adress . . . . . . : 00-53-45-00-00-00
DHCP . . . . . . . . . : No
IP-Adress. . . . . . . . . . . . : 192.168.1.162
Subnet mask . . . . . . . . . . : 255.255.255.255
Standard gateway . . . . . . . . . :
NetBIOS over TCP/IP . . . . . . . : Deactiviated

Ethernet-Adapter LAN-extern:
Verbindungsspezifisches DNS-Suffix:
Beschreibung . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
Physikalische Adresse . . . . . . : 20-CF-30-71-25-DC
DHCP aktiviert . . . . . . . . . : No
IP-Adress. . . . . . . . . . . . : 192.168.10.115
Subnet mask . . . . . . . . . . : 255.255.255.0
Standard gateway . . . . . . . . . : 192.168.10.1
DNS-Server . . . . . . . . . . . : xxx.xxx.xx.xx
xxx.xxx.xx.xx
xxx.xxx.xx.xx
NetBIOS over TCP/IP . . . . . . . : Deactivated

Ethernet-Adapter LAN-Intern:
Verbindungsspezifisches DNS-Suffix:
Description . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection #2
Physical Adress . . . . . . : 20-CF-30-71-1F-71
DHCP . . . . . . . . . : No
IP-Adress. . . . . . . . . . . . : 192.168.1.115
Subnet mask . . . . . . . . . . : 255.255.255.0
Standard gateway . . . . . . . . . :
DNS-Server . . . . . . . . . . . : 192.168.1.115
Primary WINS-Server . . . . . . : 192.168.1.115

barney_5uk

Thanks, Debbie

That finally solved the issue. How may I show my thankfulness - I would like to send you some thank-you gift if that might be possible.

Kind Regards

Bernard