Re: How to find NAT'ed address

Article View: comp.dcom.sys.cisco

Article #2135

Back to comp.dcom.sys.cisco Previous Next

#2135

From: Dan Swartzendruber
Date: Tue, 20 Aug 2002 02:39

19 lines
2252 bytes

In article <ajs8n5$hav$1@panix3.panix.com>, shore@panix.com says...
> 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.

Good points, but totally unresponsive to his statement.

Technical Details

Message-ID: <MPG.17cb75d78c196d4c98970b@news.supernews.net>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-post-01!supernews.com!news.supernews.com!not-for-mail

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> <ajs8n5$hav$1@panix3.panix.com>

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: 102702,e93f40f12aae87f4
X-Google-Attributes: gid102702,public
X-Google-Thread: 10669a,e93f40f12aae87f4
X-Google-Attributes: gid10669a,public
X-Google-Thread: 10ed20,e93f40f12aae87f4
X-Google-Attributes: gid10ed20,public
X-Google-Thread: 102e85,e93f40f12aae87f4
X-Google-Attributes: gid102e85,public
X-Google-ArrivalTime: 2002-08-19 19:40:14 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-06!sn-post-01!supernews.com!news.supernews.com!not-for-mail
From: Dan Swartzendruber <dswartz@druber.com>
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: Mon, 19 Aug 2002 22:39:08 -0400
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <MPG.17cb75d78c196d4c98970b@news.supernews.net>
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> <ajs8n5$hav$1@panix3.panix.com>
X-Newsreader: MicroPlanet Gravity v2.50
X-Complaints-To: newsabuse@supernews.com
Lines: 20

Reply to Parent Message