Re: NAT (Portforwarding) for local traffic

From: Jack Tsai (jacknew2005@gmail.com)
Date: Tue Aug 05 2008 - 12:27:38 ART


R1--R3--R2
The gold is to make use of NAT on R3, so that R2 can ping R1
Ref:
http://blog.internetworkexpert.com/2008/02/15/the-inside-and-outside-of-nat/

Her we go!
R1:
interface Serial1/0.103 point-to-point
 ip address 10.1.13.1 255.255.255.0
 frame-relay interface-dlci 132

R3:
interface Serial1/0.301 point-to-point
 ip address 10.1.13.3 255.255.255.0
 ip nat enable
 frame-relay interface-dlci 312
!
interface Serial1/0.302 multipoint
 ip address 10.1.23.3 255.255.255.0
 ip nat enable
 frame-relay map ip 10.1.23.2 302
 frame-relay map ip 10.1.23.3 302
 frame-relay interface-dlci 302
!
ip nat source static 10.1.23.2 10.1.13.2
ip nat source static 10.1.13.1 10.1.23.1

R2:
interface Serial1/0.203 multipoint
 ip address 10.1.23.2 255.255.255.0
 frame-relay map ip 10.1.23.2 203
 frame-relay map ip 10.1.23.3 203
 frame-relay interface-dlci 203

Test:
R1#sh ip route
C 10.1.13.0/24 is directly connected, Serial1/0.103

R1#ping 10.1.13.3
Sending 5, 100-byte ICMP Echos to 10.1.13.3, timeout is 2 seconds:
!!!!!

R1#ping 10.1.13.1
.....
Success rate is 0 percent (0/5)

R3#ping 10.1.13.1 successful
R3#ping 10.1.13.3 successful
R3#ping 10.1.23.2 successful
R3#ping 10.1.23.3 successful

R2#ping 10.1.23.3 successful
R2#ping 10.1.23.2
.....
Success rate is 0 percent (0/5)

R2#ping 10.1.23.1
.....
Success rate is 0 percent (0/5)

Please help!

Thanks,
Jack

Petr Lapukhov wrote:
> Huan,
>
> NAT could be tricky sometimes, you see now! But personally, I'm a big fan of
> doing all kinds of weird things with NAT :)
> So here is another link explaining the difference between inside and outside
> NAT domain:
>
> http://blog.internetworkexpert.com/2008/02/15/the-inside-and-outside-of-nat/
>
> HTH

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



This archive was generated by hypermail 2.1.4 : Mon Sep 01 2008 - 08:15:29 ART