I am trying to experiement on a very specific use-case for PSC on a Windows-10 laptop with Hyper-V.
I need to have a VPN running from the laptop indifferently from the wired or wifi interface.
The VMs running on this laptop will have their own VPN.
All those VPNs are supposed to be Always-On with locked Down.
To achieve this I created 2 vSwitch. The first is mapped to the Ethernet card. The second to the wifi.
Juniper Network service is active on the vSwitch only.
IPs are affected by DHCP on the vEthernet NIC for the laptop and the VMs.
Everthing's working fine on the VMs.
But on the laptop, we have issues with the VPN connections that do not auto-connect when network comes up.
For the wired connection we found a tweak by simply setting a fixed IP adress on the physical Ethernet NIC.
But for Wifi connection it does not work. The Pulse Secure Client never initiates the VPN on itself. But if we connect the Ethernet card first, let the negotiation initiate and remove the cable before it ends, the negociation terminates succesfuly on the Wifi connection.
It looks like the Pulse Client simply do not detect connectivity on the wireless adapter with this setup.
Has anybody been able to implement autoconnect for Wifi acces on Hyper-V ?
On the Hyper-V guest, do you see the IP address assignment on the network interface?
It seems like the interface doesn't seem to be considered as active for the Pulse Client to auto-start the connection.
If you try to manually start the connection (disable always-on and enable override), are you seeing "Waiting for network" message on the pulse client?
It's exactly the point. Pulse Client does not consider the connection to be up.
If I do a manual connection the VPN established. Everythings works fine except the autoconnect feature.
@sdeglin If the interface doesnt have any IP address (status as Not connected), then I'd call that as an issue, however manual connection should fail too.
Please open a support ticket with us as it might require additional troubleshooting.