Ticket ID: SIXXS #4856585 Ticket Status: Resolved PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)
ipv6.juniper.net not reachable from dedus01
Shadow Hawkins on Sunday, 05 June 2011 22:48:13
When trying to reach ipv6.juniper.net, I get a "No route to host", used to work a few days ago:
greyhound% curl -I6v http://ipv6.juniper.net/
* About to connect() to ipv6.juniper.net port 80 (#0)
* Trying 2620:103:c003::10... No route to host
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host
greyhound% traceroute6 ipv6.juniper.net
traceroute6 to ipv6.juniper.net (2620:103:c003::10) from 2a01:198:215::2, 64 hops max, 12 byte packets
1 2a01:198:215::2 0.440 ms 0.346 ms 0.345 ms
2 gw-86.dus-01.de.sixxs.net 50.450 ms 34.886 ms 29.101 ms
3 sixxs-dus.dus.speedpartner.de 41.328 ms !N 47.955 ms !N 36.737 ms !N
The same can be done using the traceroute tool on sixxs like this, but it looks kind of underwhelming.
If taking a different source address, like nlams01-6 to ipv6.juniper.net it all works perfectly.
State change: confirmed
Shadow Hawkins on Sunday, 05 June 2011 23:35:33
The state of this ticket has been changed to confirmed
ipv6.juniper.net not reachable from dedus01
Shadow Hawkins on Sunday, 05 June 2011 23:39:39
Thank you for pointing this out. Juniper doesn't seem to be that well meshed with IPv6-upstreams yet. We don't receive that route through any of our peerings or (even larger) IPv6-transits. The route at nlams01 you mention comes from AS12702 (Verizon actually) at AMS-IX. We've contacted them (and Juniper), since Verizon seems to be one of the few (the only?) upstream for that Juniper-prefix. Strange ...
ipv6.juniper.net not reachable from dedus01
Shadow Hawkins on Tuesday, 07 June 2011 01:37:33
Hi. Our tries have been successful. Since yesterday afternoon (6th June) we have a stable route towards ipv6.juniper.net and it is reachable from dedus01 just fine.
Go head, enjoy Juniper's IPv6-site. Have a nice World IPv6-day.
Best greetings from SpeedPartner GmbH (dedus01) :-)
State change: remoteproblem
Jeroen Massar on Monday, 06 June 2011 00:35:30
The state of this ticket has been changed to remoteproblem
ipv6.juniper.net not reachable from dedus01
Jeroen Massar on Monday, 06 June 2011 00:37:08
Juniper has lots of IPv6 connectivity issues, not only transit but also they are dropping ICMP in various places thus causing Path MTU issues. Nothing we can do about though. Various folks have tried to contact them already.
State change: resolved
Shadow Hawkins on Tuesday, 07 June 2011 01:35:29
The state of this ticket has been changed to resolved
Posting is only allowed when you are logged in. |