SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1211600
Ticket Status: User

PoP: deham01 - Easynet (Hamburg)

aiccu connected but tunnel not working
[de] Shadow Hawkins on Wednesday, 23 September 2009 08:30:30
Hi, since yesterday evening I have problems using IPv6 Internet. Me and a friend of mine, using the same PoP lost connection to IRC (connected via IPv6) at the same time and were only able to rejoin via IPv4. My "tunnel-information"-page states, my external IPv4 address is 0.0.0.0, which seems to be wrong. I ran "aiccu test" and the logs say: Sep 23 07:22:31 batman aiccu: Succesfully retrieved tunnel information for T18406 I am able to ping4 the deham01, but not ping6 it. (kind of logical, because the tunnel seems to be not established). The last time, I got connectivity problems, I figured out, everything was my fault (mostly clock-screw kind of problems ;)) but this time I can't see the problem on my side. regards Julian
aiccu connected but tunnel not working
[de] Carmen Sandiego on Wednesday, 23 September 2009 09:12:57
I can confirm: I experience exactly the same problem on my "heartbeat" tunnel T7892. Working: - ping local tunnel endpoint via IPv4 - ping remote tunnel endpoint via IPv4 - ping local tunnel endpoint via IPv6 Not working: - ping remote tunnel endpoint via IPv6 I tried ping6 to my tunnel endpoints from the outside IPv6 world, from two different hosts, one connected via another sixxs PoP and one connected through university of karlsruhe with the same results: From 2001:6f8:800:1003::2 icmp_seq=1 Destination unreachable: No route (deham01.sixxs.net has IPv6 address 2001:6f8:800:1003::2) regards, Felix
aiccu connected but tunnel not working
[ch] Jeroen Massar SixXS Staff on Wednesday, 23 September 2009 09:48:10
From 2001:6f8:800:1003::2 icmp_seq=1 Destination unreachable: No route
(deham01.sixxs.net has IPv6 address 2001:6f8:800:1003::2)
You can receive this from remote hosts when your tunnel is not configured. Like the above comment, try actually providing details. Stating "this works" and "this does not work" does not give us any insight on what the problem might be.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 23 September 2009 09:45:09
Message is Locked
The state of this ticket has been changed to user
aiccu connected but tunnel not working
[ch] Jeroen Massar SixXS Staff on Wednesday, 23 September 2009 09:46:49
using the same PoP lost connection to IRC
We really cannot care less about IRC. Now, if you would at least have provided a traceroute6 to the remote host, routing tables, interface tables, etc (see the big orange box when you submit something to the forum which points to the forum page) then we could possibly make any use of the 'details' you provided. Without details we really cannot help.
aiccu connected but tunnel not working
[de] Shadow Hawkins on Wednesday, 23 September 2009 12:28:43
We really cannot care less about IRC.
Actually this is a good indication to find out, when exactly the tunnel stopped to work. Since it stopped for both of us at the same time, the problem most likely is the remote end-point. That's why I mentioned IRC. Concerning the traceroute6, I think, I didn't clarify, I wasn't able to ping6 the remote end-point of my tunnel. Sorry for being inaccurate here. Anyway, this problem seems to be fixed, as stated in ticket #1211602: https://www.sixxs.net/tickets/?msg=tickets-1211602 And since the dates (timestamps) mentioned here and in the other ticket highly relate, I guess this has been the same problem. Thanks for your help Julian

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

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