- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
01-09-2026 02:17 AM
Hello everyone,
We’re facing an issue with WSL2 where traffic from WSL is unable to route to Prisma when GlobalProtect (GP) is running on the host Windows machine with an explicit proxy.
Environment / Setup
GlobalProtect enabled with Explicit Proxy
Proxy PAC listening on 127.0.0.1:9999
WSL2 traffic appears to use the Windows Hyper-V loopback interface
We followed the solution suggested in the Palo Alto Networks community post below:
https://live.paloaltonetworks.com/t5/globalprotect-discussions/globalprotect-blocks-the-network-traf...
Get-NetIPInterface -InterfaceAlias "vEthernet (WSL(Hyper-V firewall))" | Set-NetIPInterface -InterfaceMetric 1
Get-NetAdapter | Where-Object {$_.InterfaceDescription -Match "PANGP Virtual Ethernet Adapter #3"} | Set-NetIPInterface -InterfaceMetric 6000
This workaround causes issues for other applications on the host that also rely on the proxy.
The PowerShell changes are not persistent and revert when the session is closed.
Has anyone successfully configured proxy support for WSL2 while keeping GlobalProtect Explicit Proxy running on the Windows host at 127.0.0.1:9999?
Any guidance or best practices would be greatly appreciated.
Thanks in advance!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

