Insights / PALO ALTO

Cisco to Palo Alto NAT migration: why it breaks and how to fix it

Ross Wilkinson · November 14, 2026

Swapping a Cisco router for a Palo Alto firewall looks simple on paper: same public IPs, same servers, same internet circuit. Then cutover night comes, outbound traffic works, and the inbound services don’t. I was recently called in after a team had reached the point of pulling the new firewall out (the case study). The problems behind a broken NAT migration are almost always the same handful.

1. Cisco thinks in interfaces, Palo Alto thinks in zones

On a Cisco router, NAT hangs off interfaces marked ip nat inside and ip nat outside. On a Palo Alto, every NAT rule matches on a source zone and a destination zone, and the destination zone is decided by a route lookup on the original destination address.

That last part is where most migrations go wrong. For an inbound rule to a web server, the packet arrives addressed to the public IP, which routes to your untrust zone. So the NAT rule is untrust to untrust, with the destination translated to the server’s private address. Writing it as untrust to DMZ (or untrust to trust) means it never matches.

2. Security policy uses pre-NAT addresses and the post-NAT zone

This one catches nearly everyone. On a Palo Alto:

  • the security rule’s destination address is the original public IP (pre-NAT), and
  • the security rule’s destination zone is the zone where the server actually lives (post-NAT).

So inbound HTTPS to a server in the DMZ needs a security rule from untrust to DMZ, with the public IP as the destination address. Use the private address or the untrust zone and the traffic is denied, even though the NAT rule is fine.

3. Rule order matters

NAT rules are evaluated top-down, and the first match wins. A broad outbound source NAT rule placed above a specific static NAT will catch traffic you meant for the specific one. Put the specific rules (static and destination NAT) above the general outbound rule.

4. One static NAT, two directions

On Cisco, ip nat inside source static covers both directions for a one-to-one mapping. On a Palo Alto, a static source translation only covers outbound unless you tick Bi-directional, or write a separate destination NAT rule for the inbound side. Pick one approach and use it consistently, so the next engineer can follow it.

5. Internal users reaching servers by their public IP (U-turn NAT)

If staff reach an internal server by its public IP or public DNS name, you need a U-turn (hairpin) rule: from trust, to untrust (because the public IP routes there), destination translated to the server’s private address. If the server sits in the same zone as the users, also translate the source to the firewall’s interface, or the server replies directly to the client and the session breaks. Split DNS is often the cleaner long-term fix.

6. ARP and routing for the public addresses

A Palo Alto answers ARP for NAT addresses that fall inside the subnet of its egress interface. If your ISP gave you a separate routed block, the ISP needs a route for that block pointing at the firewall’s address.

And on cutover night, remember the upstream device still has the old Cisco router’s MAC address in its ARP cache. If inbound traffic dies right after the swap, clear ARP on the ISP router (or ask the ISP to) before you start rewriting rules.

Test before you commit to a theory

PAN-OS will tell you which rule a packet matches, without sending any traffic:

test nat-policy-match from untrust to untrust source 198.51.100.10 destination 203.0.113.20 destination-port 443 protocol 6
test security-policy-match from untrust to dmz source 198.51.100.10 destination 203.0.113.20 destination-port 443 protocol 6

If the NAT test returns nothing, fix the zones. If the security test returns the wrong rule, check pre-NAT addresses and post-NAT zones. Between those two commands and a look at show session all, most NAT migrations are sorted out quickly.

Planning a migration?

The best time to get this right is before the change window: map every Cisco NAT statement to its Palo Alto NAT and security rules, write the test plan, and keep the old router ready as the backout. If you’re facing a migration like this, request a quote or read about the Firewall Security Review.

Next step

Have a network that needs a second set of eyes?

Start with a 30-minute scoping call. You'll leave with a clear idea of what the work involves and a written quote.