🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dcom.sys.cisco
Article #2136

Re: How to find NAT'ed address

#2136
From: Dave Phelps
Date: Tue, 20 Aug 2002 03:17
46 lines
3393 bytes
In article <ajs8n5$hav$1@panix3.panix.com>, shore@panix.com says...
 
> 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.
 
I don't entirely disagree, so I will only mention the points that I 
disagree with you on for brevity.

NAT is indistinguishable from an attacker? I'm not sure what you mean 
there.

NAT doesn't significantly increase the cost of equipment. You may need 
more memory, but memory is cheap (unless you buy "Cisco" memory LOL). 
The router folks wrote the code for NAT because the demand, and lack of 
IP space, was there. They either had to support NAT, or put a rush on 
the IPv6 code, which I suspect wasn't near standardized at the 
introduction time of NAT.

A lot of the problems NAT introduces is because of programmers that have 
written code without regard for the OSI model. If they would have left 
IP addresses at layer 3, there wouldn't be nearly the problem that there 
is. FTP and Netmeeting are two examples.

As far as firewalling, NAT performs as a very good, cheap firewall for 
millions of hosts every day on networks without incident. For many 
people, the router performing NAT is the firewall also. If people want 
to enforce a more stingent firewall policy, then they must be prepared 
to spend the money that it takes. 

Tell me, exactly how does NAT enable users to violate firewall policy? I 
don't see how translating an internal address at the firewall somehow 
bypasses firewall restrictions.

-- 
Dave Phelps
Phone Masters Ltd.
deadspam=tippenring
Technical Details
Message-ID: <MPG.17cb70dd853f18d09898ff@news.charter.net>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!sn-xit-05!sn-xit-06!sn-post-01!supernews.com!corp.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: 102e85,e93f40f12aae87f4
X-Google-Attributes: gid102e85,public
X-Google-Thread: 102702,e93f40f12aae87f4
X-Google-Attributes: gid102702,public
X-Google-Thread: 10ed20,e93f40f12aae87f4
X-Google-Attributes: gid10ed20,public
X-Google-Thread: 10669a,e93f40f12aae87f4
X-Google-Attributes: gid10669a,public
X-Google-ArrivalTime: 2002-08-19 20:19:53 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!sn-xit-05!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!not-for-mail
From: Dave Phelps <tippenring@deadspam.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:17:58 -0500
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <MPG.17cb70dd853f18d09898ff@news.charter.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: 46