Help required to convert Cisco ASA NAT rule onto Palo Alto

Reply
L4 Transporter

Help required to convert Cisco ASA NAT rule onto Palo Alto

Hi Guys,

I am not expert in reading or understanding the Cisco ASA NAT rules and I have just started to feel comfortable with Palo Alto except for NAT rules.  Can someone please guide me through on how to go around configuring the following Cisco ASA NAT rule onto the Palo Alto?

I have just taken a couple of rules to convert.  Based on this, I would get the rest done on my own.

Following are the CISCO ASA NAT RULEs:

Rule 1 # access-list inside_nat0_outbound extended permit ip 10.1.2.0 255.255.255.0 10.1.250.128 255.255.255.128

Rule 2 # access-list inside_nat0_outbound extended permit ip EH_Staff_Network 255.255.255.0 10.1.250.128 255.255.255.128

I know the exact rule cannot be expalined, but an overview on how to re-configure the above rules will be very helpful.

Many Thanks in Advance.

Regards,

Kal

L4 Transporter

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

Hello Kal,

with my limited ASA knowledge I would say your sample code does not look like a NAT rule it looks like an ACL security rule.

This site might be a starting point for you to understand the cisco config:

http://www.tech21century.com/access-lists-and-nat-on-cisco-asa-firewalls-some-clarifications/

rgds Roland

Highlighted
L0 Member

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

Look to me like that is the ACL that dictates what is allowed to be NAT'd outbound.  The actuall NAT rule is setup with the command nat syntax below

xxxx(config)# nat ?

configure mode commands/options:
  (  Open parenthesis for the name of the network interface where the
     hosts/network designated by the local IP address are accessed

L4 Transporter

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

Thank you for the web link.  Will look into it, find out more relevant stuff and then come back to you guys.

Cheers Guys.. Very Kind of you.

Regards,

Kal

L4 Transporter

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

Kal just to let you know if you are not already aware of there is a migration tool.

Download.png

This tool can migrate a Cisco config to a PA config.

More info http://www.securlabs.net/

rgds Roland

L4 Transporter

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

Roland,

I did know there was a migration tool and it does not convert the NAT rules is what I got to know.  Secondly, I am not a CNSE qualified yet so might not have access to the tool is what I got to know.  Am I correct?  If not is there any way to get it sorted out?

Thank you

Kal

L4 Transporter

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

Hi Kal,

everybody can use the migration tool just follow this link:

http://www.securlabs.net/

Yes you are right

Doesn't Convert VPN and Nat Rules

rgds Roland

L4 Transporter

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

:smileyhappy: that is exactly where i was stuck.  Unfortunately, I do not feel very comfortable with configuring the NAT rules of PAN even though I understand them theoritically.  Hence was asking for help.

Out of the cisco config, I could only find 3 these rules that state NAT:  (do they make sense)

nat (inside) 0 access-list inside_nat0_outbound

nat (inside) 1 10.0.0.0 255.0.0.0

nat (dmz) 1 172.16.50.0 255.255.255.0

Not applicable

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

Kalyanram,

Here you go...

nat (inside) 0 access-list inside_nat0_outbound

This statement is a no-nat rule.  Traffic that arriving on the interface "inside" that matches the ACL "inside_nat0_outbound" is not natted.

nat (inside) 1 10.0.0.0 255.0.0.0

This statement does a hide nat for all traffic arriving on the interface "inside" that comes from 10.0.0.0/8.  It will hide it behind the global nat address that corresponds to ID 1, and the correct outgoing interface.

nat (dmz) 1 172.16.50.0 255.255.255.0

This statement (you guessed it!) does a hide nat for all traffic arriving on your "dmz" interface that comes from 172.16.50.0/24.  It nats behind the same global statements as the prior rule.

If you post (or PM me) the output of "show run | in global" and "show run | in static", I can explain the rest of the rules for you.

The nat rulebase in your PAN should do the same thing... one rule from inside to outside that does not nat (matching that ACL), and one that does nat (you can create a single rule that handles traffic from both your dmz and inside zones).

HTH,

James

L4 Transporter

Re: Help required to convert Cisco ASA NAT rule onto Palo Alto

James,

Thank you for the explanation.  I will be going on site to do the migration for the customer.  If any thing goes wrong in terms of NAT rules, I will post (or PM you).  Thank you once again for your help.

Regards,

Kal

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!