Hi since this noon tunnels over the frankfurt server don't seem to work anymore. I tried it with my main tunnel and a new one i created for testing from several hosts but all tests had the same result.
A traceroute from inside the tunnel looks like this:
traceroute to heise.de (2a02:2e0:3fe:100::8) from 2001:470:1f0b:196::5eed, 30 hops max, 24 byte packets
1 [username].tunnel.tserv6.fra1.ipv6.he.net (2001:470:1f0a:196::1) 12.962 ms 7.693 ms 7.852 ms
2 * * *
3 * * *
4 * * *
5 * * *
[...]
and from another ipv6 host outside the tunnel the traceroute looks like this:
traceroute to 2001:470:1f0b:196::deed (2001:470:1f0b:196::deed), 30 hops max, 80 byte packets
1 gw-443.leo-01.de.sixxs.net (2a01:1e8:e100:1ba::1) 87.881 ms 87.865 ms 87.858 ms
2 2a01:1e8:e000::2 (2a01:1e8:e000::2) 87.883 ms 87.880 ms 92.066 ms
3 2a01:1e8:e000::1 (2a01:1e8:e000::1) 92.997 ms 99.664 ms 99.675 ms
4 c1208gsr-lo-0.Z10a.STG.interscholz.net (2a01:1e8:1:1::4) 111.816 ms 121.379 ms 121.385 ms
5 c12gsr-lo-0.Z10a.STG.interscholz.net (2a01:1e8:2:1::2) 129.007 ms * *
6 c12gsr-lo-0.FRA1.FRA.interscholz.net (2a01:1e8:1:1::8) 160.062 ms * *
7 30gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1) 104.617 ms 104.564 ms 104.589 ms
8 * * *
9 * * *
10 * * *
[...]
To me it looks like someone/something messed up the routing on/to that server.
Same here, using tserv1.fra1.he.net. I can still ping the tunnel server, but nothing seems to go through the tunnel.
I think the problems began sometime around 11:00 CEST.
Quote from: kart0ffelsack on May 13, 2013, 07:04:07 AM
Hi since this noon tunnels over the frankfurt server don't seem to work anymore. I tried it with my main tunnel and a new one i created for testing from several hosts but all tests had the same result.
I can also confirm this problem, no packets can be transmitted via tserv1 in Frankfurt.
Quote from: pf2802 on May 13, 2013, 07:12:27 AM
I think the problems began sometime around 11:00 CEST.
Somewhere between 11:50 and 11:55 CEST according to my smokeping stats.
Did anyone tell ipv6@he.net?
I have same problem.
Letter to ipv6@he.net sent.
It's been down for about five hours now.
(http://www.thinkbroadband.com/ping/share-large/781431314a095368a201b6177cfbd3cc-13-05-2013.png)
Quote from: cholzhauer on May 13, 2013, 07:56:10 AM
Did anyone tell ipv6@he.net?
Yes, I did before this thread started. Ticket ID #2163996
my problem is solved. all ok.
Yes, the problem seems to be fixed. :-)
It is down again. I have updated ticket #2163996
(http://www.thinkbroadband.com/ping/share-large/484b6cc3b115ee60b02c235720039c1b-14-05-2013.png)
It is down again. This time the symptoms are different. IPv4 packets cannot be delivered to the tunnel server. But some of the IPv6 packets send to the tunnel server are delivered over the tunnel. I have opened ticket #2171493 about this issue.
The ping6 -n google.com command I have had running for 9½ minutes just responded. And I actually got all 585 echo replies back, the first one arrived with a 573095 ms roundtrip time.