Recent change in WARP IP address behavior?

I have been using the WARP vpn with Zero Trust Access for several months without any issue. The Zero Trust Access policy has been setup to allow only my (locally assigned) external IP address. This has been working whether I was running the WARP vpn or not. Now, I can only access Zero Trust with WARP turned off.

So, is this the result of a recent change to the WARP vpn? In other words, did the WARP vpn until recently preserve my locally assigned IP address? If not, I can’t explain the new behavior.


I created this test policy:

Selector: Source IP
Operator: is
Value: (my own IP)
Selector: SNI Domain
Operator: is

Action: Network Override
Override IP:
Override Port:

That’s a policy that, if the visitor IP is (me), and I’m visiting the web then it’s gonna change the destination IP to (which is’s IP).

After creating that policy I waited a minute and tried to open and got a SSL certificate error because of the domain mismatch, which means the policy worked by recognizing my original IP. Then I changed the policy so the IP won’t match and tried again after a minute: The policy did not match, which means it worked.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.