SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1051859
Ticket Status: User

PoP: dedus01 - SpeedPartner GmbH (Duesseldorf)

Two tunnels down
[de] Shadow Hawkins on Sunday, 05 April 2009 01:16:06
Hi,... my both tunnels on dedus01 are down.The first one does not come up again after a reboot yesterday. The second one was suddenly disconnected today, while my ssh session was active. Tunnel T20116 (ayiya) 2a01:198:200:3c4::2 Tunnel T17649 (ayiya) 2a01:198:200:226::2 None of the Tunnel-Endpoints respond to ping. $ ping6 -c 4 2a01:198:200:226::2 PING 2a01:198:200:226::2(2a01:198:200:226::2) 56 data bytes From 2a01:198:200::2 icmp_seq=1 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=2 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=3 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=4 Destination unreachable: No route --- 2a01:198:200:226::2 ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3048ms $ ping6 -c 4 2a01:198:200:226::1 PING 2a01:198:200:226::1(2a01:198:200:226::1) 56 data bytes From 2a01:198:200::2 icmp_seq=1 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=2 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=3 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=4 Destination unreachable: No route --- 2a01:198:200:226::1 ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3048ms $ ping6 -c 4 2a01:198:200:3c4::2 PING 2a01:198:200:3c4::2(2a01:198:200:3c4::2) 56 data bytes From 2a01:198:200::2 icmp_seq=1 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=2 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=3 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=4 Destination unreachable: No route --- 2a01:198:200:3c4::2 ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3046ms $ping6 -c 4 2a01:198:200:3c4::1 PING 2a01:198:200:3c4::1(2a01:198:200:3c4::1) 56 data bytes From 2a01:198:200::2 icmp_seq=1 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=2 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=3 Destination unreachable: No route From 2a01:198:200::2 icmp_seq=4 Destination unreachable: No route --- 2a01:198:200:3c4::1 ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3047ms best regards Stefan --
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 05 April 2009 18:50:59
Message is Locked
The state of this ticket has been changed to user
Two tunnels down
[ch] Jeroen Massar SixXS Staff on Sunday, 05 April 2009 18:51:58
That you can't ping is great, especially the "No route" partcoming from your local machine. You might want to check the "Reporting Problems" checklist and provide the details requested there.
Two tunnels down
[de] Shadow Hawkins on Sunday, 05 April 2009 22:50:33
Hi, thank you for your answer. Then i assume, that if a tunnel goes down for whatever (client)reason, the Tunnel end on the PoP ( [prefix]::1 ) goes down too. (?) And as long as the pop itself (2a01:198:200::2 for me) is reachable, all should be fine and i have to look at myself? $traceroute6 -n 2a01:198:200:3c4::1 traceroute to 2a01:198:200:3c4::1 (2a01:198:200:3c4::1), 30 hops max, 80 byte packets 1 2001:6f8:11d3:0:21e:8cff:fe46:b28a 0.392 ms 0.488 ms 0.473 ms 2 2001:6f8:900:b67::1 27.984 ms 35.583 ms 42.453 ms 3 2001:6f8:800:1003::209:55 45.543 ms 50.987 ms 55.601 ms 4 2001:6f8:800:0:1:0:d4e0:49a 63.542 ms 72.368 ms 75.994 ms 5 2001:6f8:1:0:87:86:71:240 79.471 ms * * 6 2001:6f8:1:0:86:87:77:64 104.269 ms * * 7 2001:6f8:1:0:87:86:77:62 112.333 ms * * 8 2001:6f8:1:0:87:86:77:249 74.633 ms * * 9 2001:7f8::a2dc:0:1 69.670 ms 64.887 ms 59.932 ms 10 2001:7f8:3a:e102::2 58.547 ms 59.481 ms 51.907 ms 11 2a01:198:200::2 50.937 ms !N 48.196 ms !N 43.043 ms !N Best regards Stefan --
Two tunnels down
[ch] Jeroen Massar SixXS Staff on Sunday, 05 April 2009 23:51:26
Then i assume, that if a tunnel goes down for whatever (client)reason,
the Tunnel end on the PoP ( [prefix]::1 ) goes down too. (?)
If you have a heartbeat or AYIYA tunnel, then <tunnel>::1 won't be available when the tunnel is not configured, which happens when no valid heartbeat or AYIYA packets are send to the PoP for 120 seconds.
And as long as the pop itself (2a01:198:200::2 for me) is reachable,
Reachable from where?
Two tunnels down
[de] Shadow Hawkins on Monday, 06 April 2009 00:13:57
If you have a heartbeat or AYIYA tunnel, then <tunnel>::1 won't be available when the tunnel is not configured, ...
Ah ok, that explains it. Thanks!
Reachable from where?
From the "outside" e.g: from another tunnel that is connected to another PoP. best regards Stefan --

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

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