Ticket ID: SIXXS #949546 Ticket Status: User PoP: dkcph01 - Availo (Copenhagen)
Traffic not passing and router unreachable
Shadow Hawkins on Thursday, 22 January 2009 19:47:14
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Since 0700 2009-01-22 traffic has ceased flowing from my ayiya tunnel to dkcph01. At around 1930 I was able to re-establish the tunnel, but traffic is still not flowing, nor can I ping the pop router address through my other working tunnel. Please see the following diagnostic information:-
# Try to ping the pop over ipv4
$ ping dkcph01.sixxs.net -c 1
PING dkcph01.sixxs.net (93.158.77.42) 56(84) bytes of data.
64 bytes from dkcph01.sixxs.net (93.158.77.42): icmp_seq=1 ttl=59 time=7.73 ms
--- dkcph01.sixxs.net ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 7.730/7.730/7.730/0.000 ms
# Try to ping the pop over ipv6 using the tunnel to dkcph01
$ ping6 -c 5 -s 2001:16d8:dd00:3a::2 2001:16d8:dd00:3a::1
PING 2001:16d8:dd00:3a::1(2001:16d8:dd00:3a::1) 2001 data bytes
--- 2001:16d8:dd00:3a::1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms
# Show the tunnel address
$ /sbin/ip -6 addr | tail -n 5
10: sixxs-T19149: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1280 qlen 500
inet6 2001:16d8:dd00:3a::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::14d8:dd00:3a:2/64 scope link
valid_lft forever preferred_lft forever
# Try to ping the pop router address using tunnel to noosl01
$ ping6 -c 5 -s 2001:16d8:ee0f::1 2001:16d8:dd00:38::1
PING 2001:16d8:dd00:38::1(2001:16d8:dd00:38::1) 2001 data bytes
--- 2001:16d8:dd00:38::1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4000ms
# Traceroute to the dkcph01 pop router through noosl01
$ traceroute6 -s 2001:16d8:ee0f::1 2001:16d8:dd00:38::1
traceroute to 2001:16d8:dd00:38::1 (2001:16d8:dd00:38::1) from 2001:16d8:ee0f::1, 30 hops max, 16 byte packets
1 gw-26.osl-01.no.sixxs.net (2001:16d8:ee00:19::1) 31.168 ms 25.416 ms 24.607 ms
2 2002-sixxs.cr0-r23.ver-osl.no.ip6.p80.net (2001:16d8:aaaa:4::1) 24.511 ms 24.213 ms *
3 v1611-r23.cr0-r69.tc-sto.se.ip6.p80.net (2001:16d8:1:1611::69) 34.44 ms 31.835 ms 31.651 ms
4 v1315-r69.cr0-r84.kn1-sto.se.ip6.p80.net (2001:16d8:1:1315::84) 31.44 ms 31.339 ms 31.092 ms
5 v1317-r84.cr0-r73.gbl-mlm.se.ip6.p80.net (2001:16d8:1:1317::73) 44.823 ms 47.05 ms 45.814 ms
6 v1306-r73.cr0-r72.gbl-cph.dk.ip6.p80.net (2001:16d8:1:1306::72) 45.48 ms 48.213 ms 47.689 ms
7 sixxs-cph-demarc0.cust.ip6.p80.net (2001:16d8:aaaa:5::2) 48.282 ms !N 51.458 ms !N 50.648 ms !N
Traffic not passing and router unreachable
Shadow Hawkins on Sunday, 19 July 2009 14:09:51
The same problem is occurring today, starting 10:33:38 CEST. Since noosl01 is down, now I have no IPv6 connectivity at all.
Traffic not passing and router unreachable
Shadow Hawkins on Sunday, 19 July 2009 14:32:16
Jul 19 14:28:15 sol aiccu-sixxs-T19077: Succesfully retrieved tunnel information for T19077
Jul 19 14:28:15 sol aiccu-sixxs-T19077: AICCU running as PID 12237
Jul 19 14:28:15 sol kernel: sixxs-T19077: Disabled Privacy Extensions
Jul 19 14:28:15 sol aiccu-sixxs-T19077: [AYIYA-start] : Anything in Anything (draft-02)
Jul 19 14:28:15 sol aiccu-sixxs-T19077: [AYIYA-tun->tundev] : (Socket to TUN) started
8: sixxs-T19077: <POINTOPOINT,MULTICAST,NOARP,UP,10000> mtu 1428 qdisc pfifo_fast qlen 500
link/[65534]
inet6 2001:16d8:dd00:38::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::14d8:dd00:38:2/64 scope link
valid_lft forever preferred_lft forever
PING dkcph01.sixxs.net (93.158.77.42) 56(84) bytes of data.
64 bytes from dkcph01.sixxs.net (93.158.77.42): icmp_seq=1 ttl=59 time=7.66 ms
64 bytes from dkcph01.sixxs.net (93.158.77.42): icmp_seq=2 ttl=59 time=8.86 ms
64 bytes from dkcph01.sixxs.net (93.158.77.42): icmp_seq=3 ttl=59 time=7.50 ms
^C
--- dkcph01.sixxs.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2006ms
rtt min/avg/max/mdev = 7.506/8.012/8.864/0.605 ms
listening on sixxs-T19077, link-type RAW (Raw IP), capture size 65535 bytes
14:28:55.214899 IP6 cl-57.cph-01.dk.sixxs.net > gw-57.cph-01.dk.sixxs.net: ICMP6, echo request, seq 1, length 64
14:28:56.226980 IP6 cl-57.cph-01.dk.sixxs.net > gw-57.cph-01.dk.sixxs.net: ICMP6, echo request, seq 2, length 64
14:28:57.226981 IP6 cl-57.cph-01.dk.sixxs.net > gw-57.cph-01.dk.sixxs.net: ICMP6, echo request, seq 3, length 64
14:28:58.227000 IP6 cl-57.cph-01.dk.sixxs.net > gw-57.cph-01.dk.sixxs.net: ICMP6, echo request, seq 4, length 64
Traffic not passing and router unreachable
Shadow Hawkins on Monday, 20 July 2009 00:20:01
Tunnel is working again as of 2009-07-20 00:15.
Traffic not passing and router unreachable
Shadow Hawkins on Thursday, 22 January 2009 21:14:26
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Now at 2110 CET the tunnel appears to be working again so the ticket can be closed.
$ traceroute6 -s 2001:16d8:dd00:3a::2 www.sixxs.net
traceroute to www.m.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:16d8:dd00:3a::2, 30 hops max, 16 byte packets
1 gw-59.tunnels-cph-01.dk.sixxs.net (2001:16d8:dd00:3a::1) 8.209 ms 7.994 ms 9.178 ms
2 3229-sixxs.cr0-r72.gbl-cph.dk.ip6.p80.net (2001:16d8:aaaa:5::1) 9.357 ms 9.211 ms 8.495 ms
3 v1308-r72.cr0-r70.tc2-ams.nl.ip6.p80.net (2001:16d8:1:1308::70) 135.647 ms 20.253 ms 19.654 ms
4 ams-ix2.ipv6.concepts.nl (2001:7f8:1::a501:2871:2) 19.84 ms 19.881 ms 19.77 ms
5 2001:838:5:2::1 (2001:838:5:2::1) 20.121 ms 20.952 ms 19.972 ms
6 2001:838:5:4::1 (2001:838:5:4::1) 20.25 ms 20.443 ms 20.826 ms
7 2001:838:0:10::2 (2001:838:0:10::2) 22.39 ms 23.773 ms 23.685 ms
8 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 22.908 ms 22.459 ms 22.693 ms
Traffic not passing and router unreachable
Jeroen Massar on Friday, 23 January 2009 10:37:18
Please actually read the "Reporting Problems" section on the Contact page and provide the details requested there.
"It does not work" and later "Now it does work" kind of statements don't really help at all.
State change: user
Jeroen Massar on Friday, 23 January 2009 10:37:22
The state of this ticket has been changed to user
Posting is only allowed when you are logged in. |