Hyper-V virtualised OS vpn tunneling through host

Got a problem with Viscosity or need help? Ask here!

Wibin

Posts: 1
Joined: Tue Jan 22, 2013 10:09 pm

Post by Wibin » Tue Jan 22, 2013 10:21 pm
Hiya!

In short, I'd like to have vpn tunnelling on a virtual machine.

Option 1. to have the vpn client in the VM environment (bad idea). Option 2. to have the vpn client on the Host computer which routes the traffic to the client virtual machine (better but does not function atm).

1. I have an external network set up for the vm and it's working fine. If I install Viscosity on the VM, the download performance drops from 30 megabits (max. for vpn) to approx. 2 megabits/sec. Strangely enough, upload is not affected, which remains at 10 megabits/sec whether viscosity is installed on a VM or a native OS.

2. So.. I installed Viscosity on the VM host computer, and made a 1:1 route with hyper-v virtual switch to the virtual machine. This should route all traffic from the Host adapter (Viscosity virtual adapter) to the VM, with dhcp/ip management happening entirely on the VM side. However, this does not work at all.
->> I have one ip-address for the VPN, and Viscosity status window is reporting an ip - which probably means it is working as a dhcp client instead of the VM client. The virtual machine should negotiate the ip itself, so is a the case where ip-dhcp is not entirely transparent - and is it possible to make it so?

Cheers!
Wibin

Eric

User avatar
Posts: 907
Joined: Sun Jan 03, 2010 3:27 am

Post by Eric » Thu Jan 24, 2013 6:21 pm
Hi Wibin,

We're a bit confused about exactly what you are trying to achieve. Are you trying to have the VM receive an IP address directly from your OpenVPN server or are you simply wanting to route all traffic from your VM through your OpenVPN connection.

How you setup your connection is important to this. If you want your VM to have an IP from your server and allow it access, you will need to setup a bridged TAP connection with Viscosity, and then bridge the Viscosity adapter to your VM adapter. Unfortunately we don't have access to Hyper-V here to do any testing. If you can be more specific about your VPN Connection (even providing the configuration file) we might be able to point you in the right direction though.

Regards,

Eric
Eric Thorpe
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
2 posts Page 1 of 1