|
Ticket ID: SIXXS #11297693 Ticket Status: User PoP: deham02 - Easynet (Hamburg)
Tunnel is up, but no connectivity
![[de]](/s/countries/de.gif) Carmen Sandiego on Saturday, 22 March 2014 10:22:05My tunnel TKJ3-SIXXS/T25119 is up, but there seems to be no internet connectivity. Anything I try to reach pretty much comes back the same as this:.
C:\>ping -6 -n 3 ipv6.l.google.com
Ping wird ausgefhrt fr ipv6.l.google.com [2a00:1450:4008:c01::66] mit 32 Bytes
Daten:
Zeitberschreitung der Anforderung.
Zeitberschreitung der Anforderung.
Zeitberschreitung der Anforderung.
Ping-Statistik fr 2a00:1450:4008:c01::66:
Pakete: Gesendet = 3, Empfangen = 0, Verloren = 3
(100% Verlust),
C:\>tracert -6 ipv6.google.com
Routenverfolgung zu ipv6.l.google.com [2a00:1450:4008:c01::65] ber maximal 30 A
bschnitte:
1 <1 ms <1 ms <1 ms fritz.box [2001:6f8:1d9d:0:be05:43ff:fe26:8845]
2 * * * Zeitberschreitung der Anforderung.
3 * * * Zeitberschreitung der Anforderung.
4 * * * Zeitberschreitung der Anforderung.
5 * * * Zeitberschreitung der Anforderung.
6 * * ^C
Tunnel is up, but no connectivity
My tunnel TKJ3-SIXXS/T25119 is up
Why do you think your tunnel is up? Can you ping the PoP side of the tunnel for instance?
ping -6 -n 3 ipv6.l.google.com
What does google have to do with your tunnel being "up"? (and are you sure they are pingable).
1 <1 ms <1 ms <1 ms fritz.box [2001:6f8:1d9d:0:be05:43ff:fe26:8845] 2 * * * Zeitberschreitung der Anforderung.
That demonstrates that you do not reach the PoP, hence your tunnel is not up.
Your Live Tunnel Status shows:
HB Sender Mismatch : 187983, last: 5.28.78.254 2014-03-22 18:02:30 (1395511350; 0 days 00:00:55 ago)
That certainly explains why things do not work. Apparently your Fritz!Box is using a wrong heartbeat password or encoding it wrong.
Interestingly there was somebody else recently who had similar issues; did you recently update your software version of the Fritz!Box?
Tunnel is up, but no connectivity
Carmen Sandiego on Sunday, 30 March 2014 06:29:29Why do you think your tunnel is up? Can you ping the PoP side of the tunnel for instance?
Fritzbox, istself means connected to SIXXS ->
Internet, IPv6 - verbunden seit 22.03.2014, 10:18 Uhr, Tele Columbus, IPv6-Prfix: 2001:6f8:1d9d::/48
all devices got an IPv6-adress
IPv6-Adresse. . . . . . . . . . . : 2001:6f8:1d9d:0:6014:b94a:84f0:a152
i can reach all my intranet devices via ping to the IPv6-adresses
did you recently update your software version of the Fritz!Box?
the fritzbox had been updated to the latest firmware FRITZ!OS 6.03 (84.06.03) from 07.Feb.2014
I also made a complete reset of the Fritzbox, but the results ar the same
Tunnel is up, but no connectivity
the fritzbox had been updated to the latest firmware FRITZ!OS 6.03 (84.06.03) from 07.Feb.2014
You are likely affected by some Fritz!Box bug where they are sending wrong heartbeats.
See also this thread where somebody had a similar issue.
From the Live Tunnel Status:
Last Heartbeat : 2014-01-15 07:27:43 (1389770863; 74 days 00:23:03 ago)
HB Sender Mismatch : 209767, last: 5.28.78.254 2014-03-30 07:50:29 (1396165829; 0 days 00:00:17 ago)
As long as your Fritz!Box does not send valid heartbeats, the tunnel will not work.
Tunnel is up, but no connectivity
Carmen Sandiego on Saturday, 05 April 2014 13:07:53 As long as your Fritz!Box does not send valid heartbeats, the tunnel will not work.
Now, i think so too. I tested my network configuration with a linux device and configured AICCU. By this configuration i got an etablished tunnel and i could work with IPv6-adresses outside of my network.
In this case a opened an incident by the AVM-Support, because the problem seems to occure since the Update to FRITZ!OS 6.01 (84.06.01) and later
Thanks a lot for you help ;)
This thread can closed
Tunnel is up, but no connectivity
Carmen Sandiego on Monday, 30 November 2015 10:36:57
Torsten Kirchner wrote:
|
![[ch]](/s/countries/ch.gif)
on Saturday, 22 March 2014 18:05:43
Posting is only allowed when you are