Article View: comp.dcom.sys.cisco
Article #2142Re: How to find NAT'ed address
From: Melinda Shore
Date: Fri, 23 Aug 2002 12:09
Date: Fri, 23 Aug 2002 12:09
23 lines
2686 bytes
2686 bytes
In article <MPG.17cf59442d7d34de989902@news.charter.net>,
Dave Phelps <tippenring@deadspam.com> wrote:
>Using your example, you are not enabling anyone to violate firewall
>policy. Installing the Micro^H^H^H^H^HSplortsoft product simply fixes
>the necessary translations to trick the IP PBX software into thinking it
>has public IP's. You still have to create a rule to allow the traffic
>thru the firewall.
Splortsort's stuff (and STUN and TURN and most firewall/NAT
workarounds) assume that all outgoing traffic is permitted
unless you specify otherwise. So, in order to accept incoming
connections, someone puts a relay outside the firewall/NAT,
sends a request to it and asks it to relay for them, establishes
a connection to it on the chosen port, and then the relay forwards
all incoming traffic matching a particular pattern (say,
the standard 5-tuple) to that connection. You've now got the
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.
--
Melinda Shore - Software longa, hardware brevis - shore@panix.com
If you send me harassing email, I'll probably post it
Technical Details
Message-ID:
<ak58md$stl$1@panix2.panix.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news.stealth.net!news.stealth.net!panix!panix2.panix.com!not-for-mailReferences:
<54c48ac0.0208181042.79852937@posting.google.com> <MPG.17ccc360a78e8145989900@news.charter.net> <ak0dap$bt6$1@panix2.panix.com> <MPG.17cf59442d7d34de989902@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: 102e85,e93f40f12aae87f4 X-Google-Attributes: gid102e85,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-ArrivalTime: 2002-08-23 05:13:33 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news.stealth.net!news.stealth.net!panix!panix2.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: 23 Aug 2002 08:09:49 -0400 Organization: PANIX -- Public Access Networks Corp. Lines: 23 Message-ID: <ak58md$stl$1@panix2.panix.com> References: <54c48ac0.0208181042.79852937@posting.google.com> <MPG.17ccc360a78e8145989900@news.charter.net> <ak0dap$bt6$1@panix2.panix.com> <MPG.17cf59442d7d34de989902@news.charter.net> NNTP-Posting-Host: panix2.panix.com X-Trace: reader1.panix.com 1030104589 12929 166.84.1.2 (23 Aug 2002 12:09:49 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Fri, 23 Aug 2002 12:09:49 +0000 (UTC)