Warp Blocking Connections to Public IP + Random Port

I am having an issue accessing public IP addresses when the Warp client is activated. We have a help desk that often connects to customer sites that contain devices that are port forwarded to our headquarters public IP address. We do not have a DNS location setup at this location yet.

Whenever the help desk tries to connect to a public IP (eg. x.x.x.x:8080 for example) to connect to these devices, they are unable to, as Warp blocks it. It seems that because the connection with Warp gives the users a public IP (it looks like a CGNAT address, something like 100.x.x.x) so they are unable to connect when on the headquarters network. My question is, is there a way to allow Warp to allow this traffic?

We previously used Cisco Umbrella, and are in the process of switching over to Cloudflare, but there were no issues like this with Umbrella. I was seeing an option where you are create essentially a Python script to make the Warp client “location aware” so that it would shut off when on certain networks, but this seems inefficient. It may also be that Cloudflare is just blocking non-standard ports. Any help would be much appreciated!

1 Like