[aklug] Re: Alaska peering

Nah. that's just a crappy tracepath on my crappy firewall.

 2 [cmts]
 3 209.165.188.81 6.457 ms 6.695 ms 6.896 ms
 4 209.165.128.34 9.200 ms 6.803 ms 8.839 ms
 5 209.165.128.9 7.903 ms 6.329 ms 7.516 ms
 6 209.165.128.31 9.579 ms 6.795 ms 7.152 ms
 7 209.165.168.198 11.416 ms 10.470 ms 8.814 ms
 8 216.152.176.226 9.248 ms 9.244 ms 9.744 ms
 9 216.152.176.1 9.638 ms !<10> 9.281 ms !<10> 9.042 ms !<10>

> -----Original Message-----
> From: aklug-bounce@aklug.org [mailto:aklug-bounce@aklug.org]
> On Behalf Of Royce Williams
> Sent: Tuesday, June 08, 2010 4:23 PM
> To: aklug@aklug.org
> Subject: [aklug] Re: Alaska peering
>
> Leif Sawyer wrote, on 6/8/2010 4:15 PM:
> >> All that we still need is a GCI-MTA test, then ... and
> preferably not
> >> from a Clearwire node, as the wireless performance makes
> it hard to
> >> discern big changes in the hops.
> >
> > How about from behind my cablemodem?
> >
> > leif@gw:~$ tracepath 216.152.176.1
> > 1: gw.denali.net (69.178.4.20)
> 0.474ms pmtu 1500
> > 1: (CMTS - no ICMP support)
> > 2: 81-188-165-209.gci.net (209.165.188.81) 21.349ms
> > 3: 34-128-165-209.gci.net (209.165.128.34) 8.670ms
> > 4: 9-128-165-209.gci.net (209.165.128.9) 10.749ms
> > 5: 31-128-165-209.gci.net (209.165.128.31) 26.438ms
> > 6: 198-168-165-209.static.gci.net (209.165.168.198) 22.689ms
> > 7: 216.152.176.226 (216.152.176.226)
> 36.457ms asymm 8
> > 8: ns1.mtaonline.net (216.152.176.1)
> 17.850ms !H
> > Resume: pmtu 1500
>
> Is there some other traffic going on that would make your
> third hop have a 21ms delay?
>
> This looks like GCI and MTA are peering. There's not a big
> spike in between, and no obvious Seattle bump.
>
> Royce
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org> with
> 'unsubscribe' in the message body.
>
>
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Tue Jun 8 16:24:32 2010