And the Fairchild F8 docs claim that it has a stack register.
What you're apparently saying is that in your experience people have
not felt a need for a special word to designate the limited form of NAT
that comes with common Linux distributions. You have now encountered,
in the Linux community, people who have for better or for worse adopted
a common English word for this purpose.
I gather from other traffic in this thread that NAT software with the
particular limitation that we've been discussing is not common in the
BSD community, so I don't find it particularly surprising, or worthy of
comment, that they don't have a special word for it.
> In other words, `NAT' is a term like `routing'; you don't find
> people saying `this device is a foo, not a router, because it
> doesn't handle ToS routing.'
But do you find people saying `this device is a bridge, not a router,
because it doesn't handle ...'?
> > If it has occurred elsewhere, then what word or
> > phrase is used to refer to it in a way that would not be confused with
> > fully-implemented NAT?
>
> `NAT that translates through only one address.' `Routing without
> ToS routing.'
10 syllables. 7 syllables. (YMMV)
Masquerading.
4 syllables.
Clearly an abomination to at least some people who know what NAT stands
for, but with a certain intuitive appeal to a net newbie.
I find it easier to explain to a lay person than full-blown NAT, and I
find it a convenient shorthand, just as I find "motorcycle" a convenient
shorthand for "motor vehicle with two wheels."
But I don't insist that people use the term, and I'm prepared to explain
it if I inadvertently use it in the presence of someone who doesn't
understand it.
--
http://psg.com/~ted/ (Ted Powell) If your hard drive crashes, perhaps you have a recent backup. If Earth crashes, what then? We need off-site backup: Luna, L5, Mars, wherever.