[33194] in North American Network Operators' Group
RE: RFC1918 addresses to permit in for VPN?
daemon@ATHENA.MIT.EDU (Deron J. Ringen)
Tue Jan 2 13:56:33 2001
From: "Deron J. Ringen" <djr@eng.bellsouth.net>
To: <mdevney@teamsphere.com>, "Stephen Stuart" <stuart@mfnx.net>
Cc: <jlewis@jasonlewis.net>, <nanog@merit.edu>
Date: Tue, 2 Jan 2001 13:49:46 -0500
Message-ID: <NEBBLOMNADAAGMHJKLDCCEDFCHAA.djr@eng.bellsouth.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.4.21.0101010143500.10993-100000@core.teamplay.net>
Errors-To: owner-nanog-outgoing@merit.edu
> Using RFC1918 space also gets you an IP range where the outside world has
> no route to it -- Sorry, but no packets are not getting there, ergo no way
> to hack.
.
.
> At that point, just by use of simple routing, you've effectively
> eliminated 100% of attacks from the outside, and you only have to worry
> about inside. The front door is secure, now work on the back door.
>
I know that this thread as escalated unrestrained, however this is the
original point that I attempted to make.
...djr...
