Re: How to find NAT'ed address

Article View: comp.dcom.sys.cisco

Article #2143

Back to comp.dcom.sys.cisco Previous Next

#2143

From: Dave Phelps
Date: Fri, 23 Aug 2002 22:03

28 lines
2563 bytes

In article <ak58md$stl$1@panix2.panix.com>, shore@panix.com says...
> In article <MPG.17cf59442d7d34de989902@news.charter.net>,
> 
> ability to receive incoming telephone calls.  You've also got
> the ability to run unauthorized servers behind the firewall/
> NAT and the ability to run unauthorized p2p applications 
> behind the firewall/NAT.

I see. So if I fired up a server instead of my IP phone using a 
predetermined port number, how would I receive phone calls? I would be 
taking my phone out of service, because all requests would go to the 
server instead of my phone.

Alternatively, all calls can relay thru the call manager, and the 
firewall will allow inbound H.323 traffic to reach the call manager 
only, which prevents me from making a server public using that security 
hole (maybe bad design would be a better term than "security hole")
altogether.

Notably, without NAT, the same problem still exists. Even if I have an 
organization that uses exclusively public IP's, I still have to open the 
firewall for the H.323 traffic, where someone could potentially install 
a server instead of taking their phone calls.

-- 
Dave Phelps
Phone Masters Ltd.
deadspam=tippenring

Technical Details

Message-ID: <MPG.17d04343f28c6eb8989909@news.charter.net>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!syros.belnet.be!news.belnet.be!isdnet!sn-xit-02!sn-xit-06!sn-post-01!supernews.com!corp.supernews.com!not-for-mail

References:

<54c48ac0.0208181042.79852937@posting.google.com> <MPG.17ccc360a78e8145989900@news.charter.net> <ak0dap$bt6$1@panix2.panix.com> <MPG.17cf59442d7d34de989902@news.charter.net> <ak58md$stl$1@panix2.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: 10ed20,e93f40f12aae87f4
X-Google-Attributes: gid10ed20,public
X-Google-Thread: 102702,e93f40f12aae87f4
X-Google-Attributes: gid102702,public
X-Google-Thread: 10669a,e93f40f12aae87f4
X-Google-Attributes: gid10669a,public
X-Google-Thread: 102e85,e93f40f12aae87f4
X-Google-Attributes: gid102e85,public
X-Google-ArrivalTime: 2002-08-23 15:04:42 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!syros.belnet.be!news.belnet.be!isdnet!sn-xit-02!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: Fri, 23 Aug 2002 17:03:02 -0500
Organization: Posted via Supernews, http://www.supernews.com
Message-ID: <MPG.17d04343f28c6eb8989909@news.charter.net>
References: <54c48ac0.0208181042.79852937@posting.google.com> <MPG.17ccc360a78e8145989900@news.charter.net> <ak0dap$bt6$1@panix2.panix.com> <MPG.17cf59442d7d34de989902@news.charter.net> <ak58md$stl$1@panix2.panix.com>
X-Newsreader: MicroPlanet Gravity v2.50
X-Complaints-To: newsabuse@supernews.com
Lines: 28

Reply to Parent Message