SixXS::Sunset 2017-06-06

AVM 7270v3 fails to connect
[de] Shadow Hawkins on Monday, 09 April 2012 23:39:29
Hi, I got a tunnel (static IP, not AYIYA/heartbeat) and a subnet activated this afternoon, but I cannot connect. I filled in the information according to the Wiki pages in the following form: Username: XXXX-RIPE/T##### Password: My TIC-Password Tunnel-ID: T##### I get the following error message from my router: "Internetverbindung IPv6 (SixXS Tunnel) ist fehlgeschlagen: Heartbeat-Untersttzung erforderlich (6in4-static)." So it says that it needs the heartbeat; does a static tunnel not work with this router? How do I set up my tunnel and router correctly if I have got a static IPv4 address? Regards, Christoph
AVM 7270v3 fails to connect
[de] Shadow Hawkins on Tuesday, 10 April 2012 04:18:55
Hi, The router's log message in my last post was the result when setting it up via its SixXs specific option, with this I got no tunnel at all (no global IPv6 address on any interface). I've tested other configuration options as well (the router is capable of native connections and offers the following tunneling methods: "6to4", "6RD", "SixXs", "6in4") and now I've got some new information, interesting test results and new questions: I initially had problems with 6to4, which was my reason to try SixXs instead, I've resolved those now, so 6to4 works correctly. Nonetheless I'd like to get my SixXs tunnel also up and running. I mention this to make the following remarks more clear. No matter which tunneling method (6to4, 6in4) is chosen, the router won't display the DNS servers on the configuration page, the two fields remain empty, but resolution works. This made me think that 6to4 was broken in the first place, but now I think this is the router's normal behaviour; perhaps DNS servers are only shown on native v6 connections. When looking at my tunnel's configuration page at SixXs in order to check whether I made a mistake, I noticed that SixXs uses 6in4, so I had the idea to use my router's generic 6in4 configuration option rather than the SixXs specific one. The following paragraphs are all about the generic 6in4 configuration: In the generic 6in4 configuration there's no place to enter a TIC password and server; I assume this isn't really necessary to set up the tunnel? Do I have to delete the password on the SixXs tunnel configuration page to make it work without the TIC server? The router correctly gets a subnet, my hosts also get valid IPv6 addresses. IPv6 DNS resolution works (I see AAAA records being returned in Tcpdump). However, I cannot get any data through the tunnel. IPv4 connections to web pages are significantly delayed or even time out. I think this is because IPv6 is tried first and then fails. My router shows the following log entries:
09.04.1223:49:21Internetverbindung IPv6 (6to4) wurde erfolgreich hergestellt. Prfix: 2001:4dd0:ff00:e32::/64. 09.04.1223:49:21Internetverbindung IPv6 wurde erfolgreich hergestellt. IP-Adresse: 2001:4dd0:ff00:e32::2
Please note that it incorrectly says "6to4" despite of "6in4" being configured. This might be a display-only bug in the firmware, but I'm not sure about this. The messages mean that a connection was set up successfully, but I get the problems I described above. I hope you've got a solution for me or at least an idea what to try next. If I need to change my tunnel type into a heartbeat one, I'm in a deadlock situation, because I'm a new user and have only got 10 ISK left, cannot get the tunnel to work to earn more ISK, but would need 15 ISK to make the change. Christoph
AVM 7270v3 fails to connect
[ch] Jeroen Massar SixXS Staff on Tuesday, 10 April 2012 11:12:03
In the generic 6in4 configuration there's no place to enter a TIC password and server; I assume this isn't really necessary to set up the tunnel? Do I have to delete the password on the SixXs tunnel configuration page to make it work without the TIC server?
TIC is just a method for transfering the tunnel details from a tunnel broker to the host that the tunnel gets configured on. Fritz!Box only apparently supports TIC when configured to Heartbeat tunnel.
09.04.1223:49:21Internetverbindung IPv6 (6to4) wurde erfolgreich hergestellt. Prfix: 2001:4dd0:ff00:e32::/64.
If I need to change my tunnel type into a heartbeat one, I'm in a deadlock situation, because I'm a new user and have only got 10 ISK left, cannot get the tunnel to work to earn more ISK, but would need 15 ISK to make the change.
One can always change tunnel types, you'll just go into the minus. I think you that you should likely reset the configuration of your Fritz!Box to a known default state and then try to configure a static tunnel instead. That is of course if you actually have a static endpoint that never changes, otherwise heartbeat is the right type to use.
AVM 7270v3 fails to connect
[ch] Jeroen Massar SixXS Staff on Tuesday, 10 April 2012 11:07:31
"Internetverbindung IPv6 (SixXS Tunnel) ist fehlgeschlagen: Heartbeat-Untersttzung erforderlich (6in4-static)."
If you configure a Fritz!Box using TIC (thus the "SixXS" option), then you need to have a heartbeat tunnel. As you have a static tunnel, you should use the static 6in4 option. (Bit odd that Fritz!Box does not recognize that configuration method, but oh well)
AVM 7270v3 fails to connect
[de] Shadow Hawkins on Tuesday, 10 April 2012 15:48:53
Hi, as I described in my second message, I've done this, and set up 6in4 manually without using TIC, but I've got severe problems. Following additional information: 1) The tunnel (ID=T92050) apparently is up and there's traffic in both directions, I see red and green bars on its RRD graphics. 2) IPv4 is negatively affected. According to ipv6-test.com my browser uses v4 if both protocols are available (tested also with a running 6to4 configuration). Many web sites, among them sixxs.net (has got AAAA DNS records), suffer from long delays and timeouts. Others, such as wikipedia.org (hasn't got an AAAA DNS record according to dig) still work normally. 3) Ipv6-test.com and test-ipc6.com say I've got no v6 connectivity. 4) Ping6 to 2001:960:800::2, one of the SixXS addresses, fails. My situation is now as follows: A) 6to4 does work as expected on my router. B) 6in4 does not; for the symptoms, see above. C) If it would work, 6in4 via SixXS would probably be the better choice (9 hops/25ms latency to the next 192.99.88.1 anycast gateway for 6to4, 5 hops/20ms latency to my SixXS tunnel endpoint.) Have you got any ideas what I can try? Regards and thank you for the answers, Christoph
AVM 7270v3 fails to connect
[ch] Jeroen Massar SixXS Staff on Tuesday, 10 April 2012 17:57:14
1) The tunnel (ID=T92050) apparently is up and there's traffic in both directions, I see red and green bars on its RRD graphics.
Having spikes in the graphs might just be from the ICMP tests that the PoP does and your Fritz!Box replying.
Many web sites, among them sixxs.net (has got AAAA DNS records), suffer from long delays and timeouts.
This can mean two things: you have a broken DNS recursor somewhere and/or broken connectivity.
3) Ipv6-test.com and test-ipc6.com say I've got no v6 connectivity.
While your Fritz!Box might have connectivity, what is the full configuration of the client.
A) 6to4 does work as expected on my router.
Are you using 6to4 or the connectivity provided by SixXS, it is an either/or question, as they will not easily work together.
B) 6in4 does not; for the symptoms, see above.
Does not do what? You'll need to detail the exact configuration of your Fritz!Box and your client hosts if you want anybody to help you with this.
solved: AVM 7270v3 fails to connect
[de] Shadow Hawkins on Tuesday, 10 April 2012 18:35:54
I tried 6to4 and 6in4 alternatively, not at the same time, of course. The router allows one of: "native", "auto" (= try "native" on connect, if that fails, try "6to4"), "6to4", "SixXS" (= heartbeat tunnel ONLY, no AYIYA, not static), "6RD", "6in4". "6in4" failed with all those weird symptoms mentioned in my earlier posts. I have now found the solution. The Fritz boxen have four configuration fields for 6in4: 1) The IPv4 address of the tunnel endpoint. 2) The IPv6 address of the tunnel endpoint. 3) The IPv6 address of the router's side of the tunnel endpoint. 4) The IPv6 address of the routed subnet. The last point was the failure's reason, I thought I had to fill in the tunnel's subnet there, which is different. The addresses were so similar that I at first didn't notice that the routed subnet is totally different from the tunnel's subnet (mine has an 8 where the tunnel has a 0, one important hex digit of a difference). I will now update the Wiki page for AVM Fritz routers accordingly to make clear that they: 1) CANNOT use AYIYA; 2) MUST use a heartbeat tunnel and have a TIC password set up when you've got a dynamic v4 IP as usual, this is the only thing the "SixXS" configuration option of the router supports; 3) MUST use the generic "6in4" option if you've got a static v4 IP AND have set up a static tunnel rather than heartbeat at SixXS. I'll also include what information exactly needs to be filled into the configuration fields to actually succeed. I've noticed that there's an extra page for one AVM model and one redirection to "Fritz!Box generic" on the "HOW-TO" category page, but the extra page duplicates information from the generic page only (or vice-versa). Is it OK to change this into a redirection and make additional redirections for all the router models which are covered by the generic page? I would of course double check that no information will be lost. Thank you for your patient answers. Christoph

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker