[33109] in North American Network Operators' Group
Re: RFC1918 addresses to permit in for VPN?
daemon@ATHENA.MIT.EDU (Simon Lyall)
Fri Dec 29 15:05:17 2000
Date: Sat, 30 Dec 2000 09:02:38 +1300 (NZDT)
From: Simon Lyall <simon.lyall@ihug.co.nz>
To: <nanog@merit.edu>
In-Reply-To: <20001229134801.B275@noc.untraceable.net>
Message-ID: <Pine.LNX.4.30.0012300853170.639-100000@boggle.ihug.co.nz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On Fri, 29 Dec 2000, Andrew Brown wrote:
> they might actually have reverse dns set up for those addresses, but
> i, of course, have no idea what server to ask about it. :)
Perhaps IANA could set up reverses for those networks to discourage people
from using them? I would guess that a few reverses with names like
192-168-1-1.danger.stupid.idiot.network.admin in a traceroute would
quickly sort things out.
One of the companies we work with has 192.168 address for some of the
radius servers we have to talk to, we are directly connected to them so
it's not a big pain but it's just so ugly.
--
Simon Lyall. | Newsmaster | Work: simon.lyall@ihug.co.nz
Senior Network/System Admin | | Home: simon@darkmere.gen.nz
ihug, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz
