Hyper-V virtualised OS vpn tunneling through host
Posted: 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
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