From: gladston@br.ibm.com
Date: Mon Jun 06 2005 - 22:29:15 GMT-3
Hi Tom,
Thanks for the reply.
No, it achieve the result, as pointed on Gorito's book.
ip nat outside source static udp 142.20.28.14 520 224.0.0.9 520
The goal is to have multicast RIP converted to unicast without using
neighbor. This works fine.
What I do not understand is this:
If packet sourced by this router with destination 224.0.0.9 is converted
to 142.20.28.14 when exiting outside interface, why packet entering
outside interface, which source is 142.20.28.14 does not get converted by
this NAT entry.
It seems I am missing something here.
Cordially,
------------------------------------------------------------------
Gladston
"Tom Nooning" <t.nooning@insightbb.com>
06/06/2005 22:05
To
Alaerte Gladston Vidali/Brazil/IBM@IBMBR, <ccielab@groupstudy.com>
cc
Subject
Re: NAT - Unexpected behavior
I *think* you may have the logic reversed in your NAT statement:
ip nat outside source static udp 142.20.28.14 520 224.0.0.9 520
Try:
ip nat outside source static udp 224.0.0.9 520 142.20.28.14 520
Of course, I could always be very, very wrong.
-Tom
----- Original Message -----
From: <gladston@br.ibm.com>
To: <ccielab@groupstudy.com>
Sent: Monday, June 06, 2005 11:51 AM
Subject: NAT - Unexpected behavior
> 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.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:41 GMT-3