Article View: comp.dcom.sys.cisco
Article #2134Re: How to find NAT'ed address
From: Melinda Shore
Date: Tue, 20 Aug 2002 02:15
Date: Tue, 20 Aug 2002 02:15
19 lines
2294 bytes
2294 bytes
In article <MPG.17cb5c97939967059898fc@news.charter.net>,
Dave Phelps <tippenring@deadspam.com> wrote:
>Just get rid of NAT. Well there's an easy solution. I'll reserve a /24
>for each of my clients with 5 hosts.
NAT introduces a host of other problems, including
nasty protocol interactions, host unreachability, and
security unpleasantness (NAT is indistinguishable from an
attacker). They undermine network performance and jack up
the cost of equipment (there are several large manufacturers
I can think of that I would guess are each spending about
$10,000,000/year figuring out how to work around problems
that NAT introduces). Many of the workarounds also double
as tools to allow your users, should they choose to do so,
to violate local firewall policy. But hey, it's your
network.
--
Melinda Shore - Software longa, hardware brevis - shore@panix.com
If you send me harassing email, I'll probably post it
Technical Details
Message-ID:
<ajs8n5$hav$1@panix3.panix.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!panix!panix3.panix.com!not-for-mailReferences:
<54c48ac0.0208181042.79852937@posting.google.com> <ajp0ov$24a$1@canopus.cc.umanitoba.ca> <ajp1am$o05$1@panix3.panix.com> <MPG.17cb5c97939967059898fc@news.charter.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f922c,e93f40f12aae87f4 X-Google-Attributes: gidf922c,public X-Google-Thread: 10ed20,e93f40f12aae87f4 X-Google-Attributes: gid10ed20,public X-Google-Thread: 10669a,e93f40f12aae87f4 X-Google-Attributes: gid10669a,public X-Google-Thread: 102702,e93f40f12aae87f4 X-Google-Attributes: gid102702,public X-Google-Thread: 102e85,e93f40f12aae87f4 X-Google-Attributes: gid102e85,public X-Google-ArrivalTime: 2002-08-19 19:15:03 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!bloom-beacon.mit.edu!panix!panix3.panix.com!not-for-mail From: shore@panix.com (Melinda Shore) Newsgroups: comp.dcom.sys.cisco,comp.os.linux.networking,fa.firewall,mail.firewalls,comp.security.firewalls Subject: Re: How to find NAT'ed address Date: 19 Aug 2002 22:15:01 -0400 Organization: PANIX -- Public Access Networks Corp. Lines: 19 Message-ID: <ajs8n5$hav$1@panix3.panix.com> References: <54c48ac0.0208181042.79852937@posting.google.com> <ajp0ov$24a$1@canopus.cc.umanitoba.ca> <ajp1am$o05$1@panix3.panix.com> <MPG.17cb5c97939967059898fc@news.charter.net> NNTP-Posting-Host: panix3.panix.com X-Trace: reader2.panix.com 1029809702 8027 166.84.1.3 (20 Aug 2002 02:15:02 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Tue, 20 Aug 2002 02:15:02 +0000 (UTC)