SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #12392789
Ticket Status: Resolved

PoP: deham01 - Easynet (Hamburg)

routing to 2001:6f8:1000::/38 broken
[de] Shadow Hawkins on Tuesday, 30 September 2014 07:58:06
routing to 2001:6f8:1000::/38 seems broken: root@tasse:~# tracepath6 2001:6f8:0900:: 1?: [LOCALHOST] 0.035ms pmtu 1500 1: 2a03:4000:6:1000::2 0.716ms 1: 2a03:4000:6:1000::2 0.568ms 2: 30gigabitethernet4-3.core1.fra1.he.net 8.187ms 3: te0-2-1-0.gr11.ixfra.de.easynet.net 6.828ms asymm 5 4: 2001:6f8:1:1:87:86:76:34 18.164ms asymm 5 5: tengige0-0-0-2-112.er0.kgham.nexinto.net 14.200ms asymm 3 6: 2001:6f8:862:1::c2e9:c729 13.544ms asymm 3 7: 2001:6f8:862:1::c2e9:c729 13.663ms asymm 3 8: gw-1.ham-01.de.sixxs.net 13.604ms !N Resume: pmtu 1500 root@tasse:~# tracepath6 2001:6f8:1000:: 1?: [LOCALHOST] 0.039ms pmtu 1500 1: 2a03:4000:6:1000::2 0.733ms 1: 2a03:4000:6:1000::2 0.533ms 2: 30gigabitethernet4-3.core1.fra1.he.net 18.119ms 3: te0-2-1-0.gr11.ixfra.de.easynet.net 8.690ms !N Resume: pmtu 1500 root@tasse:~# tracepath6 2001:6f8:1100:: 1?: [LOCALHOST] 0.040ms pmtu 1500 1: 2a03:4000:6:1000::2 0.728ms 1: 2a03:4000:6:1000::2 0.581ms 2: 30gigabitethernet4-3.core1.fra1.he.net 5.022ms 3: te0-2-1-0.gr11.ixfra.de.easynet.net 8.828ms !N Resume: pmtu 1500 root@tasse:~# tracepath6 2001:6f8:1300:: 1?: [LOCALHOST] 0.032ms pmtu 1500 1: 2a03:4000:6:1000::2 0.697ms 1: 2a03:4000:6:1000::2 0.431ms 2: 30gigabitethernet4-3.core1.fra1.he.net 4.064ms 3: te0-2-1-0.gr11.ixfra.de.easynet.net 8.221ms !N Resume: pmtu 1500 root@tasse:~# tracepath6 2001:6f8:1400:: 1?: [LOCALHOST] 0.036ms pmtu 1500 1: 2a03:4000:6:1000::2 0.660ms 1: 2a03:4000:6:1000::2 1.993ms 2: 30gigabitethernet4-3.core1.fra1.he.net 14.114ms 3: te0-2-1-0.gr11.ixfra.de.easynet.net 8.585ms asymm 5 4: 2001:6f8:1:1:87:86:76:21 24.578ms asymm 9 5: 2001:6f8:1:2:87:86:71:177 26.360ms asymm 7 6: bebru01.sixxs.net 22.179ms asymm 8 7: gw-660.bru-01.be.sixxs.net 21.831ms !N Resume: pmtu 1500
subnet not routing to the internet anymore (MBJ16-SIXXS) Private
[de] Shadow Hawkins on Tuesday, 30 September 2014 08:14:40
Hello, since sometime yesterday evening we're having trouble with the routing for one of our registered subnets. We have two tunnels that use the POP deham01, IDs T127214 and T137314. On tunnel T137314 there's the subnet R236074. From this subnet I cannot reach any other IPv6 host outside of deham01. Meaning: - I cannot ping6 www.heise.de or www.google.com, nor can I reach www.sixxs.net via https. - However, I can ping the subnet that the other tunnel using POP deham01 has available (R225402). - From that other tunnel I can reach all three aforementioned hosts just fine. To make it clear: - From R236074 to R225402 and the other way around: works - From R225402 to the internet (www.sixxs.net, www.google.com): works - From R236074 to the internet (www.sixxs.net, www.google.com): does NOT work The subnet R236074 used to work just fine until roughly late last night (meaning ~21:00 UTC) according to several syslog messages I'm seeing about unreachable hosts. The POP itself (deham01) is up according to the POP status page. The tunnel is established (aiccu is running, logs look fine). I've tried re-starting aiccu but that didn't change anything; the tunnel was established again but the routing problem persists. Both aiccus run behind NATing gateways connected via DSL lines. The gateways itself have dynamic but public IPv4 addresses, meaning there's most likely no further NAT applied by the provider. tracepath6 www.sixxs.net looks like the following from those two tunnels: 1. From R236074: [0 mbunkus@chai-latte ~] tracepath6 www.sixxs.net 1?: [LOCALHOST] 0.010ms pmtu 1500 1: 2001:6f8:13dc:2::1 0.587ms 1: 2001:6f8:13dc:2::1 0.523ms 2: 2001:6f8:13dc:2::1 0.472ms pmtu 1400 2: gw-4300.ham-01.de.sixxs.net 24.533ms 3: 2001:6f8:862:1::c2e9:c729 24.503ms asymm 2 4: 2001:6f8:862:1::c2e9:c72c 25.522ms asymm 3 5: no reply 6: no reply 7: no reply 8: no reply 9: no reply 10: no reply 11: no reply 12: no reply 13: no reply 14: no reply 15: no reply 16: no reply 17: no reply 18: no reply 19: no reply ... 2. From R225402: [0 mosu@sweet-chili ~] tracepath6 www.sixxs.net 1?: [LOCALHOST] 0.026ms pmtu 1500 1: 2001:6f8:900:9029::1 1.281ms 1: 2001:6f8:900:9029::1 0.418ms 2: 2001:6f8:900:9029::1 0.421ms pmtu 1400 2: gw-4138.ham-01.de.sixxs.net 25.391ms 3: 2001:6f8:862:1::c2e9:c729 26.640ms asymm 2 4: vl2280.cr10.noham.de.easynet.net 26.683ms asymm 3 5: decix.peering-inx.fra.leaseweb.net 36.344ms asymm 7 6: 2a00:c98::7 60.249ms asymm 7 7: 2a03:2280:38::2d 60.699ms asymm 8 8: 2001:1af8::81:17:32:169 44.060ms asymm 9 9: 2001:1af8::81:17:32:175 46.401ms asymm 10 10: nlhaa01.sixxs.net 45.989ms reached Resume: pmtu 1400 hops 10 back 54 tracepath deham01.sixxs.net looks like the following: 1. From R236074: [0 mbunkus@chai-latte ~] tracepath deham01.sixxs.net 1?: [LOCALHOST] pmtu 1500 1: 10.199.92.1 0.524ms 1: 10.199.92.1 0.437ms 2: 10.199.92.1 0.449ms pmtu 1476 2: 192.168.141.2 1.536ms 3: 217.0.117.216 21.911ms asymm 4 4: 217.237.153.246 25.774ms asymm 7 5: hh-eb5-i.HH.DE.NET.DTAG.DE 28.606ms asymm 8 6: 62.157.250.54 25.282ms asymm 8 7: 194.15.144.79 25.300ms asymm 9 8: 194.15.144.79 24.516ms asymm 9 9: deham01.sixxs.net 24.928ms reached Resume: pmtu 1476 hops 9 back 56 2. From R225402: [0 mosu@sweet-chili ~] tracepath deham01.sixxs.net 1?: [LOCALHOST] pmtu 1500 1: astaro.local.bunkus.org 0.674ms 1: astaro.local.bunkus.org 0.590ms 2: astaro.local.bunkus.org 0.731ms pmtu 1492 2: fritzbox.local.bunkus.org 2.160ms 3: 217.0.119.190 23.002ms 4: 87.186.194.58 27.879ms 5: hh-eb5-i.HH.DE.NET.DTAG.DE 29.727ms asymm 8 6: 62.157.250.54 27.039ms asymm 8 7: 194.15.144.79 32.599ms asymm 8 8: 194.15.144.79 27.648ms 9: deham01.sixxs.net 26.385ms reached Resume: pmtu 1492 hops 9 back 57 If you need any more information please just ask. Thanks. Kind regards, Moritz Bunkus
subnet not routing to the internet anymore (MBJ16-SIXXS) Private
[de] Shadow Hawkins on Tuesday, 30 September 2014 08:21:48
There seems to be a routing problem in or through EasyNet. I have a similar problem: $ traceroute6 sturgeon.freenode.net traceroute to sturgeon.freenode.net (2a02:2498:1:3ad::2) from 2001:6f8:138e:0:224:1dff:fede:7b31, port 33434, from port 63555, 30 hops max, 60 bytes packets 1 Bifrost.Balrog.DE (2001:6f8:138e::fe) 0.872 ms 1.116 ms 1.207 ms 2 gw-1243.ham-01.de.sixxs.net (2001:6f8:900:4da::1) 59.057 ms 55.862 ms 59.289 ms 3 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 58.132 ms 60.715 ms 61.282 ms 4 vl2280.cr10.noham.de.easynet.net (2001:6f8:862:1::c2e9:c72c) 62.697 ms 64.504 ms 57.182 ms 5 * * * 6 * * * ...
subnet not routing to the internet anymore (MBJ16-SIXXS) Private
[de] Shadow Hawkins on Tuesday, 30 September 2014 12:39:50
Just a quick /me too. The tunnel T4512 is fine, but the routing of the subnet R2070 is broken since about 00:45 UTC.
routing to 2001:6f8:1000::/38 broken Private
[de] Shadow Hawkins on Tuesday, 30 September 2014 08:28:12
This seems to be related to Ticket 12392805 as in both cases EasyNet is the last routing hop. They seem to have some problems at the moment.
routing to 2001:6f8:1000::/38 broken Private
[de] Shadow Hawkins on Tuesday, 30 September 2014 08:54:54
I can confirm the same issue on subnet 2001:6f8:1183::/48. Routing out of the network works fine while routing back into the network fails.
State change: confirmed Locked
[ch] Jeroen Massar SixXS Staff on Tuesday, 30 September 2014 13:15:46
Message is Locked
The state of this ticket has been changed to confirmed
routing to 2001:6f8:1000::/38 broken Private
[de] Shadow Hawkins on Tuesday, 30 September 2014 20:19:50
I am seeing problems from here too, but additionally something weird that seems to be related. When doing anything from my gateway (a linux box), I can connect to almost everywhere. Though whenever I try it from any other box within my network, traceroutes stop at the very same:
vl2280.cr10.noham.de.easynet.net (2001:6f8:862:1::c2e9:c72c) 62.697 ms 64.504 ms 57.182 ms
host that seems to make problems. In the past I had that problem too and it went away after a day or two without me changing anything...
routing to 2001:6f8:1000::/38 broken Private
[de] Shadow Hawkins on Tuesday, 30 September 2014 23:17:58
Dennis Lubert wrote:
I am seeing problems from here too, but additionally something weird that seems to be related. When doing anything from my gateway (a linux box), I can connect to almost everywhere. Though whenever I try it from any other box within my network, traceroutes stop at the very same:
vl2280.cr10.noham.de.easynet.net (2001:6f8:862:1::c2e9:c72c) 62.697 ms 64.504 ms 57.182 ms
host that seems to make problems. In the past I had that problem too and it went away after a day or two without me changing anything...
The endpoint tunnels are indeed working as usual. But the routing for the networks to the tunnel endpoints is somehow damaged. It is very likely that the destination routing table entrys are gone, it might be also a aggregated route which is gone. In short: What seems to be weird is due that the endpoint tunnel is indeed working. It is also usual that the destination route for interfaces as they got up are set up. So also when you initiate a connection to sixxs the POP also uses a tunnel interface and so it sets up a interface based destination route. But it also would need to set up a route for your network which gets routed to your endpoint. And that is what probably is missing.
routing to 2001:6f8:1000::/38 broken Private
[de] Shadow Hawkins on Tuesday, 30 September 2014 23:19:41
Also that packets to external targets get routed properly is not unusual because it might be a default route to the next hop at the POP entry. It is just the destination route to your endpoint for your network which fails.
routing to 2001:6f8:1000::/38 broken Private
[de] Shadow Hawkins on Wednesday, 01 October 2014 07:24:24
Same problem here. The tunnel R2464 is assigned to the tunnel T5396 which is working correctly. At least it is possible to ping the router address (2001:6f8:900:417::2) from another native IPv6 host. The routing of the tunnel traffic stops somewhere on the path. This tracepath test is trying to discover the route from the routed network to an external host. ::fe is the router providing the tunnel to sixxs. $ tracepath6 -n 2a01:4f8:d13:4700::2 1?: [LOCALHOST] 0.066ms pmtu 1280 1: 2001:6f8:131f::fe 1.110ms 1: 2001:6f8:131f::fe 0.513ms 2: 2001:6f8:900:417::1 24.006ms 3: 2001:6f8:862:1::c2e9:c729 23.870ms asymm 2 4: 2001:6f8:862:1::c2e9:c72c 24.243ms asymm 3 5: no reply 6: no reply 7: no reply 8: no reply 9: no reply 10: no reply 11: no reply 12: no reply 13: no reply 14: no reply 15: no reply 16: no reply 17: no reply 18: no reply Starting from the host in the internet to a host behind the sixxs tunnel, the result of the tracepath is this. $ tracepath6 -n 2001:6f8:131f:0:5054:ff:febc:3624 1?: [LOCALHOST] 0.017ms pmtu 1500 1: no reply 2: 2a01:4f8:d13:d::1 1.909ms 3: 2a01:4f8:0:d0:1:0:10:3 0.565ms 4: 2a01:4f8:0:3::61 0.967ms 5: 2a01:4f8:0:3::b1 5.288ms 6: 2a01:4f8:0:3::11e 11.373ms 7: 2001:7f8:1::a500:4589:1 25.452ms !N Resume: pmtu 1500
routing to 2001:6f8:1000::/38 broken
[de] Shadow Hawkins on Wednesday, 01 October 2014 16:42:43
Seems to be resolved now... $ tracepath6 -n 2a01:4f8:d13:4700::2 1?: [LOCALHOST] 0.037ms pmtu 1280 1: 2001:6f8:131f::fe 1.903ms 1: 2001:6f8:131f::fe 4.289ms 2: 2001:6f8:900:417::1 26.446ms 3: 2001:6f8:862:1::c2e9:c729 29.350ms asymm 2 4: 2001:6f8:862:1::c2e9:c72c 27.358ms asymm 3 5: 2001:7f8::616c:0:1 36.418ms asymm 9 6: 2a01:4f8:0:3::5 39.540ms asymm 8 7: 2a01:4f8:0:3::b2 42.117ms asymm 9 8: 2a01:4f8:0:3::8e 42.566ms asymm 10 9: 2a01:4f8:0:d0:1:d:13:2 42.134ms asymm 11 10: no reply 11: 2a01:4f8:d13:4700::2 46.588ms reached Resume: pmtu 1280 hops 11 back 13
routing to 2001:6f8:1000::/38 broken Private
[de] Shadow Hawkins on Wednesday, 01 October 2014 11:07:25
Hello, TunnelID T133130 Subnet R231910 i have a similar problem, traceroutes to external hosts stops somewhere on the route: test01 :: ~ traceroute6 www.heise.de traceroute6 to www.heise.de (2a02:2e0:3fe:1001:7777:772e:2:85) from 2001:6f8:1269::9d9a:e22f:53f0:70ac, 64 hops max, 12 byte packets 1 2001:6f8:1269::1 0.623 ms 0.453 ms 0.375 ms 2 gw-4217.ham-01.de.sixxs.net 22.731 ms 22.383 ms 22.675 ms 3 2001:6f8:862:1::c2e9:c729 23.387 ms 22.609 ms 23.975 ms 4 2001:6f8:862:1::c2e9:c72c 24.130 ms 22.965 ms 31.837 ms 5 *^C a 'online' traceroute to my tunnel endpoint(2001:6f8:900:1078::2): traceroute to 2001:6f8:900:1078::2 (2001:6f8:900:1078::2), 30 hops max, 40 byte packets 1 2a02:348:82::1 (2a02:348:82::1) 2.830 ms 0.341 ms 0.322 ms 2 xl-internetservices.nl.ip6.jointtransit.nl (2a02:10:0:1::e:3) 1.611 ms 1.623 ms 1.531 ms 3 te3-0-0.gr10.saams.nl.easynet.net (2001:7f8:1::a500:4589:1) 3.627 ms 4.097 ms 4.016 ms 4 2001:6f8:801:1:0:1a03:c240:813 (2001:6f8:801:1:0:1a03:c240:813) 9.463 ms 9.409 ms 9.333 ms 5 2001:6f8:801:1:0:1a03:c240:812 (2001:6f8:801:1:0:1a03:c240:812) 12.932 ms 12.859 ms 12.800 ms 6 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 12.614 ms 12.551 ms 12.474 ms 7 2001:6f8:862:1::c2e9:c729 (2001:6f8:862:1::c2e9:c729) 12.419 ms 12.475 ms 12.732 ms 8 gw-4217.ham-01.de.sixxs.net (2001:6f8:900:1078::1) 12.715 ms 12.640 ms 12.551 ms 9 * * * 'online' traceroute to my router: traceroute to 2001:6f8:1269:0:56e6:fcff:feaf:3862 (2001:6f8:1269:0:56e6:fcff:feaf:3862), 30 hops max, 40 byte packets 1 2a02:348:82::1 (2a02:348:82::1) 1.251 ms 1.207 ms 0.418 ms 2 xl-internetservices.nl.ip6.jointtransit.nl (2a02:10:0:1::e:3) 7.791 ms 7.734 ms 7.638 ms 3 te3-0-0.gr10.saams.nl.easynet.net (2001:7f8:1::a500:4589:1) 4.707 ms !N 4.565 ms !N 5.215 ms !N
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 October 2014 17:01:55
Message is Locked
The state of this ticket has been changed to resolved

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker