From: ccie2be (ccie2be@nyc.rr.com)
Date: Wed Jun 30 2004 - 15:26:56 GMT-3
Hi guys,
I want to use NAT on R3 to convert the destination address of a rip routing
update 224.0.0.9 to a unicast going to R2.
Here's the scenario from practice lab in the cisco press ccie practice lab
book ( you can download lab from cisco press):
R3 e1 ------- e2 R2
R3 and R2 and both running RIP and are both on ethernet 172.16.0.0/24.
R3's e1 address is 172.16.0.2 and R2's e2 address is 172.16.0.1
Here's the issue:
The config must be done on R3.
Here's the solution they show:
interface FastEthernet0/0
ip address 172.16.0.2 255.255.0.0
ip nat outside
!
ip nat outside source static udp 172.16.0.1 520 224.0.0.9 520 <----- this
doesn't make sense to me
R3#debug ip nat det
IP NAT detailed debugging is on
R3#clear ip route *
R3#
00:57:29: NAT: i: udp (172.16.0.2, 520) -> (224.0.0.9, 520) [0]
00:57:29: NAT: s=172.16.0.2, d=224.0.0.9->172.16.0.1 [0]
***********************
So, I've got a couple of questions:
Is the above solution the best, most logical solution to this problem?
Wouldn't it be better and more intuitive to directly change the destination
address of packets leaving R3 instead of changing the source address of
packets arriving from R2?
For example, wouldn't it make more sense to use
ip nat inside destination list 1 pool <name> where list 1 references 224.0.0.9
and pool references 172.16.0.1?
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:53 GMT-3