--On Monday, April 29, 2002 11:05 AM -0700 "Crist J. Clark"
<[EMAIL PROTECTED]> wrote:
> I knew this (and didn't care since a NAT'ing bridge is such a heinous
> concept (oh, and it would be a lot more work to do it right)) back
> when I was adding the code, but then I forgot it in the meantime.
OK, I understand all the reasons why NAT is an abomination, in general.
What I _don't_ understand is why NAT is more evil on a bridge than on a
router. Can someone who espouses that religion enlighten me? My initial
analysis yields:
- NAT frequently occurs between a real network and a virtual network (one
which exists nowhere, except in a routing table). The firewall having or
not having IP addresses seems to be irrelevant to the discussion.
- NAT on a bridge makes 2 (or more) parts of a network segment have a
different view of the routing universe. I can see this being bizarre if
there are hosts on the local nets, but if the bridge has no local hosts,
this should not be an issue.
--
Carson Gaspar - [EMAIL PROTECTED]
Queen Trapped in a Butch Body