Breaking Out Specific Ports from a VPN Tunnel for a Client IP breaks INET

[dromanelli]

Hi All,

I am running a PA-850 in my data center.  All of our internet-destined traffic goes into a catchall VPN and goes off to a cloud security company called Zscaler for processing before it goes onto the internet.  However, for the IP of my machine, I do not want TCP ports 22 and 10443 going to Zscaler. I want any TCP 22 or TCP 10443 traffic sourced from my IP to go out the direct internet circuit (on a translated IP, as you'll see below) and not go into any VPN. However, when I set the NAT statement in the Palo to accomplish that, it completely breaks my internet connectivity.  The only way I can get it back is to either break out ALL traffic sourced from my PC (not just 22 and 10443), or remove the attempt to break out 22 and 10443 from the Zscaler VPN. Below are the rules. If I disable them, BAM!, internet is back. I don't understand why. Any help is appreciated.

[raji_toor]

I don't know your eact architecture, but how are you forwarding traffic to Zsclaer, routing or PBF, It won't be only NAT in play, if its done at the firewall. You probably would need a PBF rule with source from your system to be forwarded towards internet link.

[dromanelli]

Hi Raji,

We are using PBF.

So you're saying I would need to write in a rule for my client IP port 22 and 10443 and insert it into the PBR negates? 

[raji_toor · Accepted solution]

@dromanelli you should try a new PBF rule higher in order with you ip in source and negate private ranges and use your specific ports and action as No PBF

[dromanelli]

That worked. Thank you so much.