From: ccie2be (ccie2be@nyc.rr.com)
Date: Mon Sep 27 2004 - 16:38:10 GMT-3
Hey Drew,
The extendable keyword applies only to static NAT translations. Normally,
in a static translation an inside local address can only be translated into
1 inside global address. However, there are situations where the inside
local address needs to be translated into more than 1 address.
For example, assume your DNS server is assigned the address of 10.0.0.1
(inside local addr) and your 1 router is connected to two different ISP's
where each ISP has assigned you a different address space. Since each ISP
has their own DNS servers which have to access your DNS server, you need to
static translations.
Normally, this isn't allowed.
To overcome this restriction, you use the "extendable" keyword on your 2
static translations.
See the example on page 378 in Jeff Doyle's book Routing TCP/IP vol II.
HTH, Tim
----- Original Message -----
From: "Drew Whitaker" <drew.whitaker@gmail.com>
To: <ccielab@groupstudy.com>
Sent: Monday, September 27, 2004 1:15 PM
Subject: NAT-Extendable
> Can someone explain to me the use of the keyword 'extendable' at the
> end of NAT statements? Cisco's web site says it is used for
> 'ambiguous' translations which, pardon the pun, is a bit ambiguous.
>
> The example I'm looking at is the final configuration or R3 in the
> CCIE Routing and Switching Practice Labs (Cisco Press) lab #1, section
> 2.1:
> ip nat outside source static udp 172.16.0.1 520 224.0.0.9 520 extendable
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:50 GMT-3