Products
Solutions
Partners
Support
Company
Try Now
Pulse Secure Community
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
since ‎10-27-2020
‎03-01-2022
aritzbastida
New Contributor

Re: WSL2 network connection breaks with Pulse Secu...

by in Pulse Desktop Clients
‎10-29-2020 01:33:AM
1 Kudo
‎10-29-2020 01:33:AM
1 Kudo
Thanks for the reply. I'm using Windows Pulse Client (9.1). My connection detais are:     Tiempo restante de la sesión: 7h 58m 12s Duración de la sesión: 1m 48s Tipo de túnel: VPN Tipo de VPN: ESP IPV4 asignada:: 10.57.181.148 Bytes recibidos: 347713 Bytes enviados: 198792 Origen de conexión: Añadido por el usuario Regarding WSL2 Linux compatibility with Windows Pulse Secure client, is the feature expected at some point? Could you consider to enhance it?     It seems that there is already some support for "Linux on Windows", as stated in the release notes of version 9.1.5: https://www-prev.pulsesecure.net/download/techpubs/current/2197/pulse-client/pulse-secure-client-desktop/9.1rx/ps-pulse-9.1r9.0-releasenotes.pdf    Pulse Linux Client on Windows now supports Fedora 30, Ubuntu 19.10 and Debian 10 platforms However, that is quite the opposite of my setup. I'd need Pulse Windows Client support for WSL2 distributions (Ubuntu, etc.). To sum up, both my local workstation (Windows PC) and local virtual machines (WSL2 distributions) should be capable of connecting to the corporate network through the VPN.         ... View more

Re: WSL2 network connection breaks with Pulse Secu...

by in Pulse Desktop Clients
‎10-27-2020 10:21:AM
‎10-27-2020 10:21:AM
Yes, probably the configuration is Full Tunnel, because some sites are restricted while I'm connected to the VPN. Is there any way to share with you my Pulse Secure client configuration?   Regarding the limitation of local subnets, I'm not sure that is the case. When connected to the VPN, my Docker containers can still reach other domains (both corporate and external). See the example below. Note that "Docker for Windows" is using WSL2 under-the-hood.   [email protected]:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal [email protected]:~$ ping www.google.com ping: www.google.com: Temporary failure in name resolution [email protected]:~$ ping kibana.es.telefonica ping: kibana.es.telefonica: Temporary failure in name resolution [email protected]:~$ docker run -it --rm busybox /bin/sh / # ping www.google.com PING www.google.com (216.58.211.36): 56 data bytes 64 bytes from 216.58.211.36: seq=0 ttl=37 time=16.116 ms 64 bytes from 216.58.211.36: seq=1 ttl=37 time=19.486 ms ^C --- www.google.com ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 16.116/17.801/19.486 ms / # ping kibana.es.telefonica PING kibana.es.telefonica (10.148.136.56): 56 data bytes 64 bytes from 10.148.136.56: seq=0 ttl=37 time=23.034 ms 64 bytes from 10.148.136.56: seq=1 ttl=37 time=28.450 ms ^C --- kibana.es.telefonica ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 23.034/25.742/28.450 ms Apparently, it's quite common to have connectivity issues with WSL2 and VPN. However, all the workarounds I have found are for other products, such as Citrix or Cisco AnyConnect. For example: https://github.com/microsoft/WSL/issues/5764   I have tried out many workarounds, but none of them seem to work. ... View more

WSL2 network connection breaks with Pulse Secure V...

by in Pulse Desktop Clients
‎10-27-2020 07:07:AM
2 Kudos
‎10-27-2020 07:07:AM
2 Kudos
My workstation setup is: Windows 10 (1909) + WSL2 (ubuntu)  My Linux distribution connects to the external network. I can ping www.google.com, download packages with apt-get, and so on. But, once I connect to the corporate VPN with Pulse Secure (9.1.5), connectivity suddenly stops:   Before connecting to VPN: [email protected]:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.17.135.17 0.0.0.0 UG 0 0 0 eth0 172.17.135.16 0.0.0.0 255.255.255.240 U 0 0 0 eth0 [email protected]:~$ ping 172.17.135.17 PING 172.17.135.17 (172.17.135.17) 56(84) bytes of data. 64 bytes from 172.17.135.17: icmp_seq=1 ttl=128 time=0.410 ms 64 bytes from 172.17.135.17: icmp_seq=2 ttl=128 time=0.568 ms ^C --- 172.17.135.17 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1031ms rtt min/avg/max/mdev = 0.410/0.489/0.568/0.079 ms  After connecting to VPN: [email protected]:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 172.17.135.17 0.0.0.0 UG 0 0 0 eth0 172.17.135.16 0.0.0.0 255.255.255.240 U 0 0 0 eth0 [email protected]:~$ ping 172.17.135.17 PING 172.17.135.17 (172.17.135.17) 56(84) bytes of data. ^C --- 172.17.135.17 ping statistics --- 320 packets transmitted, 0 received, 100% packet loss, time 331775ms   Note that I cannot even connect to the default gateway, which is the virtual network adapter for WLS: PS C:\Users\UT06609> Get-NetIPConfiguration -InterfaceAlias "*WSL*" InterfaceAlias : vEthernet (WSL) InterfaceIndex : 66 InterfaceDescription : Hyper-V Virtual Ethernet Adapter #2 IPv4Address : 172.17.135.17 IPv6DefaultGateway : IPv4DefaultGateway : DNSServer : 10.144.145.179 10.144.57.198 I tried to "manipulate" the routing rules created by Pulse Secure (e.g. change metrics), but couldn't make it work. Is PulseSecure compatible with WSL2? If so, should I open a bug ticket (and how)?   Thank you in advance. Aritz       ... View more
Labels:
Latest Tags
Kudos from
View All
© 2017 Pulse Secure, LLC. Use of this website assumes acceptance of our Legal Notices and Privacy Policy. Pulse Secure has updated its Privacy Policy effective June 28, 2017.