[149919] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Common operational misconceptions

daemon@ATHENA.MIT.EDU (Josh Hoppes)
Thu Feb 16 20:17:39 2012

In-Reply-To: <4F3DA93A.3060904@necom830.hpcl.titech.ac.jp>
Date: Thu, 16 Feb 2012 19:16:36 -0600
From: Josh Hoppes <josh.hoppes@gmail.com>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

2012/2/16 Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>:
> Andreas Echavez wrote:
>> *How NAT breaks end-to-end connectivity (fun one..., took me
>> =A0hours to explain to an old boss why doing NAT at the ISP level
>> =A0was horrendously wrong)
>
> That's another misconception.
>
> While NAT breaks the end to end connectivity, it can be
> restored by end systems by reversing translations by NAT,
> if proper information on the translations are obtained
> through some protocol such as UPnP.
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0Masataka Ohta
>

UPnP can scale to about the size of an average home use, but it's
worth jack squat at the ISP level when NAT44 comes into play. UPnP is
not an ISP grade solution, it's a consumer one.


home help back first fref pref prev next nref lref last post