Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ASA Dynamic NAT problems after config of statics

Hello,

I'm configuring a asa 5510.

I have a dynamic NAT rule configured:

NAT (INSIDE) 1 0.0.0.0 0.0.0.0

global (outside) 1 interface

On the interface of the outside the IP adress 192.168.1.1 is configured.

With only this config the PAT translation works between the inside and outside interface. inside network is the 10.1.0.0/16 network.

If I try the packet trace with the inside address 10.1.1.4 tot the outside interface

Now I configured an additional static nat entry on the inside interface to the outside interface.

static (inside,outside) 192.168.1.51 10.1.1.1 netmask 255.255.255.255

The static is working, but the dynamic not more!?

It is not working according the packet trace, it fails in the nat translation.

Anyone encountered this problem? I'm running version 8.2(2).

Greetings,

Marcel

4 REPLIES

Re: ASA Dynamic NAT problems after config of statics

Hi,

If you remove the static it works again?

no static (inside,outside) 192.168.1.51 10.1.1.1

The static should not affect the dynamic NAT since the static only affects traffic to 10.1.1.1 using IP 192.168.1.51

Can you try it again?

Federico.

New Member

Re: ASA Dynamic NAT problems after config of statics

Yes correct.

when I remove the static it works again.

It must indeed not affect the dynamic rule, but some how it does.

I've tried a clear xlate but with no effect.

Best regards,

Marcel

Re: ASA Dynamic NAT problems after config of statics

If the outside IP of the ASA is 192.168.1.1, then using 192.168.1.51 on the static NAT is no problem.

How about you try creating a different static using a different IP 192.168.1.x?  same result?

Federico.

New Member

Re: ASA Dynamic NAT problems after config of statics

The problem is solved.

It was the syntax of the packet tracer.

it was not a physical problem.

When I do a packet trace from the ASDM for IP traffic

It sends a 'rawip' command, this doesn't work for a PAT translate.

Because a PAT translate needs udp or tcp ports before it can translate.

But I can't find it in any documentation and in the SNAF and SNAA courses it is not mentioned.

I found it after a TAC request to Cisco.

Regards,

Marcel

355
Views
0
Helpful
4
Replies
CreatePlease login to create content