[39152] in North American Network Operators' Group

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

Is this normal?

daemon@ATHENA.MIT.EDU (Larry Diffey)
Wed Jun 27 02:29:47 2001

Message-ID: <007001c0fed3$6b44cf00$6401a8c0@difster>
From: "Larry Diffey" <ldiffey@technologyforward.com>
To: <nanog@merit.edu>
Date: Tue, 26 Jun 2001 23:35:55 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_006D_01C0FE98.BE9E3FA0"
Errors-To: owner-nanog-outgoing@merit.edu


This is a multi-part message in MIME format.

------=_NextPart_000_006D_01C0FE98.BE9E3FA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I've only been lurking here for a couple of days and I hope this isn't =
an inappropriate question for this group.  No flames please if I =
shouldn't have posted this (or for the double negative); a good stern =
warning will do just fine. :-)   The reason that I'm addressing this =
group is that I'm trying to get a perspective on provider policy and how =
decisions are made to do such things.  If it's not a conscious decision =
but the result of um er human error, what mechanisms are in place; or =
should be in place in order to correct such issues.  So here it is:

I'm wondering if what I'm seeing in this trace route is normal provider =
behavior (I haven't seen this happen before now).  My provider is @home =
and when ever I do a trace route I get the following results:

  1   211 ms    20 ms    20 ms  cr1-hfc10.alsv1.occa.home.net =
[24.0.216.1]
  2    10 ms    20 ms    40 ms  r1-ge2-0.alsv1.occa.home.net =
[24.1.160.1]
  3   180 ms    20 ms    30 ms  10.0.242.77
  4    80 ms    50 ms    20 ms  10.0.242.73
  5    30 ms   291 ms    20 ms  c1-pos5-0.anhmca1.home.net [24.7.74.73]
  ... rest of results omitted for brevity.

As you can see, the third and fourth hop are advertising 10's and I =
wouldn't think a provider would want traffic passing through a private =
address space.  Also, this is happening just as the traffic is leaving =
one facility and going to another (I don't know if that means anything). =
 If you're interested alsv is Aliso Viejo and anhmca is Anaheim (both in =
Orange County, CA).  I could be wrong but I'm fairly certain this has =
just been happening for the last few weeks.  Maybe I  never noticed =
before.

I'd call @home about it but I know I'd get the run around and it would =
take 5 hours on the phone for someone just to tell me it's none of my =
business.

Regards,

Larry Diffey

P.S.  NANOG Range Day should include pictures of various vendor =
equipment.  Pick whatever is frustrating you at the moment.




------=_NextPart_000_006D_01C0FE98.BE9E3FA0
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 http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2462.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>I've only been lurking here for a couple of days and =
I hope=20
this isn't an inappropriate question for this group.&nbsp; No flames =
please if I=20
shouldn't have posted this (or for the double negative); a good stern =
warning=20
will do just fine. :-) &nbsp; The reason that I'm addressing this group =
is that=20
I'm trying to get a perspective on provider policy&nbsp;and =
how&nbsp;decisions=20
are made to do such things.&nbsp; If it's not a conscious decision but =
the=20
result of um er human error, what mechanisms are in place; or should be =
in place=20
in order to correct such issues.&nbsp; So here it is:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I'm wondering if what I'm seeing in this trace route =
is normal=20
provider behavior (I haven't seen this happen before now).&nbsp; My =
provider is=20
@home and when ever I do a trace route I get the following =
results:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>&nbsp; 1&nbsp;&nbsp; 211 ms&nbsp;&nbsp;&nbsp; 20=20
ms&nbsp;&nbsp;&nbsp; 20 ms&nbsp; cr1-hfc10.alsv1.occa.home.net=20
[24.0.216.1]<BR>&nbsp; 2&nbsp;&nbsp;&nbsp; 10 ms&nbsp;&nbsp;&nbsp; 20=20
ms&nbsp;&nbsp;&nbsp; 40 ms&nbsp; r1-ge2-0.alsv1.occa.home.net=20
[24.1.160.1]<BR>&nbsp; 3&nbsp;&nbsp; 180 ms&nbsp;&nbsp;&nbsp; 20=20
ms&nbsp;&nbsp;&nbsp; 30 ms&nbsp; 10.0.242.77<BR>&nbsp; =
4&nbsp;&nbsp;&nbsp; 80=20
ms&nbsp;&nbsp;&nbsp; 50 ms&nbsp;&nbsp;&nbsp; 20 ms&nbsp; =
10.0.242.73<BR>&nbsp;=20
5&nbsp;&nbsp;&nbsp; 30 ms&nbsp;&nbsp; 291 ms&nbsp;&nbsp;&nbsp; 20 =
ms&nbsp;=20
c1-pos5-0.anhmca1.home.net [24.7.74.73]<BR>&nbsp; ... rest of results =
omitted=20
for brevity.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>As you can see, the third and fourth hop are =
advertising 10's=20
and I wouldn't think a provider would want traffic passing through a =
private=20
address space.&nbsp; Also, this is happening just as the traffic is =
leaving one=20
facility and going to another (I don't know if that means =
anything).&nbsp; If=20
you're interested alsv is Aliso Viejo and anhmca is Anaheim (both in =
Orange=20
County, CA).&nbsp; I could be wrong but I'm fairly certain this has just =
been=20
happening for the last few weeks.&nbsp; Maybe I&nbsp; never noticed=20
before.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I'd call @home about it but I know I'd get the run =
around and=20
it would take 5 hours on the phone for someone just to tell me it's none =
of my=20
business.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Regards,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Larry Diffey</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>P.S.&nbsp; NANOG Range Day should include pictures =
of various=20
vendor equipment.&nbsp; Pick whatever is frustrating you at the=20
moment.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_006D_01C0FE98.BE9E3FA0--


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