The MPLS-OPS Archive

[Marcelo Blanes <mblanes@larc.usp.br>]

Hi Vinod,

Sorry, now I have understand! You need to 2 NAT rules. This appear to be
NAT discussion not a MPLS one, but I think to should need 2 nat process?!
Using the same router I dont think this is possible, you should use 2
routers or do the private to private nat in other router (possible?).
Remember that nat has performance issues and usually nat from
private to private is a interim solution, usefull in network migrations.

Good luck,
Marcelo.

On Sat, 19 Jan 2002, Vinod Anthony Joseph Cherunni wrote:

> Hi,
> 
> I need NAT on the interface connecting to the Intranet site (on the CPE) 
> because the design requires NAT to happen for certain Private destination 
> prefixes also, & that's the reason the interface has "ip nat outside". As 
> per the Cisco docs i tried applying the config below, & find that even 
> after defining a route-map to policy route prefixes to a dummy non /32 
> loopback block, still NAT happens for all destinations.
> 
> interface Loopback0
> ip address 1.1.1.1 255.255.255.0
> !
> interface Ethernet0/0
> ip address 172.16.1.2 255.255.255.0
> ip nat inside
> ip route-cache policy
> ip policy route-map nonat
> !
> interface Serial 0/1
> # Interface to the Internet #
> ip address 200.1.1.1 255.255.255.252
> ip nat outside
> 
> interface Serial 0/2
> # Interface to the MPLS Private VPN #
> ip address 192.168.20.1 255.255.255.252
> ip nat outside
> 
> ip nat inside source static 172.16.1.1 202.54.9.1
> 
> access-list 123 permit ip host 172.16.1.1 172.26.1.0 0.0.0.255
> !--- Except the private network from the NAT process: 
> route-map nonat permit 10
> match ip address 123
> set ip next-hop 1.1.1.2
> !
> end
> 
> Kindly advise,
> 
> With warm regards,
> 
> Vinod.

-------
The MPLS-OPS Mailing List
Subscribe/Unsubscribe:  http://www.mplsrc.com/mplsops.shtml
Archive: http://www.mplsrc.com/mpls-ops_archive.shtml