DanEllison
I recently upgraded all my machines to Windows 10. My tap adapter got renamed; fixed that. My client could connect; things were looking good.
It appears my client is connecting using IPv6. If I ping my server, it comes back IPv6, and I can see the shares from my server in explorer. However, I can't ping my server using its static IPv4, nor can I ping or remote desktop to any computer on my home network which I used to be able to do.
Do I have to force OpenVPN to IPv4 only some how?
Traffic
Please see the Forum rules (top of page)
DanEllison
Server Config:
port 1194
proto udp
dev tap
dev-node tap-bridge
ca "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\MOZART.crt"
key "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\MOZART.key" # This file should be kept secret
dh "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\dh2048.pem"
ifconfig-pool-persist ipp.txt
server-bridge 10.19.80.9 255.255.255.0 10.19.80.200 10.19.80.255
keepalive 10 120
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 3
Client Config:
client
dev tap
proto udp
remote 99.999.999.999 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\CRAY.crt"
key "C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\CRAY.key" # This file should be kept secret
ns-cert-type server
comp-lzo
verb 3
DanEllison
Okay, I solved it. Besides the upgrade recreating my tap adapter, and having to rename it back to tap-bridge, I had to bridge it back to my Ethernet adapter again.
Traffic
Thanks for letting us know your solution 8-)
