cancel
Showing results for 
Search instead for 
Did you mean: 

How to share a VPN connection between a VM and the host?

shimmer
Occasional Contributor

How to share a VPN connection between a VM and the host?

Hi,

 

Following from https://community.pulsesecure.net/t5/Pulse-Desktop-Clients/How-to-share-a-VPN-connection-between-a-V...

which I can't post to because I get a post-flooding error.

 

Mod [email protected] advised this requires a NAT connection with the VM. 

 

I've setup my VM (ubuntu) in hyperv with NAT networking following instructions here: 

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network

and here: https://serverfault.com/a/911587

 

But when Pulse Secure connects, I can no longer connect to the NAT router (my host laptop). Ping no longer responds in either direction. VPN is working fine on the Windows host laptop, the new NIC appeas on it: Pulse Secure - Juniper Networks Virtual Adapter, and connectivity to remote hosts works fine on it.  The VM's NAT nic remains up, has an IP assigned, and can ping itself, but can no longer ping the host.

 

A similar setup works fine in virtualbox by following guidance here: https://www.virtualbox.org/manual/ch06.html#network_nat_service

 

Any ideas?

3 REPLIES 3
zanyterp
Moderator

Re: How to share a VPN connection between a VM and the host?

i am not sure that should be working. can you do the following:
take a pulse client log
open the zip file
navigate to the log folder
open pulseclient.log
search for Enforcement IPV4=0 Enforcement IPV6=0
is either of those set to 1?
shimmer
Occasional Contributor

Re: How to share a VPN connection between a VM and the host?

No mention of Enforcement in any pulseclient.logs. Are you thinking this ability has been disallowed by admin policy? Is there any other way of checking? Eg a registry value? If this is true, it's strange how it works in virtualbox, but not hyperv

zanyterp
Moderator

Re: How to share a VPN connection between a VM and the host?

thank you for checking. yes, that is what i was thinking.the configuration values are sent down to the client only; they are not expected to be in the registry. it is odd if it is policy-based; however, i know there have been special accommodations in-general for different virtual adapters
i would recommend opening a case with our support team for investigation to confirm which behavior you are seeing is correct.