NAT - Unexpected behavior

From: gladston@br.ibm.com
Date: Mon Jun 06 2005 - 12:51:01 GMT-3


Hi,

Studying the example used on Gorito's book, lab1.
It works fine, 224.0.0.9 is converted to unicast using NAT.

But when I try to see the opposite convertion, debug does not show it.

R2(e0/1)-----(eo)R14

R2 is configured with NAT and converts RIP advertisement:

*Mar 1 04:03:17: RIP: sending v2 update to 224.0.0.9 via Ethernet0/1 (142.20.28.2)
*Mar 1 04:03:17: RIP: build update entries
*Mar 1 04:03:17: 0.0.0.0/0 via 0.0.0.0, metric 1, tag 0
*Mar 1 04:03:17: 142.20.2.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 04:03:17: 142.20.12.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 04:03:17: 142.20.23.0/24 via 0.0.0.0, metric 1, tag 0
*Mar 1 04:03:17: 142.20.125.0/27 via 0.0.0.0, metric 1, tag 0
*Mar 1 04:03:17: NAT: s=142.20.28.2, d=224.0.0.9->142.20.28.14 [0]

Now, I expect RIP traffic coming from R14 (source in this case, on the opposite hand when traffic goes from R2 to R14) to be converted, but it is not (at least, not showed by debug ip nat:

*Mar 1 04:05:09: IP: s=142.20.28.14 (Ethernet0/1), d=224.0.0.9, len 52, rcvd 2
*Mar 1 04:05:09: UDP src=520, dst=520
*Mar 1 04:05:09: RIP: received v2 update from 142.20.28.14 on Ethernet0/1
*Mar 1 04:05:09: 142.20.14.0/24 via 0.0.0.0 in 1 hops
Rack2R2#

Am I wrong or NAT should convert the source 142.20.28.14 to 224.0.0.9,
because the following NAT command?

R2
ip nat outside source static udp 142.20.28.14 520 224.0.0.9 520
!
int e 0/1
ip nat outside

Rack2R2#

Rack2R2#sh ip nat tr
Pro Inside global Inside local Outside local Outside global
udp --- --- 224.0.0.9:520 142.20.28.14:520

Or am I missing some rule like 'traffic destinated to the router is not NATed'?

Thanks for any feedback.



This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:41 GMT-3