[34992] in North American Network Operators' Group
Re: rfc 1918?
daemon@ATHENA.MIT.EDU (Rancken)
Fri Feb 23 04:50:39 2001
Message-ID: <013201c09d7e$9b4e1640$5313d0d1@atlantic.net>
From: "Rancken" <rancken@atlantic.net>
To: <nanog@merit.edu>
Date: Fri, 23 Feb 2001 04:52:51 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_012B_01C09D54.79B395C0"
Errors-To: owner-nanog-outgoing@merit.edu
This is a multi-part message in MIME format.
------=_NextPart_000_012B_01C09D54.79B395C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
On Thursday, February 22, 2001 10:14 PM, Valdis.Kletnieks@vt.edu =
(Valdis Kletnieks) wrote:
That's probably optional. But if you have the router resources to do =
it.
every little bit helps. You probably should filter and log it, to find =
out
why one of your hosts is trying to send to a 1918 address outside your
site - if you're not using 1918 space, it shouldn't happen, and if you =
ARE
using it, the packet should have ended up inside your net, not on your
border router.
Which is quite true, but there are a lot of people out there still using =
hubs, which (along with improperly configured NATs) probably explains =
the origins of a lot of this traffic. Which brings me to my point - =
some of us are actually grateful for having our Private (pun intended) =
packets filtered while we were setting up a network.
John T. Rancken II
Rancken@Atlantic.net (which is my isp, not where I work :).
------=_NextPart_000_012B_01C09D54.79B395C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3019.2500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>On</FONT><FONT face=3DArial =
size=3D2><FONT=20
size=3D1> Thursday, February 22, 2001 10:14 PM, <A=20
href=3D"mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</A> =
(Valdis=20
Kletnieks) wrote:</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT =
size=3D1></FONT></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2><FONT size=3D1>That's probably =
optional. But if=20
you have the router resources to do it.<BR>every little bit helps. =
You=20
probably should filter and log it, to find out<BR>why one of your hosts =
is=20
trying to send to a 1918 address outside your<BR>site - if you're not =
using 1918=20
space, it shouldn't happen, and if you ARE<BR>using it, the packet =
should have=20
ended up inside your net, not on your<BR>border =
router.<BR></FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Which is quite true, but there =
are a lot of=20
people out there still using hubs, which (along with improperly =
configured NATs)=20
probably explains the origins of a lot of this traffic. Which =
brings me to=20
my point - some of us are actually grateful for having our Private =
(pun=20
intended) packets filtered while we were setting up a=20
network.</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2>John T. Rancken =
II</FONT></FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><A=20
href=3D"mailto:Rancken@Atlantic.net">Rancken@Atlantic.net</A> (which is =
my isp,=20
not where I work :).</FONT></DIV></FONT></BODY></HTML>
------=_NextPart_000_012B_01C09D54.79B395C0--
