very interesting NAT scenario, any idea?

From: jeremy co (jeremy.cool14@gmail.com)
Date: Sat Mar 28 2009 - 10:00:43 ART


R1----------------e0/0--R2--e0/1-------------R3

R1 has a default route to R2
R2 and R3 run ospf

** do not advertise NAT pool addresses as a route to R3

NAT statement on R2

access-list 100 deny ospf any any

access-list 100 permit any any
ip ant inside source list 100 pool NAT
ip nat pool NAT 150.0.100.1 150.0.100.254

e0/0 ----> ip nat inside
e0/1 ----> ip nat outside

But what is interesting here?

- if u let time goes on R2 will be adjacent with R3
- if u ping R3 interface ,NAT process will translate e0/1 to your NAT
pool!!!

Basically with a broad statement like ACL 100 inside address as well as
local R2 addresses will translate to NAT pool
However, interesting behavior of R2 is taht if u let time goes on R2 will be
adjacent with R3 with its original e0/1 address not translated address!!!

Any idea why this is happened ?

Jeremy

Blogs and organic groups at http://www.ccie.net



This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:07 ART