[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Fri Dec 10 01:57:08 2004 -->
- <!--x-from-r13: xnobbz ng tngrpu.rqh (Quevf Dvpxre) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: Pine.LNX.4.44.0412072308310.13794-[email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] [OT] Voicepulse question -->
- <li><em>date</em>: Fri Dec 10 01:57:08 2004</li>
- <li><em>from</em>: kaboom at gatech.edu (Chris Ricker)</li>
- <li><em>in-reply-to</em>: <<a href="msg00407.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00311.html">[email protected]</a>> <<a href="msg00324.html">[email protected]</a>> <<a href="msg00407.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] [OT] Voicepulse question</li>
> > I agree. IP addresses used with NAT are always private ... 10.0.0.0=20
> > /172.16.0.0 / 192.168.0.0
> > No point using "public" adddresses with NAT. In theory, however one could=
> =20
> > do so.
>
> It's actually being done in practice in several very significant
> instances. As far as "no point using", I don't know that I can argue
> one way or the other or both.
>
> I know of several very large networks (an entire /16 for one)
> that "went NAT". It was a fully assigned portable /16 address space
> (one of the old class B spaces) and they decided, for one reason or
> another (mine is not to judge), they wanted to no longer be "routable"
> and placed the entire /16 behind one or more NAT devices. They then
> withdrew the BGP advertisement for that address space, so it no longer
> routes (or, at least, shouldn't). Now, "no point", I can't say. I don't
> know what they point for WANTING NAT might be. Once you take it NAT
> though, you still probably want to keep those public addresses just to
> avoid the pain of renumbering an address space of 65,536 addresses.
Another usage of NAT with publically routable addresses is when you have a
situation like companies that are merging two different routable address
spaces into one and they don't want to renumber either existing network....
later,
chris
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00311" href="msg00311.html">[ale] [OT] Voicepulse question</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
<li><strong><a name="00324" href="msg00324.html">[ale] [OT] Voicepulse question</a></strong>
<ul><li><em>From:</em> sriad at uab.edu (Aditya Srinivasan)</li></ul></li>
<li><strong><a name="00407" href="msg00407.html">[ale] [OT] Voicepulse question</a></strong>
<ul><li><em>From:</em> mhw at wittsend.com (Michael H. Warfield)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00420.html">[ale] PAM_Tally oddness</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00422.html">[ale] Make RAID 1 during install</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00435.html">[ale] [OT] Voicepulse question</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00335.html">[ale] [OT] Voicepulse question</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00421"><strong>Date</strong></a></li>
<li><a href="threads.html#00421"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>