| Can't directly connect to 81.223.20.173, but works w/proxy The IP address is for packman.inode.at, which is a software repository for openSUSE Linux. Normally I use my package manager to connect, but the site is browsable. The problem is that I cannot connect directly through Earthlink, not even using the IP address, but can connect through a proxy; so it's not a DNS issue, and the site is definitely up.
The traceroute:
traceroute to 81.223.20.173 (81.223.20.173), 30 hops max, 40 byte packets using UDP
1 10.0.0.1 (10.0.0.1) 1.012 ms 0.151 ms 0.131 ms
2 192.168.1.1 (192.168.1.1) 0.540 ms 0.485 ms 0.459 ms
3 user-11fag01.dsl.mindspring.com (66.245.64.1) 42.829 ms 44.015 ms 45.290 ms
4 209.165.97.65 (209.165.97.65) 101.426 ms 101.084 ms 103.071 ms
5 gi10-0.860.border1.rap.ord.transedge.com (216.217.0.132) 135.176 ms 135.601 ms 137.310 ms
6 * * *
7 * * *
8 * * *
9 gi5-0.410.border1.rap.atl.transedge.com (216.217.0.181) 72.304 ms 72.391 ms 74.023 ms
10 * * *
11 unassigned.transedge.com (216.217.2.61) 87.523 ms 91.070 ms 90.777 ms
12 * * *
13 gi5-0.410.border1.rap.atl.transedge.com (216.217.0.181) 106.317 ms 110.983 ms 110.131 ms
14 * * *
15 unassigned.transedge.com (216.217.2.61) 119.701 ms 120.443 ms 121.897 ms
16 * * *
17 gi5-0.410.border1.rap.atl.transedge.com (216.217.0.181) 144.587 ms 145.554 ms 144.519 ms
18 * * *
19 unassigned.transedge.com (216.217.2.61) 123.948 ms 124.567 ms 126.272 ms
20 * * *
21 gi5-0.410.border1.rap.atl.transedge.com (216.217.0.181) 120.961 ms 121.837 ms 122.832 ms
22 * * *
23 unassigned.transedge.com (216.217.2.61) 111.321 ms 112.183 ms 112.884 ms
24 * * *
25 gi5-0.410.border1.rap.atl.transedge.com (216.217.0.181) 110.465 ms 111.824 ms 112.678 ms
26 * * *
27 unassigned.transedge.com (216.217.2.61) 118.755 ms 120.149 ms 120.892 ms
28 * * *
29 gi5-0.410.border1.rap.atl.transedge.com (216.217.0.181) 122.020 ms 122.297 ms 122.561 ms
30 * * *
This is the second time this problem has occurred. The first time, about a month ago, by some miracle I got a tech support person who actually listened to what I said, let me send him the traceroute, and forwarded the problem to the network people. It was fixed by the next day, and worked fine until last night. When I called again last night, I was not so lucky, and got one of those techs unable to do anything but follow a script. I refused to back down and supposedly the problem has been reported to the network people, but frankly, I'm not so sure he wasn't just saying that to get me off the phone.
So, in anticipation of having to call again, can anyone give me any advice as to what to say so I don't get the brushoff again? Any ideas as to why the problem would recur? The traceroute from last night is identical to the one from a month ago--the packets end up bouncing between the same two servers. And is there any way to contact Earthlink's network people directly with this kind of information instead of having to go through low-level tech support who don't know anything and can't do anything? |
|
 Doctor OldsI Need A Remedy For What's Ailing Me.Premium,VIP
