[71952] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: The use of .0/.255 addresses.

daemon@ATHENA.MIT.EDU (Chris Ranch)
Sat Jun 26 19:42:21 2004

From: Chris Ranch <CRanch@Affinity.com>
To: 'Jonathan McDowell' <noodles@earth.li>, nanog@nanog.org
Date: Sat, 26 Jun 2004 19:41:17 -0400
Errors-To: owner-nanog-outgoing@merit.edu


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C45BD7.1312C530
Content-Type: text/plain;
	charset="iso-8859-1"

I see traffic from this last IP address octet all the time from prefixes of
length less than /24.  Use of these host id's when the prefix length is
greater than or equal to /24 is illegal.  So if that's your case, I'd
suggest not doing it.

If that's not the case, look for over-zealous or incorrect filters in the
path.  I saw this situation once before.  There was a border ingress filter
with a typo in it...

Chris

> Various people I've asked about this have said they wouldn't 
> use the .0
> or .255 addresses themselves, though couldn't present any 
> concrete info
> about why not; my experience above would seem to suggest a 
> reason not to
> use them.

------_=_NextPart_001_01C45BD7.1312C530
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2657.73">
<TITLE>RE: The use of .0/.255 addresses.</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I see traffic from this last IP address octet all the =
time from prefixes of length less than /24.&nbsp; Use of these host =
id's when the prefix length is greater than or equal to /24 is =
illegal.&nbsp; So if that's your case, I'd suggest not doing =
it.</FONT></P>

<P><FONT SIZE=3D2>If that's not the case, look for over-zealous or =
incorrect filters in the path.&nbsp; I saw this situation once =
before.&nbsp; There was a border ingress filter with a typo in =
it...</FONT></P>

<P><FONT SIZE=3D2>Chris</FONT>
</P>

<P><FONT SIZE=3D2>&gt; Various people I've asked about this have said =
they wouldn't </FONT>
<BR><FONT SIZE=3D2>&gt; use the .0</FONT>
<BR><FONT SIZE=3D2>&gt; or .255 addresses themselves, though couldn't =
present any </FONT>
<BR><FONT SIZE=3D2>&gt; concrete info</FONT>
<BR><FONT SIZE=3D2>&gt; about why not; my experience above would seem =
to suggest a </FONT>
<BR><FONT SIZE=3D2>&gt; reason not to</FONT>
<BR><FONT SIZE=3D2>&gt; use them.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C45BD7.1312C530--

home help back first fref pref prev next nref lref last post