[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Private use of non-RFC1918 IP space

On Mon, 02 Feb 2009 12:20:25 EST, "D'Arcy J.M. Cain" said:
> On Mon, 02 Feb 2009 18:03:57 +0100 (CET)
> sthaug at nethelp.no wrote:
> > > What reason could you possibly have to use non RFC 1918 space on a
> > > closed network?  It's very bad practice - unfortunately I do see it done
> > > sometimes....
> > 
> > There are sometimes good reasons to do this, for instance to ensure
> > uniqueness in the face of mergers and acquisitions.
> How does that help?  If you are renumbering due to a merger, couldn't
> you just agree on separate private space just as easily?

They don't renumber, they end up just double-NAT or triple-NAT betweem the
merged units.  I think one poor soul posted here that they had
quintuple-NAT'ing going on due to a long string of mergers....

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20090202/c845cc84/attachment.bin>