[OCCAID] IPv4 Routing question from me to IAD
James Jun
james at towardex.com
Sun Jul 30 15:29:48 EDT 2006
as far as I can tell, it's AT&T sending suboptimal MEDs (happens very often
between ATT<->Cogent,
ATT<->just_about_anyone_who_thinks_cold_potato_actually_works)
In English, it's not something we can fix, something you'll have to bring up
to Comcast or their upstream to resolve.
james
traceroute to 24.125.204.61 (24.125.204.61), 30 hops max, 40 byte packets
1 fe3-15.hr2.iad1.us.nlayer.net (69.31.31.37) 0.511 ms 1.093 ms 0.410
ms
2 g1-26.ar1.iad1.us.nlayer.net (69.31.31.197) 0.379 ms 0.271 ms 0.256
ms
3 ge-7-0-0.ar1.DCA3.gblx.net (208.51.117.125) 0.929 ms 0.402 ms 0.620
ms
4 pos7-0-0-10G.ar2.CHI2.gblx.net (67.17.105.110) 32.673 ms 32.609 ms
33.002 ms
5 gblx-gw.cgcil.ip.att.net (192.205.32.125) 45.294 ms 33.296 ms 33.412
ms
6 tbr2-p012201.cgcil.ip.att.net (12.123.6.38) 28.475 ms 28.228 ms
28.628 ms
MPLS Label=32144 CoS=0 TTL=1 S=1
7 tbr2-cl3641.phlpa.ip.att.net (12.122.10.94) 28.291 ms 28.303 ms
28.642 ms
MPLS Label=31392 CoS=0 TTL=1 S=1
8 tbr1-cl9.wswdc.ip.att.net (12.122.2.85) 28.989 ms 29.309 ms 29.354 ms
MPLS Label=32381 CoS=0 TTL=1 S=1
9 12.123.8.25 (12.123.8.25) 28.189 ms 28.016 ms 28.014 ms
10 12.118.122.14 (12.118.122.14) 30.256 ms 30.237 ms 30.254 ms
11 te-9-1-ur02.staplesmllrd.va.richmond.comcast.net (68.86.172.93) 31.346
ms 30.700 ms 30.172 ms
12 ge-0-2-ubr01.staplesmllrd.va.richmond.comcast.net (68.86.175.110)
30.432 ms 30.162 ms 30.515 ms
13 *^C
_____
From: occaid-bounces at cnacs.occaid.org
[mailto:occaid-bounces at cnacs.occaid.org] On Behalf Of Lists
Sent: Sunday, July 30, 2006 11:13 AM
To: occaid
Subject: RE: [OCCAID] IPv4 Routing question from me to IAD
Oops.. Meant to include my tracert
Tracing route to occaid.g1-36.ar1.iad1.us.nlayer.net [69.31.31.102] over a
maximum of 30 hops:
1 2 ms <1 ms 1 ms linksys.ropeguru.int [192.168.1.1]
2 9 ms 8 ms 7 ms
c-3-0-ubr01.staplesmllrd.va.richmond.comcast.net [73.141.96.1]
3 9 ms 7 ms *
GE-6-24-ur02.staplesmllrd.va.richmond.comcast.net [68.86.175.109]
4 9 ms 9 ms 9 ms
te-1-3-ar01.staplesmllrd.va.richmond.comcast.net [68.86.172.94]
5 12 ms 11 ms 11 ms 12.118.122.13
6 19 ms 12 ms 16 ms tbr1-p010401.wswdc.ip.att.net [12.123.8.26]
7 11 ms 9 ms 11 ms sar1-a300s3.wswdc.ip.att.net [12.123.8.105]
8 38 ms 39 ms 37 ms att-gw.washdc.gblx.net [192.205.32.42]
9 39 ms 37 ms 37 ms nlayer.ge-7-0-0.ar1.DCA3.gblx.net
[208.51.117.126]
10 40 ms 39 ms 39 ms occaid.g1-36.ar1.iad1.us.nlayer.net
[69.31.31.102]
Trace complete.
_____
From: Lists
Sent: Sunday, July 30, 2006 9:10 AM
To: occaid
Subject: [OCCAID] IPv4 Routing question from me to IAD
Good morning all,
Been quite a while since I have posted here as my Linksys router died and
I am just getting back up and online with my tunnel. Very happy that it is
even still up and running.
My question. When I originally had my tunnel changed from EWR to IAD I was
seen a solid 9ms ping time. Now that I have had the opportunity to set
everything back up again, I am seeing 39ms to IAD from the same IP with
Comcast I have always had. Seems there has been a routing change and I hop
off AT&T to GLBX for two hops before hitting nlayer. The hop off AT&T to
GLBX takes a 21ms jump which is what seems to be the additional latency. I
know that neither of these belong to Towardex, but could there be some sort
of route table issue?
I know 39ms really isn't that bad, but was just really surprised at the
increase.
Thanks,
Robert Webb
PS - What are the contact emails now for end point changes and dns changes?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.twdx.net/pipermail/occaid/attachments/20060730/7bc9e276/attachment.html
More information about the Occaid
mailing list