Tickets - No route to 2001:41d0::/32 :: SixXS - IPv6 Deployment & Tunnel Broker

Ticket ID: SIXXS #3779981
Ticket Status: Resolved

PoP: plwaw01 - ICM (Warsaw)

No route to 2001:41d0::/32

Shadow Hawkins on Sunday, 27 February 2011 22:22:58

Hi, When I'm trying to connect with machine that is in 2001:41d0::/32 (OVH) I see "No route to host". For example:

$ ping6 2001:41d0:1:8851:dada:fafa:caca:baba PING 2001:41d0:1:8851:dada:fafa:caca:baba(2001:41d0:1:8851:dada:fafa:caca:baba) 56 data bytes From 2001:6a0:1:1::1 icmp_seq=1 Destination unreachable: No route

$ traceroute6 2001:41d0:1:8851:dada:fafa:caca:baba traceroute to 2001:41d0:1:8851:dada:fafa:caca:baba (2001:41d0:1:8851:dada:fafa:caca:baba), 30 hops max, 80 byte packets 1 2001:6a0:14d::1 (2001:6a0:14d::1) 0.213 ms 0.219 ms 0.231 ms 2 gw-119.waw-01.pl.sixxs.net (2001:6a0:200:76::1) 11.254 ms 15.275 ms 16.137 ms 3 kp-mm-r3.rtr.net.icm.edu.pl (2001:6a0:1:1::1) 19.997 ms !N 20.290 ms !N 20.851 ms !N

State change: confirmed Locked

Jeroen Massar SixXS Staff

on Sunday, 27 February 2011 22:36:52

The state of this ticket has been changed to confirmed

No route to 2001:41d0::/32

Shadow Hawkins on Thursday, 10 March 2011 13:01:46

any progress?

No route to 2001:41d0::/32

Shadow Hawkins on Tuesday, 29 March 2011 23:11:52

Problem still exists, and for Polish users is quite important one. Many PL websites are hosted on OVH servers, and when IPv6 works there we cannot visit those pages as usual. root@zuom:~# ping6 2001:41d0:1:f0cf::1 PING 2001:41d0:1:f0cf::1(2001:41d0:1:f0cf::1) 56 data bytes From 2001:6a0:1:1::1 icmp_seq=1 Destination unreachable: No route From 2001:6a0:1:1::1 icmp_seq=2 Destination unreachable: No route From 2001:6a0:1:1::1 icmp_seq=3 Destination unreachable: No route traceroute to 2001:41d0:1:f0cf::1 (2001:41d0:1:f0cf::1) from 2001:6a0:18b:deaf::1, 30 hops max, 16 byte packets 1 gw-141.waw-01.pl.sixxs.net (2001:6a0:200:8c::1) 26.953 ms 24.813 ms 23.82 ms 2 kp-mm-r3.rtr.net.icm.edu.pl (2001:6a0:1:1::1) 34.895 ms !N 29.598 ms !N 29.943 ms !N

No route to 2001:41d0::/32

Shadow Hawkins on Wednesday, 30 March 2011 20:44:15

ping -6 2001:41d0:1:8851:dada:fafa:caca:baba

Ping 2001:41d0:1:8851:dada:fafa:caca:baba 32 Bytes Data Answer from 2001:41d0:1:8851:dada:fafa:caca:baba: time=67ms

tracert -6 2001:41d0:1:8851:dada:fafa:caca:baba

ovh.sawicki.eu.org [2001:41d0:1:8851:dada:fafa:caca:baba]: 1 92 ms 61 ms 51 ms gw-343.muc-02.de.sixxs.net [2001:a60:f000:156::1] 2 81 ms * 50 ms 2001:a60:0:30::1 3 66 ms * 65 ms th1-1-6k.fr.eu [2001:41d0::b92] 4 68 ms * 65 ms gsw-1-6k.fr.eu [2001:41d0::501] 5 70 ms * 97 ms rbx-1-6k.fr.eu [2001:41d0::531] 6 72 ms 69 ms 69 ms ovh.sawicki.eu.org [2001:41d0:1:8851:dada:fafa:c aca:baba] Seems like the used PoP routes not in the right direction. Hop after PoP is for me th1-1-6k.fr.eu Hope this helps

No route to 2001:41d0::/32

Shadow Hawkins on Friday, 01 April 2011 23:59:14

