Im trying to connect Windows Server 2016 VM(KVM based), to Openvp server.
VIrtualMachine has following network configuration:
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 169.254.0.1 5.5.5.5 16
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::5c12:97a3:bbcc:6a96%5
IPv4 Address. . . . . . . . . . . : 5.5.5.5
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : fe80::ffff:1:1%5
169.254.0.1
While connecting to OpenvVPN server, applications tries to set direct route via IPAPI fails, then runs following command to add direct route to VPN server:
C:\Windows\system32\route.exe ADD 6.6.6.6 MASK 255.255.255.255 169.254.0.1
Warning: route gateway is not reachable on any active network adapters: 169.254.0.1
Route addition via IPAPI failed [adaptive]
Route addition fallback to route.exe
Where 5.5.5.5 is my VM external routable IPv4 address. 6.6.6.6 is OpenVPN server external routable IP.
This route command fails:
route ADD 6.6.6.6 MASK 255.255.255.255 169.254.0.1
The route addition failed: Element not found.
I could fix VPN connection by running following command, and defining interface ID to route command:
route ADD 6.6.6.6 MASK 255.255.255.255 169.254.0.1 IF 5
OK!
I have tried variuos configuration, like "route-method exe" etc, but Opevpn fails to add correct route to VPN server. I think it because that 169.254.0.1 is virtual link-locak IP(point to point interface), and it is not accesible as normal network.
Maybe someone has suggestions how solve this issue inf OpenVPN configuration?
