11-01-2013 07:15 PM - edited 03-11-2019 07:59 PM
So, in 8.2 If I had an inside interface at 10.10.10.1 and an mpls interface (sec-100) at 10.20.20.1, and I wanted traffic to traverse between the two to interfaces, I could write the following statement:
static (inside,mpls) 10.10.10.0 10.10.10.0 netmask 255.255.255.0
What would this look like in 8.3?
Thanks!
Solved! Go to Solution.
11-02-2013 04:19 AM
In 8.3 version nat statement depends on object. You need to create object for the source ip as well nat ip and call the object in nat statement.
Object network
Host/Range/Subnet IP Address
Object network obj-10.10.10.0
Subnet 10.10.10.0 255.255.255.0
Exit
Nat (inside,mpls) sourse static obj-10.10.10.0 obj-10.10.10.0
This statement will work in similar way which u expect. You can mention nat wit respect to specific destination (similar to policy nat)
Nat (inside,mpls) source static obj-10.10.10.0 obj-10.10.10.0. Destination static obj-4.4.4.4 obj-4.4.4.4
Regards
Gk
11-02-2013 04:19 AM
In 8.3 version nat statement depends on object. You need to create object for the source ip as well nat ip and call the object in nat statement.
Object network
Host/Range/Subnet IP Address
Object network obj-10.10.10.0
Subnet 10.10.10.0 255.255.255.0
Exit
Nat (inside,mpls) sourse static obj-10.10.10.0 obj-10.10.10.0
This statement will work in similar way which u expect. You can mention nat wit respect to specific destination (similar to policy nat)
Nat (inside,mpls) source static obj-10.10.10.0 obj-10.10.10.0. Destination static obj-4.4.4.4 obj-4.4.4.4
Regards
Gk
11-03-2013 06:23 PM
That did it! That should allow for communication to take place both ways, right?
Thanks!
11-04-2013 12:41 AM
Hi,
The above NAT rule should enable bidirectional connection establishment. (Provided that the interface ACL allow the traffic)
Though usually if you dont want to NAT the source or destination network then you should not need any NAT configuration in the new software.
But this depends on the rest of the NAT configuration which we have not seen.
- Jouni
11-02-2013 06:45 AM
Hi,
In the 8.3+ software levels you dont need any NAT configuration between 2 interfaces if you dont need to specifically NAT something.
If you have a Dynamic PAT configuration from "inside" to "mpls" that contains the networks behind "inside" as the source address then in this situation you would need another NAT configuration to enable communication from the "mpls" to "inside". (to enable bidirectional connection forming that is)
If there is no NAT configuration between "inside" and "mpls" at the moment then you wont need any NAT configuration. You will just have to make sure the traffic is allowed in the interface ACL. If your have equal "security-level" between the interfaces then you will have to make sure you have "same-security-traffic permit inter-interface" also configured
- Jouni
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