join:2001-04-19
1970 442 W30
kudos:18 | It works here from BBR:
And it works from a Earthlink/Covad line here:
tracert packman.inode.at
Tracing route to packman.inode.at [81.223.20.173]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 192.168.1.1
3 15 ms 14 ms 13 ms h-66-167-51-1.atlngahp.dynamic.covad.net [66.167.51.1]
4 14 ms 14 ms 13 ms 192.168.1.5
5 30 ms 28 ms 29 ms 67.100.36.3-ge3.4-atln-osr2-atlanta.covad.com [67.100.36.3]
6 29 ms 28 ms 28 ms 67.100.37.203-ge3.6-miat-osr2-miami.covad.com [67.100.37.203]
7 49 ms 29 ms 29 ms ip65-47-56-153.z56-47-65.customer.algx.net [65.47.56.153]
8 46 ms 29 ms 29 ms 216.156.15.25.ptr.us.xo.net [216.156.15.25]
9 64 ms 63 ms 63 ms vb1901.rar3.atlanta-ga.us.xo.net [216.156.0.229]
10 66 ms 64 ms 66 ms te-11-0-0.rar3.washington-dc.us.xo.net [207.88.12.10]
11 64 ms 63 ms 63 ms te-3-0-0.rar3.nyc-ny.us.xo.net [207.88.12.73]
12 148 ms 144 ms 146 ms ae0d0.cir1.london2-eng.uk.xo.net [207.88.13.201]
13 153 ms 155 ms 155 ms uk-lon01a-ri1-ge-1-0-0.aorta.net [195.66.224.89]
14 173 ms 177 ms 178 ms uk-lon01b-rd1-xe-7-1-0.aorta.net [84.116.134.37]
15 182 ms 183 ms 214 ms at-vie15a-rd1-xe-2-0-0.aorta.net [84.116.130.254]
16 191 ms 164 ms 166 ms at-vie-xion-pe02-vl-2051.upc.at [84.116.229.2]
17 172 ms 171 ms 173 ms at-vie-xion-pe01-vl-2052.upc.at [84.116.228.197]
18 176 ms 174 ms 176 ms packman.inode.at [81.223.20.173]
Trace complete.
--
What’s the point of owning a supercar if you can’t scare yourself stupid from time to time? |
|
| It's still not working from here; traceroute is the same. I've called Earthlink support twice since posting, and all they tell me is that the problem was escalated, but they haven't had an update from their network people. Is there anything else I can do to get them to act on this? |
|
Doctor OldsI Need A Remedy For What's Ailing Me.Premium,VIP
join:2001-04-19
1970 442 W30
kudos:18 | It is called a "routing loop". Earthlink needs to contact the transedge.com NOC or use another route.
»www.exit109.com/~jeremy/news/pro···ute.html
quote:
Sometimes you might see a route start “looping” back and forth between two routers, until the 30-hop limit is reached. This is a routing loop. This usually means that one router has lost communication (BGP) with another, and thus has dropped that route. Since the router has lost the route it needs, it sends the packet back where it came from, thinking maybe that is the best route. That router knows better and sends it back to the other one, over and over. Here's an example of a loop:
14 hou-core-03.inet.qwest.net (205.171.5.146) 165.484 ms 164.335 ms 175.928 ms
15 hou-core-02.inet.qwest.net (205.171.23.5) 162.291 ms 172.713 ms 171.532 ms
16 kcm-core-01.inet.qwest.net (205.171.5.201) 212.967 ms 193.454 ms 199.457 ms
17 dal-core-01.inet.qwest.net (205.171.5.203) 206.296 ms 212.383 ms 189.592 ms
18 kcm-core-01.inet.qwest.net (205.171.5.201) 210.201 ms 225.674 ms 208.124 ms
19 dal-core-01.inet.qwest.net (205.171.5.203) 189.089 ms 201.505 ms 201.659 ms
20 kcm-core-01.inet.qwest.net (205.171.5.201) 334.19 ms 320.39 ms 245.182 ms
21 dal-core-01.inet.qwest.net (205.171.5.203) 218.519 ms 210.519 ms 246.635 ms
More info.
»en.wikipedia.org/wiki/Routing_loop_problem
--
What’s the point of owning a supercar if you can’t scare yourself stupid from time to time? |
|
| Thanks for the explanation; at least now I know the technical term to use next time I call Earthlink.
As far as Earthlink needing to contact transedge.com to fix it, well, according to WHOIS, transedge.com is Earthlink. If you go to www.transedge.com and click on the "Contact Us" link at the bottom, it takes you www.earthlinkbusiness.com. That's one of the reasons I'm finding their stonewalling so frustrating. |
|
