GloablProtect + Explicit Proxy blocks WSL traffic.

Arunkumar_N — Fri, 09 Jan 2026 10:17:30 GMT

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-traffic-of-wsl2/td-p/354962

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!

topic GloablProtect + Explicit Proxy blocks WSL traffic. in Prisma Access Discussions

GloablProtect + Explicit Proxy blocks WSL traffic.