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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Nat statements in ASA :8.3(1)

Hello All,

The configuration for the natting is something like this

object network Obj-10.232.50.99

nat (INSIDE,ATT-Tele-Net) static 32.x.x.69

object network Obj-10.232.50.98

nat (INSIDE,ATT-Tele-Net) static 32.x.x.66

when I do a show xlate

mdcxf01b/EXTRANET# sh xlate | i ATT

NAT from INSIDE:10.232.50.98 to ATT-Tele-Net:32.x.x.66

NAT from INSIDE:10.232.50.99 to ATT-Tele-Net:32.x.x.69

mdcxf01b/EXTRANET#

If I understand the config statements 10.232.50.98 is natted to 32.x.x.66  and 10.232.50.99 is natted to 32.x.x.69 , but do we need reverse natting stements as well to work this ?

Thanks,

Josh

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Red

Nat statements in ASA :8.3(1)

Hi Josh,

The xlates are showing the correct  output, if the inside host goes to the internet, it would be natted  to 32.x.x.69, and if someone tries to access it from internet, it would be on the public ip, so yes, it is bi-directional mapping that you see there.

Thanks,
Varun Rao
Security Team,
Cisco TAC

Thanks, Varun Rao Security Team, Cisco TAC
1 REPLY
Red

Nat statements in ASA :8.3(1)

Hi Josh,

The xlates are showing the correct  output, if the inside host goes to the internet, it would be natted  to 32.x.x.69, and if someone tries to access it from internet, it would be on the public ip, so yes, it is bi-directional mapping that you see there.

Thanks,
Varun Rao
Security Team,
Cisco TAC

Thanks, Varun Rao Security Team, Cisco TAC
237
Views
0
Helpful
1
Replies