IS there any estimate date when it will be fixed?

State change: resolved Locked

Jeroen Massar SixXS Staff

on Saturday, 02 April 2011 18:40:47

The state of this ticket has been changed to resolved

No route to 2001:41d0::/32

Jeroen Massar SixXS Staff

on Saturday, 02 April 2011 18:41:10

Resolved, that is, the problem disappeared: traceroute to 2001:41d0:1:8851:dada:fafa:caca:baba (2001:41d0:1:8851:dada:fafa:caca:baba), 30 hops max, 80 byte packets 1 css6-XE2-0-0-4045.ipv6.man.poznan.pl (2001:808:2:3003::1) 0.447 ms 0.475 ms 0.551 ms 2 css5-XE0-2-0-50.ipv6.man.poznan.pl (2001:808:2:d::2) 0.515 ms 0.544 ms 0.631 ms 3 2001:b10:a000:23e::1 (2001:b10:a000:23e::1) 0.620 ms 0.789 ms 0.732 ms 4 * * amsix2.routers.ovh.net (2001:7f8:1::a501:6276:2) 18.606 ms 5 rbx-g2-a9.fr.eu (2001:41d0::ab1) 25.987 ms 26.587 ms 26.347 ms 6 rbx-1-6k.fr.eu (2001:41d0::6c1) 23.666 ms * * 7 ovh.sawicki.eu.org (2001:41d0:1:8851:dada:fafa:caca:baba) 23.671 ms 23.682 ms 23.650 ms

No route to 2001:41d0::/32

Shadow Hawkins on Sunday, 03 April 2011 10:34:32

The problem still exists:

> ping6 swmud.pl PING swmud.pl(swmud.pl) 56 data bytes From kp-mm-r3.rtr.net.icm.edu.pl icmp_seq=1 Destination unreachable: No route From kp-mm-r3.rtr.net.icm.edu.pl icmp_seq=2 Destination unreachable: No route From kp-mm-r3.rtr.net.icm.edu.pl icmp_seq=3 Destination unreachable: No route From kp-mm-r3.rtr.net.icm.edu.pl icmp_seq=4 Destination unreachable: No route From kp-mm-r3.rtr.net.icm.edu.pl icmp_seq=5 Destination unreachable: No route From kp-mm-r3.rtr.net.icm.edu.pl icmp_seq=6 Destination unreachable: No route ^C --- swmud.pl ping statistics --- 6 packets transmitted, 0 received, +6 errors, 100% packet loss, time 5007ms

> ifconfig sixxs sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet6 addr: fe80::4a0:200:255:2/64 Scope:Link inet6 addr: 2001:6a0:200:255::2/64 Scope:Global UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1 RX packets:742 errors:0 dropped:0 overruns:0 frame:0 TX packets:705 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:622168 (607.5 KiB) TX bytes:151209 (147.6 KiB)

Reopen of: No route to 2001:41d0::/32

Shadow Hawkins on Sunday, 03 April 2011 10:42:00

The problem still exists:

> host -a swmud.pl swmud.pl AAAA 2001:41D0:1:8191:0:0:0:1

Reopen of: No route to 2001:41d0::/32

Shadow Hawkins on Sunday, 03 April 2011 10:46:17

> traceroute6 2001:41D0:1:8191:0:0:0:1 traceroute to 2001:41D0:1:8191:0:0:0:1 (2001:41d0:1:8191::1) from 2001:6a0:200:255::2, 30 hops max, 24 byte packets 1 gw-598.waw-01.pl.sixxs.net (2001:6a0:200:255::1) 12.736 ms 7.756 ms 8.551 ms 2 kp-mm-r3.rtr.net.icm.edu.pl (2001:6a0:1:1::1) 11.448 ms !N 12.812 ms !N 12.245 ms !N

Reopen of: No route to 2001:41d0::/32

Jeroen Massar SixXS Staff

on Sunday, 03 April 2011 12:10:59

Only thing I can state here is that OVH should look for proper transit as several ISPs are not receiving their prefix: http://www.ris.ripe.net/mt/prefixdashboard.html?prefix=2001%3A41D0%3A%3A%2F32 Nothing we can do about this. As you claim to be a paying customer, complain to them about their service and point them to the above RIS page or to GRH which will tell you the same thing.

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