Here are my details...
Here is my ipconfig output
Windows IP Configuration
Host Name . . . . . . . . . . . . : DESKTOP-*******
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : *
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2601:c6:8304:47b0:997f:c7cb:76e8:eeca(Preferred)
Temporary IPv6 Address. . . . . . : 2601:c6:8304:47b0:9897:2796:d992:cf71(Preferred)
Link-local IPv6 Address . . . . . : fe80::997f:c7cb:76e8:eeca%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.62.78.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::200:caff:fe11:2233%12
10.62.78.1[code]
DHCPv6 IAID . . . . . . . . . . . : 58781299
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-A7-3E-3D-80-EE-73-B1-4D-58
DNS Servers . . . . . . . . . . . : 75.75.75.75
75.75.76.76
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller #2
Physical Address. . . . . . . . . : *
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::b1cb:b529:1514:4143%5(Preferred)
IPv4 Address. . . . . . . . . . . : 172.16.12.101(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, September 30, 2016 2:34:02 PM
Lease Expires . . . . . . . . . . : Saturday, October 1, 2016 2:34:01 PM
Default Gateway . . . . . . . . . : fe80::e246:9aff:fe3a:137e%5
172.16.12.1
DHCP Server . . . . . . . . . . . : 172.16.12.1
DHCPv6 IAID . . . . . . . . . . . : 125890163
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-A7-3E-3D-80-EE-73-B1-4D-58
DNS Servers . . . . . . . . . . . : 172.16.12.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-E9-76-40-80
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{2285724C-B32C-402D-93A2-0B6E86F92A42}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:2891:a67:f5c1:b19a(Preferred)
Link-local IPv6 Address . . . . . : fe80::2891:a67:f5c1:b19a%3(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 33554432
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-A7-3E-3D-80-EE-73-B1-4D-58
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{965522E4-73CB-4500-97F9-5ACE226AE6A1}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
[/code]
Here is my server configuration for OpenVPN:
local 10.62.78.101
port 1194
proto udp
dev tun
ca "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\server.crt"
key "C:\\Program Files\\OpenVPN\\config\\server.key"
dh "C:\\Program Files\\OpenVPN\\config\\dh1024.pem"
topology subnet
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 10.62.78.0 255.255.255.0"
#push "route 172.16.12.0 255.255.255.0"
keepalive 10 120
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 3
Here is my client configuration file:
client
dev tun
proto udp
remote **********.ddns.net 1194
resolv-retry infinite
nobind
persist-key
persist-tun
<ca>
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
</ca>
<cert>
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----
-----END PRIVATE KEY-----
</key>
remote-cert-tls server
comp-lzo
verb 3
I also updated the registry to enable IP forwarding. I changed the value for IPEnableRouting.
If I disable the Ethernet 2, everything works as expected. I can connect from my phone to the VPN, and I can browse on both the 10.8.0.0 network as well as the 10.62.78.0 network.
If I enable the second Ethernet 2 adapter I get lots of these in the logs:
Fri Sep 30 14:44:35 2016 **.**.**.**:48601 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Fri Sep 30 14:44:35 2016 **.**.**.**:48601 TLS Error: TLS handshake failed
Fri Sep 30 14:44:35 2016 **.**.**.**:48601 SIGUSR1[soft,tls-error] received, client-instance restarting
If I disable the Ethernet 2 adapter, it connects right away.
Also, if I disable IP forwarding, it will work with both adapters enabled. So if I disable IPEnableRouting, both adapters can be enabled, and it works, but... I cannot browse anything on the 10.62.78.0 network, only the 10.8.0.0 network.
While I was posting this I did change topology from default to subnet. I didn't think it would make a difference because I thought the Android client was always using net30 anyway. So when I did this, I had both adapters enabled, and it stalled when connected and showed the normal errors in the log, then after about 5 seconds, it connected and worked.
Now it appears to be working, but I don't feel like it will keep working for some reason.
I feel it has to be a routing issue of some kind.
So maybe topology fixed it, maybe not, we will see.