Opened 7 years ago

Closed 6 years ago

Last modified 5 weeks ago

#390 closed request (wontfix)

routing troubles?

Reported by: shep@… Owned by: msackett@…
Priority: tbd Milestone: ietf-080
Component: network Keywords:
Cc: My Current Location:
My MAC Address: My OS: linux

Description

Several times today I've seen some things on the internet become inaccessible.
When I debug this, I find that traceroute shows two hops and then nothing more.
The best example of this was en.wikipedia.org. But en.wikipedia.org was still accessible from other places on the Internet (where I ssh'd to and did the traceroute from there.

Even stranger, I asked someone else (via jabber) at the IETF meeting if he was seeing the same problem and he was not (traceroute was going the full distance). My traceroute attempts still showed only two hops and nothing more.

He was probably on the 802.11a network, while I was on the 802.11g network, which might explain the difference.

Change history (8)

comment:1 Changed 7 years ago by msackett@…

Component: incomingnetwork
Owner: changed from llynch@… to msackett@…
Status: newaccepted

You don't happen to have a copy of those traceroutes, do you?

comment:2 Changed 7 years ago by shep@…

Here are some traceroutes, one from each end, run pretty much simultaneously. This is to a box at home (not wikipedia like I originally reported.) These traceroutes were collected between 14:20 and 14:30 CEST (12:20 and 12:30 UT). As of 14:33 CEST I am still seeing this outage. I saw several outages like this yesterday, and several more today. This is the first I've managed to get traceroutes collected before the outage healed itself.

$ tcptraceroute -n 130.129.38.123
Selected device eth0, address 66.92.66.146, port 42935 for outgoing packets
Tracing the path to 130.129.38.123 on TCP port 80 (www), 30 hops max

1 69.3.202.53 11.359 ms 10.816 ms 8.985 ms
2 192.168.4.37 18.128 ms 13.190 ms 9.797 ms
3 63.211.168.25 13.228 ms 13.605 ms 11.874 ms
4 4.69.132.242 12.703 ms 15.307 ms 13.650 ms
5 4.69.140.90 13.323 ms 14.337 ms 12.689 ms
6 4.69.140.98 17.389 ms 19.252 ms 17.636 ms
7 4.69.137.77 86.527 ms 87.630 ms 90.075 ms
8 4.69.139.98 114.716 ms 209.383 ms 98.611 ms
9 212.113.16.110 104.622 ms 83.536 ms 81.834 ms

10 84.233.190.57 118.808 ms 118.104 ms 118.915 ms
11 84.233.190.2 127.589 ms 117.518 ms 118.597 ms
12 84.233.190.50 131.593 ms 123.923 ms 116.684 ms
13 212.23.42.173 98.909 ms 116.541 ms 133.760 ms
14 84.233.138.209 115.568 ms 117.771 ms 116.596 ms
15 195.81.119.98 148.608 ms 117.845 ms 116.614 ms
16 217.31.202.3 117.600 ms 118.500 ms 117.072 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Destination not reached
$ date -u
Tue Mar 29 12:27:38 UTC 2011

$ tcptraceroute -n 66.92.66.146
Selected device bcm0, address 130.129.38.123, port 37381 for outgoing packets
Tracing the path to 66.92.66.146 on TCP port 80 (www), 30 hops max

1 130.129.32.2 1.156 ms 1.042 ms 2.473 ms
2 82.113.59.4 2.930 ms 1.180 ms 1.163 ms
3 213.200.74.93 5.194 ms 1.290 ms 4.502 ms
4 89.149.182.101 107.140 ms 102.873 ms 112.765 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *

10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Destination not reached
$ date -u
Tue Mar 29 12:27:34 UTC 2011

comment:3 Changed 7 years ago by msackett@…

I've been looking around, but haven't noticed what might be causing this behavior. Are you still seeing this?

comment:4 in reply to:  3 Changed 7 years ago by shep@…

Replying to msackett@…:

I've been looking around, but haven't noticed what might be causing this behavior. Are you still seeing this?

I don't think I've seen this problem today (Wednesday).

comment:5 Changed 7 years ago by shep@…

happening again, during the Wednesday plenary. Once again, traceroutes from both ends (timestamps in local time zones, traceroutes run simultaneously from each end):

$ date && tcptraceroute -n 130.129.38.123
Wed Mar 30 12:40:31 EDT 2011
Selected device eth0, address 66.92.66.146, port 43333 for outgoing packets
Tracing the path to 130.129.38.123 on TCP port 80 (www), 30 hops max

1 69.3.202.53 10.484 ms 10.212 ms 8.415 ms
2 192.168.4.37 14.260 ms 14.267 ms 12.938 ms
3 63.211.168.25 12.693 ms 14.033 ms 12.969 ms
4 4.69.132.242 14.692 ms 14.306 ms 13.847 ms
5 4.69.140.90 13.384 ms 14.965 ms 12.967 ms
6 4.69.140.98 18.439 ms 18.994 ms 17.449 ms
7 4.69.137.77 86.756 ms 87.948 ms 85.210 ms
8 4.69.139.98 86.513 ms 86.949 ms 85.576 ms
9 212.113.16.110 88.505 ms 87.806 ms 87.441 ms

10 84.233.190.57 145.008 ms 118.800 ms 118.614 ms
11 84.233.190.2 140.765 ms 183.604 ms 118.758 ms
12 84.233.190.50 118.599 ms 123.557 ms 141.608 ms
13 212.23.42.173 130.691 ms 99.641 ms 100.418 ms
14 84.233.138.209 117.723 ms 116.536 ms 116.613 ms
15 195.81.119.98 117.596 ms 116.842 ms 118.623 ms
16 217.31.202.3 118.826 ms 118.485 ms 118.091 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *

$ date && tcptraceroute 66.92.66.146
Wed Mar 30 18:40:44 CEST 2011
Selected device bcm0, address 130.129.38.123, port 51556 for outgoing packets
Tracing the path to 66.92.66.146 on TCP port 80 (www), 30 hops max

1 130.129.32.2 1.620 ms 3.397 ms 0.924 ms
2 82.113.59.4 3.302 ms 3.157 ms 1.633 ms
3 xe-4-0-0.prg11.ip4.tinet.net (213.200.74.93) 2.132 ms 1.375 ms 1.529 ms
4 xe-9-1-0.was12.ip4.tinet.net (89.149.182.105) 97.991 ms 98.100 ms 98.813 ms
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *

10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *

comment:6 Changed 7 years ago by msackett@…

Do you mind stopping by the NOC during a break, or posting something in noc@… so we could try and debug this a little more real time? I'm having trouble looking into this as it seems that the condition that's causing your trouble goes away when I take a look.

comment:7 Changed 6 years ago by joelja@…

Resolution: wontfix
Status: acceptedclosed

comment:8 Changed 5 weeks ago by Rick Alfvin

Milestone: ietf-80ietf-080

Milestone renamed

Note: See TracTickets for help on using tickets.