12-02-2010 03:05 PM - edited 03-11-2019 12:17 PM
Is anyone else annoyed with the changes in 8.3 nat configuration? Or maybe I'm doing it wrong. In the past, something like this would just be two lines:
object network obj-10.204.1.10-47808
host 10.204.1.10
object network obj-10.204.1.10-21068
host 10.204.1.10
object network obj-10.204.1.10-47808
nat (inside,outside) static interface service tcp 47808 47808
object network obj-10.204.1.10-21068
nat (inside,outside) static interface service tcp 21068 21068
12-02-2010 03:19 PM
Yes, unfortunately there is quite a huge change in the NAT configuration from ASA version 8.3 onwards.This is to cater for more flexibility within the NAT feature which the earlier version is lack of. I guess we are all trying to get used to the new format at this point
12-02-2010 07:26 PM
Jenn is right.
You can compare old and the new here: https://supportforums.cisco.com/docs/DOC-9129
-KS
12-03-2010 12:23 AM
With all due respect, this change doesn't make any sense. I understand that NAT will be more "flexible" than it was before, but it could have been done without such drastic change on CLI configuration. I've just converted a large NAT config to new style and it looks terrible now.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide