SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #14439081
Ticket Status: Resolved

PoP: usbos01 - OCCAID Inc. (Boston, Massachusetts)

Routing issue
[us] Shadow Hawkins on Wednesday, 21 October 2015 12:42:56
Hello, It looks like there is a routing issue with the Boston PoP / within Occaid's network. Outbound traceroute: traceroute www.sixxs.net -6 traceroute to www.sixxs.net (2001:1af8:4050::2), 30 hops max, 80 byte packets 1 yggdrasil.falling.se (2001:4830:1164::1) 0.718 ms 0.708 ms 0.687 ms 2 gw-242.bos-01.us.sixxs.net (2001:4830:1100:f1::1) 11.204 ms 15.868 ms 16.859 ms 3 sixxs-ic-1139-bos.customer.occaid.net (2001:4830:e1:b::2) 17.015 ms 17.001 ms 17.326 ms 4 dcr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 17.310 ms 17.287 ms 17.262 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * Inbound traceroute to the tunnel: traceroute 2001:4830:1100:f1::2 traceroute to 2001:4830:1100:f1::2 (2001:4830:1100:f1::2), 30 hops max, 80 byte packets 1 v3.thor.falling.se (2001:470:7a88::1) 1.367 ms 1.303 ms 1.255 ms 2 jjfalling-3.tunnel.tserv11.ams1.ipv6.he.net (2001:470:1f14:70c::1) 14.637 ms 19.318 ms 18.261 ms 3 v213.core1.ams1.he.net (2001:470:0:7d::1) 25.741 ms 25.692 ms 24.783 ms 4 100ge9-1.core1.lon2.he.net (2001:470:0:2d0::1) 21.805 ms 33.616 ms 21.664 ms 5 ibr01-ve26.lndn01.occaid.net (2001:7f8:4::7577:1) 27.256 ms 26.539 ms 26.507 ms 6 ibr01-ve26.lndn01.occaid.net (2001:7f8:4::7577:1) 27.052 ms !N 18.989 ms !N 19.907 ms !N It looks like the closet hop to my tunnel that is reachable on inbound connections is sixxs-ic-1139-bos.customer.occaid.net (2001:4830:e1:b::2). After that I start seeing routing issues in Occaid. traceroute 2001:4830:e1:b::2 traceroute to 2001:4830:e1:b::2 (2001:4830:e1:b::2), 30 hops max, 80 byte packets 1 v3.thor.falling.se (2001:470:7a88::1) 1.354 ms 1.262 ms 1.214 ms 2 jjfalling-3.tunnel.tserv11.ams1.ipv6.he.net (2001:470:1f14:70c::1) 43.652 ms 42.593 ms 43.513 ms 3 v213.core1.ams1.he.net (2001:470:0:7d::1) 43.993 ms 43.962 ms 43.915 ms 4 100ge9-1.core1.lon2.he.net (2001:470:0:2d0::1) 46.731 ms 49.954 ms 45.638 ms 5 ibr01-ve26.lndn01.occaid.net (2001:7f8:4::7577:1) 47.559 ms 47.493 ms 47.725 ms 6 bbr01-g1-1.slgh01.occaid.net (2001:4830:fe:2004::1) 47.675 ms 50.225 ms 49.125 ms 7 bbr01-p2-4.whkn01.occaid.net (2001:4830:fe:2002::2) 134.676 ms 130.429 ms 133.894 ms 8 nyk01-ip-rt-gi0-0-1.occaid.net (2001:4830:ff:13::1) 137.684 ms 142.754 ms 141.612 ms 9 bsn01-ip-rt-gi0-1-232.occaid.net (2001:4830:ff:12::2) 146.312 ms 148.009 ms 147.697 ms 10 bos01-ip-rt-gi0-4.occaid.net (2001:4830:ff:11::2) 148.154 ms 148.112 ms 148.325 ms 11 sixxs-ic-1139-bos.customer.occaid.net (2001:4830:e1:b::2) 147.750 ms 145.582 ms 144.298 ms Thank you, /Jeremy
Routing issue Private
[us] Shadow Hawkins on Wednesday, 21 October 2015 15:25:26
I am seeing the same behavior, since at least some time last night. From a non-sixxs machine in Germany, and from a sixxs tunnel from uschi02 I can traceroute6 to 2001:4830:e1:b::2, which I think is the sixxs box endpoint; it's one hop beyond the box that terminates my tunnel, If I try to traceroute6 to 2001:4830:1100::1 (not a valid address probably, but should hit the /48 routing entry), I stop from .de at 7 ibr01-ve26.lndn01.occaid.net 16.76 ms !N 17.215 ms !N 16.841 ms !N and from uschi02 at 2 gw-627.chi-02.us.sixxs.net 25.536 ms 26.51 ms 26.02 ms 3 unassigned.v6.your.org 26.603 ms 25.822 ms 26.05 ms 4 sixxs.ge-0.0.0-30.core1.chi.bb6.your.org 26.329 ms 26.824 ms 27.738 ms 5 unassigned.v6.your.org 26.338 ms 26.394 ms 26.427 ms 6 unknown.ipv6.scnet.net 26.168 ms 26.226 ms 26.211 ms 7 ae13-0.cr1.ord6.scnet.net 26.881 ms 26.922 ms 27.118 ms 8 lag-27.ear1.Chicago2.Level3.net 34.438 ms 27.573 ms 27.624 ms 9 * vl-51.ear2.Chicago2.Level3.net 28.649 ms 203.978 ms 10 2001:1900:4:1::be 48.783 ms 48.664 ms 48.34 ms 11 2001:1900:4:1::4ad 49.078 ms 48.951 ms 48.952 ms 12 vl-4086.edge3.London1.Level3.net 117.344 ms 116.55 ms 116.213 ms 13 vl-51.sar1.London1.Level3.net 245.356 ms 301.795 ms 292.682 ms 14 ibr02-ve26.lndn01.occaid.net 119.453 ms !N 119.147 ms !N 119.205 ms !N From panix (NYC): 6 ibr01-ve96.asbn01.occaid.net 7.226 ms !N 6.969 ms !N 7.107 ms !N I get similar results with my actual tunnel address, except that I have shortcut routes via a private tunnel among some of my sites. I also have similar results from a box at ISC colo in San Francisco (which has traceroute issues, but confirmed with ping6. So it looks to me like the 2001:4830:1100::/48 prefix is not getting into occaid's IGP.
Routing issue Private
[us] Shadow Hawkins on Wednesday, 21 October 2015 17:11:03
I'm seeing the same as well, it started last night. traceroute6 www.sixxs.net traceroute6: Warning: nginx.sixxs.net has multiple addresses; using 2001:960:800::2 traceroute6 to nginx.sixxs.net (2001:960:800::2) from 2001:4830:1100:******, 64 hops max, 12 byte packets 1 2001:4830:1100:****** 6.633 ms 0.759 ms 0.542 ms 2 gw-800.bos-01.us.sixxs.net 23.135 ms 25.638 ms 21.415 ms 3 sixxs-ic-1139-bos.customer.occaid.net 22.313 ms 25.702 ms 22.331 ms 4 dcr01-ve402.bstn01.occaid.net 22.337 ms 23.614 ms 22.129 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * *
Routing issue Private
[us] Shadow Hawkins on Wednesday, 21 October 2015 23:10:32
Same problem here: # traceroute6 www.facebook.com traceroute to star.c10r.facebook.com (2a03:2880:11:1f04:face:b00c:0:1) from 2001:4830:1100:1fa::2, 30 hops max, 16 byte packets 1 gw-507.bos-01.us.sixxs.net (2001:4830:1100:1fa::1) 2.819 ms 2.687 ms 2.711 ms 2 sixxs-ic-1139-bos.customer.occaid.net (2001:4830:e1:b::2) 2.742 ms 2.736 ms 2.75 ms 3 dcr01-ve402.bstn01.occaid.net (2001:4830:e1:b::1) 2.823 ms 2.786 ms 2.827 ms 4 * * * Looks from my MRTG like it started at 1615 Eastern yesterday (10/20).
Routing issue Private
[ca] Shadow Hawkins on Wednesday, 21 October 2015 23:59:03
Me too! From TekSavvy's (Canada) native IPv6 to my tunnel: pablob@lennie:~$ traceroute6 2001:4830:1100:32e::2 traceroute to 2001:4830:1100:32e::2 (2001:4830:1100:32e::2), 30 hops max, 80 byte packets 1 node-77b29keehjsye4wp729.ipv6.teksavvy.com (2607:f2c0:f00f:e00::1) 1.330 ms 1.651 ms 3.831 ms 2 node-4stumn9czaceuw4ucqp.ipv6.teksavvy.com (2607:f2c0:a000:1a::1) 51.873 ms 54.186 ms 56.669 ms 3 ae0_2140-bdr04-tor.teksavvy.com (2607:f2c0:1:2140::4) 58.037 ms 62.408 ms ae1_2150-bdr04-tor.teksavvy.com (2607:f2c0:1:2150::4) 66.628 ms 4 10gigabitethernet9-9.core1.tor1.he.net (2001:504:d:80::6939:1) 66.050 ms 67.948 ms 71.840 ms 5 100ge7-2.core1.nyc4.he.net (2001:470:0:2dc::1) 90.506 ms 90.601 ms 90.830 ms 6 100ge15-1.core1.ash1.he.net (2001:470:0:299::1) 99.717 ms 68.570 ms 72.734 ms 7 ibr01-ve96.asbn01.occaid.net (2001:504:0:2:0:3:71:1) 68.346 ms 69.846 ms 73.597 ms 8 ibr01-ve96.asbn01.occaid.net (2001:504:0:2:0:3:71:1) 76.065 ms !N 78.109 ms !N 80.307 ms !N As the others, outbound traceroute ends at dcr01-ve402.bstn01.occaid.net (in my phone, so I cannot easily paste the output). Thanks!
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Thursday, 22 October 2015 17:24:46
Message is Locked
The state of this ticket has been changed to confirmed
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 23 October 2015 00:17:20
Message is Locked
The state of this ticket has been changed to resolved
Routing issue Private
[ca] Shadow Hawkins on Tuesday, 21 February 2017 23:54:27
Hello, It looks like this issue in a routing issue with the Boston PoP / within Occaid's network. Came back: $ tracepath6 www.sixxs.net 1?: [LOCALHOST] 0.006ms pmtu 1500 1: gateway 0.699ms 1: gateway 0.596ms 2: gateway 0.760ms pmtu 1280 2: gw-326.bos-01.us.sixxs.net 29.133ms 3: sixxs-ic-1139-bos.customer.occaid.net 29.046ms asymm 2 4: dcr01-ve402.bstn01.occaid.net 29.428ms !N Or should I open new ticket? Thank you in advance, Alex
Routing issue Private
[us] Shadow Hawkins on Friday, 03 March 2017 02:50:41
I can confirm that I'm also seeing this issue with the Boston PoP.

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker