Ambiguous nat translations

From: balaji.balakrishnan (balaji.balakrishnan@swift.com)
Date: Tue Feb 25 2003 - 14:27:14 GMT-3


Hi Group,

I have a clarification on using "extendable" keyword with static nat translation entries.
The "extendable" can be used to create ambiguous nat translations, where single Global address can be used to map to two local IP
addresses. This may require in some applications like DNS where all the customer DNS request on different Global addresses can be
mapped to single local. For example,

ip nat inside source static 192.168.1.1 202.1.1.1 extendable
ip nat inside source static 192.168.1.1 198.1.2.1 extendable

For any new outside to inside session, the router will track the session by creating full translation table ( address/ports). But,
my question is that how router will behave when the traffic initiated from the local side. In above example, what entry will be used
when the traffic initiated from 192.168.1.1 ??

Rgds,
Bala.



This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:35 GMT-3