From: Richard Dumoulin (richard.dumoulin@vanco.es)
Date: Wed Aug 11 2004 - 16:40:55 GMT-3
Gladston, you have it. It translates the source "172.16.0.2" to "224.0.0.9".
But as you said such a packet does not exist. So no issues here.
Now think the other way around. In this direction the destination will be
translated from "224.0.0.9" to "172.16.0.2",
--Richard
-----Original Message-----
From: gladston@br.ibm.com [mailto:gladston@br.ibm.com]
Sent: miircoles, 11 de agosto de 2004 19:47
To: ccielab@groupstudy.com
Subject: NAT Outside
There is this example at Cisco Lab Press book:
int fa 0/0
ip ad 172.16.0.1
ip nat outside
!
ip nat outside source static udp 172.16.0.2 520 224.0.0.9 520
!
end
The goal is to unicast RIP packets instead of broadcast it to the multicast
address 224.0.09. I implemented it and it works really nice. What I would
appreciate is any tip about the interpretation of a "nat outside" statement
when reading it.
At the first glance I would say that this example would translate source
address whit IP 172.16.0.2 to 224.0.0.9 when the packet goes from outside to
inside; ok, it would really does it if there was a response for RIP updates,
which is not the case.
Is there a logical way to think about it? or just memorize?
This archive was generated by hypermail 2.1.4 : Fri Sep 03 2004 - 07:02:41 GMT-3