Tickets - Tunnel Down in Chicago :: SixXS - IPv6 Deployment & Tunnel Broker

Ticket ID: SIXXS #14976165
Ticket Status: User

PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)

Tunnel Down in Chicago

Shadow Hawkins on Monday, 07 March 2016 22:18:31

T17978 uschi02 - Your.Org, Inc. Can't reach your end of tunnel. Appears to be problem within Your.Org infrastructure. My end of the tunnel is a Cisco 1811 66.92.168.157 To 216.14.98.22 For 2001:4978:F:1E3::1 Traceroute from my router to tunnel destination #trace 216.14.98.22 Type escape sequence to abort. Tracing the route to sixxs.cx01.chi.bb.your.org (216.14.98.22) VRF info: (vrf in name/id, vrf out name/id) 1 66.166.190.65.vr9.mclnva23-seb1.mclean.covad.com (66.166.190.65) 12 msec 8 msec 12 msec 2 192.168.22.93 [AS 65333] 8 msec 12 msec 8 msec 3 207.87.63.229 8 msec 8 msec 8 msec 4 vb1100.rar3.washington-dc.us.xo.net (216.156.0.33) 32 msec 32 msec 32 msec 5 ae0d0.mcr2.chicago-il.us.xo.net (216.156.0.166) 28 msec 28 msec 36 msec 6 xe920.eg113mx.ord.your.org (208.177.246.210) 28 msec 32 msec 28 msec 7 eg113mx.cr1.your.org (216.14.98.42) 32 msec 28 msec 28 msec 8 * * * You show it hasnt been pingable, yet I cant ping anything on your side at all. A traceroute6 from the outside to 2001:4978:F:1E3::2 on my end stops at: 7 10gigabitethernet1-1-8.switch5.ash1.he.net 1156.869 ms 1284.280 ms 1968.421 ms 8 10ge3-6.core2.chi1.he.net 1002.714 ms 1354.789 ms 300.651 ms 9 * * * 10 unassigned.v6.your.org 304.932 ms 303.382 ms 303.372 ms 11 unassigned.v6.your.org 305.308 ms 1076.348 ms 350.312 ms 12 gw-484.chi-02.us.sixxs.net 305.085 ms 308.456 ms 305.311 ms 13 * * * The same traceroute, but to Sixxs end of the tunnel 2001:4978:F:1E3::1 7 10gigabitethernet1-1-8.switch5.ash1.he.net 280.099 ms 464.491 ms 280.486 ms 8 10ge3-6.core2.chi1.he.net 325.022 ms 303.380 ms 300.001 ms 9 * * * 10 unassigned.v6.your.org 303.504 ms 328.101 ms 303.571 ms 11 unassigned.v6.your.org 382.698 ms 303.421 ms 342.794 ms 12 * * * numerical 7 2001:470:1:2d8::1 1346.484 ms 1946.269 ms 2047.497 ms 8 2001:470:0:286::1 543.622 ms 1438.435 ms 2011.578 ms 9 * * * 10 2001:4978:2::2 981.365 ms 303.864 ms 303.449 ms 11 2001:4978:1:400::53:1 303.626 ms 303.442 ms 764.937 ms 12 * * * Tunnel Details Shows: Encap.Pkt Send Error1989612, last: 0.12.0.1 2016-03-07 21:59:34 (1457387974; 0 days 00:00:02 ago)

State change: user Locked

Jeroen Massar SixXS Staff

on Monday, 07 March 2016 22:19:42

The state of this ticket has been changed to user

Tunnel Down in Chicago

Jeroen Massar SixXS Staff

on Monday, 07 March 2016 22:30:18

Can't reach your end of tunnel. Appears to be problem within Your.Org infrastructure.

Why do you think that?

2 192.168.22.93 [AS 65333] 8 msec 12 msec 8 msec

An RFC1918 address, are you sure you are not behind a NAT? Also, with that in the path various things like Path MTU discovery will be broken.

You show it hasnt been pingable

What do you mean with "You show it hasn't been pingable"? Who show what?

yet I cant ping anything on your side at all.

If your tunnel is broken then indeed you can't ping anything on the other side of the tunnel... PoP is perfectly reachable over IPv4 and IPv6:

...
16  ae0d0.mcr1.chicago-il.us.xo.net (216.156.0.162)  146.543 ms  148.134 ms  146.483 ms
17  ae1d0.mcr2.chicago-il.us.xo.net (216.156.1.82)  147.029 ms  145.603 ms  145.344 ms
18  xe920.eg113mx.ord.your.org (208.177.246.210)  147.237 ms  147.485 ms  147.442 ms
19  eg113mx.cr1.your.org (216.14.98.42)  147.992 ms  146.663 ms  146.936 ms
20  sixxs.cx01.chi.bb.your.org (216.14.98.22)  148.728 ms  147.736 ms  147.098 ms

18  2001:418:0:5000::25b (2001:418:0:5000::25b)  128.996 ms  130.735 ms  129.934 ms
19  ae4-0.cr1.ord6.scnet.net (2001:1838::cc5d:cc55)  127.913 ms  128.083 ms  128.112 ms
20  ae1-0.ar3.ord6.scnet.net (2001:1838::cc5d:cc6d)  142.381 ms  139.5 ms  137.437 ms
21  unknown.ipv6.scnet.net (2001:1838:2000:201::2)  123.473 ms  122.007 ms  121.67 ms
22  * unassigned.v6.your.org (2001:4978:2::2)  121.356 ms  121.912 ms
23  sixxs.cx01.chi.bb6.your.org (2001:4978:1:400:202:b3ff:feb4:59cb)  121.196 ms  121.839 ms  123.491 ms

A traceroute6 from the outside to 2001:4978:F:1E3::2 on my end stops at:

It stops there as the tunnel between the PoP and you does not work, the next hop would be your host.

The same traceroute, but to Sixxs end of the tunnel 2001:4978:F:1E3::1

Works quite fine:

...
21  unknown.ipv6.scnet.net (2001:1838:2000:202::2)  126.018 ms  126.842 ms  126.724 ms
22  unassigned.v6.your.org (2001:4978:2::2)  123.728 ms  125.359 ms  124.816 ms
23  unassigned.v6.your.org (2001:4978:1:400::53:1)  125.651 ms  129.291 ms  125.267 ms
24  gw-484.chi-02.us.sixxs.net (2001:4978:f:1e3::1)  125.509 ms  125.414 ms  126.989 ms

Note that depending on your routing tables, you might not receive the response back as you route it over the wrong prefix. Your latency is extremely high btw, it only takes about 100ms to go from Europe to the US, thus why are you in the 300ms range?

Encap.Pkt Send Error1989612, last: 0.12.0.1 2016-03-07 21:59:34 (1457387974; 0 days 00:00:02 ago)

Those are ICMPs coming back from hops somewhere in the path between the PoP and you. Seems something is causing corrupt packets on your specific path as we do not see that for any of the other tunnels. Please also check the rest of the contact page's Reporting Problems section.

Please note Posting is only allowed when you are logged in.