[aklug] Re: Alaska peering

Royce Williams writes:
> If the latter, I think that this is useful in the general
> geek sense, but you'd be right if you're saying that it's not
> directly Linux-related. But at least it's technical. :-)
> I'd be happy to kill the thread if folks are thinking that
> it's too OT.
>
> > http://tlms.pastebin.com/jBkG9hAy
>
> Good info - that's what we needed; thanks, Thomas!
>
> You're coming from GCI space, so I would expect these
> traceroutes, when adjusted for wireless performance, to
> reflect GCI's peering.
>
> 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 15=
00
 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
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Tue Jun 8 16:16:08 2010