Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: No route  (Read 6524 times)

wiro

  • Newbie
  • Newbie
  • *
  • Posts: 1
No route
« on: June 16, 2008, 08:32:26 AM »

One or two days ago I lost connection to IPv6.
I use 216.66.80.30 server and I can ping it. I can also ping my IPv6 adress and IP6 adress of tunnel server.
When I try to ping other hosts I give:
From wiro.tunnel.tserv6.fra1.ipv6.he.net icmp_seq=1 Destination unreachable: No route

My routes are:
2001:470:1f0a:20a::/64 via :: dev he-ipv6  metric 256  expires 17181518sec mtu 1480 advmss 1420 hoplimit 4294967295
2001:470:1f0b:20a::/64 via :: dev he-ipv6  metric 256  expires 17181518sec mtu 1480 advmss 1420 hoplimit 4294967295
fe80::/64 dev eth0  metric 256  expires 12241183sec mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 via :: dev he-ipv6  metric 256  expires 21333876sec mtu 1480 advmss 1420 hoplimit 4294967295
ff00::/8 dev eth0  metric 256  expires 12241183sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev he-ipv6  metric 256  expires 21333876sec mtu 1480 advmss 1420 hoplimit 4294967295
default dev he-ipv6  metric 1024  expires 21333876sec mtu 1480 advmss 1420 hoplimit 4294967295

Any idea ?
Logged

piojan

  • Jr. Member
  • **
  • Posts: 85
Re: No route
« Reply #1 on: June 16, 2008, 08:44:20 AM »

One or two days ago I lost connection to IPv6.
I use 216.66.80.30 server and I can ping it. I can also ping my IPv6 adress and IP6 adress of tunnel server.
From wiro.tunnel.tserv6.fra1.ipv6.he.net icmp_seq=1 Destination unreachable: No route
Any idea ?

I am also connected to the FRA tunnel and also had problems. Today in the morning tserv6.fra1.ipv6.he.net was not reachable via ipv4 and now it is so they are probably working on it.

I have just checked and for eg tserv10.par1.ipv6.he.net, tserv5.lon1.ipv6.he.net, tserv9.chi1.ipv6.he.net, are also affected.
So they have a lot of work.

It looks like HE internal ipv6 routing is having a problem all over the world.
« Last Edit: June 16, 2008, 09:23:41 AM by piojan »
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1722
Re: No route
« Reply #2 on: June 16, 2008, 10:16:23 AM »

The German tunnel-server required some work and is back up now.

I'm not seeing any other IPv6 routing issues going on "all over the world", or with the other tunnel servers you listed.

If you can report the problems you see to ipv6@he.net so we can track in our ticket system, that would be most helpful.

Thanks!
« Last Edit: June 16, 2008, 10:21:37 AM by broquea »
Logged

piojan

  • Jr. Member
  • **
  • Posts: 85
Re: No route
« Reply #3 on: June 16, 2008, 10:26:19 AM »

I might have misunderstude the results of the traceroute like this one:

traceroute6 tserv5.lon1.ipv6.he.net
 5  pionier-bckp.rt1.poz.pl.geant2.net (2001:798:23:10aa::5)  26.304 ms  30.89 ms  26.241 ms
 6  so-7-1-0.rt1.fra.de.geant2.net (2001:798:cc:1401:2301::1)  68.086 ms  46.717 ms  42.367 ms
 7  2001:450:2002:70::1 (2001:450:2002:70::1)  191.21 ms  196.367 ms  201.302 ms
 8  ams-ix.he.net (2001:7f8:1::a500:6939:1)  187.152 ms  180.933 ms  178.56 ms
 9  10gigabitethernet1-4.core1.lon1.he.net (2001:470:0:3f::1)  179.052 ms  181.771 ms  184.048 ms
10  10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1)  178.218 ms  181.633 ms  188.244 ms
11  10gigabitethernet3-1.core1.sjc2.he.net (2001:470:0:33::1)  269.632 ms  270.517 ms  273.488 ms
12  * * *
13  * * *
14  * * *

Or form you LG:
Sending 1, 16-byte ICMPv6 Echo to 2001:470:0:68::1
timeout 5000 msec, Hop Limit 64
Request timed out.
No reply from remote host.
Storing [core1.chi1.he.net ping ipv6 2001:470:0:68::1]

If so - sorry.

Cheers
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1722
Re: No route
« Reply #4 on: June 16, 2008, 10:56:00 AM »

Agreed, that is odd behavior for the loopback address on both tunnel-servers. I'll fiddle around and see why that isn't happy. BGP between the tunnel-servers and core routers is operational though, so tunnel traffic won't be affected by any issues with the loopback addresses.

I might have misunderstude the results of the traceroute like this one:

traceroute6 tserv5.lon1.ipv6.he.net
 5  pionier-bckp.rt1.poz.pl.geant2.net (2001:798:23:10aa::5)  26.304 ms  30.89 ms  26.241 ms
 6  so-7-1-0.rt1.fra.de.geant2.net (2001:798:cc:1401:2301::1)  68.086 ms  46.717 ms  42.367 ms
 7  2001:450:2002:70::1 (2001:450:2002:70::1)  191.21 ms  196.367 ms  201.302 ms
 8  ams-ix.he.net (2001:7f8:1::a500:6939:1)  187.152 ms  180.933 ms  178.56 ms
 9  10gigabitethernet1-4.core1.lon1.he.net (2001:470:0:3f::1)  179.052 ms  181.771 ms  184.048 ms
10  10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1)  178.218 ms  181.633 ms  188.244 ms
11  10gigabitethernet3-1.core1.sjc2.he.net (2001:470:0:33::1)  269.632 ms  270.517 ms  273.488 ms
12  * * *
13  * * *
14  * * *

Or form you LG:
Sending 1, 16-byte ICMPv6 Echo to 2001:470:0:68::1
timeout 5000 msec, Hop Limit 64
Request timed out.
No reply from remote host.
Storing [core1.chi1.he.net ping ipv6 2001:470:0:68::1]

If so - sorry.

Cheers
« Last Edit: June 16, 2008, 12:51:04 PM by broquea »
Logged

piojan

  • Jr. Member
  • **
  • Posts: 85
Re: No route
« Reply #5 on: June 16, 2008, 11:23:15 AM »

Agreed, that is odd behavior for the loopback address on both tunnel-servers.
Probably all of the tunnel-servers have the same unreachablity.
Eg. traceroute6 tserv8.dal1.ipv6.he.net
Quote
BGP between the tunnel-servers and core routers is operational though, so tunnel traffic won't be affected by any issues with the loopback addresses.
I haven't figuered any other way of seeing if this is only tserv6.fra1.ipv6.he.net unavailable or otheres then by tracerouting (loopback) adresses.
So that was worrying that they all routed to SJC. My apologise for my comment about "all over the world".

Cheers.
Logged