On 11 May 99, at 17:01, John Talbot wrote:
> This mapping between internal and external seems to take place:
> * Staticly, where one internal IP address is mapped to one external
> address
> * Dynamicly, where all the internal IP addresses are mapped to a few
> external addresses
>
> My question is how often is the addressing done dynamicly, and if it is, how
> can I have applications addressing hosts within my private addressing
> domain, if the addresses are masked by NAT.
This is, I believe, the case where static mapping is *required*.
Note, however, that there is another case which doesn't quite fit either of
your definitions above.
If you use Linux IP "masquerading", all of your internal addresses map to a
*single* external address; this is like your "dynamic" scenario in that the
pool of external addresses is smaller than the number of internal addresses
mapped onto that pool.
BUT, I believe you can statically map a specific internal (IP,port) pair to
a specific external port, and this is sufficient to qualify as a static NAT
for purposes of allowing external clients to connect to an internal server.
David G
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
