Tickets - ptlis01 PoP - isolated? - part2 :: SixXS - IPv6 Deployment & Tunnel Broker

Ticket ID: SIXXS #8782702
Ticket Status: Resolved

PoP:

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 08 February 2013 23:01:16

My post on ticket 8777218 disapear (or never got in?), but at that time, the pop was marked up and i had not route to outside of network 2001:b18:*. right now the problem persist, the pop is again marked up but i still have no route to the "great internet": $ tracepath6 -n www.sixxs.net 1?: [LOCALHOST] 0.024ms pmtu 1280 1: 2001:b18:400f::1 3.364ms 1: 2001:b18:400f::1 1.191ms 2: 2001:b18:2000:22::1 13.200ms 3: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 12.801ms asymm 2 4: no reply 5: no reply 6: no reply 7: no reply 8: no reply i tried to traceroute from other ipv6 netowrk and got this: $ traceroute6 ipv6.motaleite.net -n traceroute to ipv6.motaleite.net (2001:b18:400f:0:461e:a1ff:fe3b:775b), 30 hops max, 80 byte packets 1 2001:690:2006:200::ffff 1.966 ms 2.118 ms 2.333 ms 2 2001:690:2006:1::ffff 0.101 ms 0.146 ms 0.129 ms 3 2001:690:810:4::1 2.607 ms * * 4 2001:690:800:2::4 2.694 ms * * 5 2001:7f8:a:1::12 2.984 ms 3.166 ms * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * I tried to restart the tunnel and the problem persist. Thanks higuita

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 05 September 2013 11:39:35

The connection beyond the PoP seems to be down again. $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net; wget http://ipv6.google.com && rm index.htmlThu Sep 5 13:38:00 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=111 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=110 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 110.648/111.141/111.635/0.595 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 113.979 ms 114.797 ms 117.674 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 118.850 ms 122.099 ms 123.397 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 113.813 ms 115.954 ms 117.669 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 120.984 ms 122.181 ms 124.917 ms 3 2001:b18:0:1000::1 128.532 ms 129.711 ms 131.320 ms 4 2001:b18:0:f:1::5 141.138 ms 142.551 ms 142.729 ms 5 2001:b18:0:f:1::e 154.800 ms 157.724 ms 170.169 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * --2013-09-05 13:38:49-- http://ipv6.google.com/ Resolving ipv6.google.com (ipv6.google.com)... 2a00:1450:4003:802::1013 Connecting to ipv6.google.com (ipv6.google.com)|2a00:1450:4003:802::1013|:80... ^C

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 06 September 2013 06:48:53

The PoP still is down! Can someone please have a look at this? Thanks! $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net; wget http://ipv6.google.com && rm index.html Fri Sep 6 08:46:56 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=90.5 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=86.8 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 86.841/88.684/90.528/1.867 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 88.640 ms 91.195 ms 92.834 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 95.780 ms 96.880 ms 99.840 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 90.233 ms 91.393 ms 94.087 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 95.758 ms 98.363 ms 99.641 ms 3 2001:b18:0:1000::1 102.682 ms 104.668 ms 106.833 ms 4 2001:b18:0:f:1::5 108.748 ms 110.845 ms 113.028 ms 5 2001:b18:0:f:1::e 131.641 ms 131.914 ms 135.518 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * --2013-09-06 08:47:39-- http://ipv6.google.com/ Resolving ipv6.google.com (ipv6.google.com)... 2a00:1450:4003:802::1012 Connecting to ipv6.google.com (ipv6.google.com)|2a00:1450:4003:802::1012|:80... ^C

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Sunday, 08 September 2013 11:05:22

And it's working again. Thanks!

State change: confirmed Locked

Jeroen Massar SixXS Staff

on Tuesday, 12 February 2013 13:33:55

The state of this ticket has been changed to confirmed

State change: resolved Locked

Jeroen Massar SixXS Staff

on Tuesday, 12 February 2013 15:52:08

The state of this ticket has been changed to resolved

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Monday, 04 March 2013 22:39:41

Hi there, I think that the problem isn't solved yet. I'll be happy to give away more info. [root@oracle /home/xumpi]# traceroute6 www.sixy.ch traceroute6 to sixy.ch (2a02:200:3:1::103) from 2001:b18:2000:e4::2, 64 hops max, 12 byte packets 1 gw-229.lis-01.pt.sixxs.net 7.494 ms * 7.860 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 7.582 ms 7.174 ms 9.060 ms 3 2001:b18:0:1000::1 8.678 ms 7.337 ms * 4 2001:b18:0:f:1::5 7.858 ms 8.773 ms 9.362 ms 5 * * * 6 * * * 7 * * * ^C [root@oracle /home/xumpi]# traceroute6 www.sixxs.net traceroute6: Warning: nginx.sixxs.net has multiple addresses; using 2001:838:2:1::30:67 traceroute6 to nginx.sixxs.net (2001:838:2:1::30:67) from 2001:b18:2000:e4::2, 64 hops max, 12 byte packets 1 gw-229.lis-01.pt.sixxs.net 7.359 ms 8.110 ms 7.276 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 7.152 ms 7.875 ms 6.873 ms 3 2001:b18:0:1000::1 8.469 ms 8.593 ms 9.894 ms 4 2001:b18:0:f:1::5 8.181 ms 8.508 ms 11.450 ms 5 * * * ^C [root@oracle /home/xumpi]# traceroute6 www.telecom.pt traceroute6 to www.telecom.pt (2a02:818:2020:5040::1) from 2001:b18:2000:e4::2, 64 hops max, 12 byte packets 1 gw-229.lis-01.pt.sixxs.net 7.265 ms 8.429 ms 7.100 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 7.288 ms 7.968 ms 8.167 ms 3 2001:b18:0:1000::1 8.555 ms 7.871 ms 7.109 ms 4 2001:b18:0:f:1::5 14.551 ms 8.504 ms 17.511 ms 5 * *^C [root@oracle /home/xumpi]# traceroute6 www.nfsi.pt traceroute6 to www.nfsi.pt (2001:b18:0:2:211:43ff:fecd:8c3c) from 2001:b18:2000:e4::2, 64 hops max, 12 byte packets 1 gw-229.lis-01.pt.sixxs.net 8.234 ms 7.249 ms 8.599 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 7.779 ms 8.249 ms 8.376 ms 3 * * 2001:b18:0:1000::1 8.743 ms 4 2001:b18:0:f:1::a 8.926 ms 8.419 ms 9.742 ms 5 2001:b18:0:2:211:43ff:fecd:8c3c 8.928 ms 9.646 ms 8.222 ms [root@oracle /home/xumpi]# traceroute6 ipv6.motaleite.net traceroute6 to ipv6.motaleite.net (2001:b18:400f:0:461e:a1ff:fe3b:775b) from 20 1 gw-229.lis-01.pt.sixxs.net 8.026 ms 7.427 ms 8.214 ms 2 cl-35.lis-01.pt.sixxs.net 17.078 ms 19.272 ms 16.892 ms 3 * * * 4 * *^C [root@oracle /home/xumpi]# traceroute6 www.kame.net traceroute6 to orange.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7) from 2001 1 gw-229.lis-01.pt.sixxs.net 7.701 ms 7.702 ms 6.962 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 7.072 ms 8.737 ms 7.205 ms 3 2001:b18:0:1000::1 8.031 ms 9.090 ms 9.474 ms 4 * 2001:b18:0:f:1::5 8.671 ms 8.488 ms 5 * * * 6 *^C [root@oracle /home/xumpi]# Thanks in advance, Nuno Duarte aka Xumpi

ptlis01 routing intermittent problems

Shadow Hawkins on Thursday, 14 March 2013 18:59:18

Hi I and many ptlist01 users have noted that we have intermittent connectivity problems to several sites. Sometimes all is working fine but then it stop working for most ipv6 sites. Some sites ( www.sixxs.net is a good example) are failing since about one month. We have tried to reopen tickets 8782702, but since one month have passed and the problem persists, i'm trying open a new ticket to get some feedback and hope it's acknowledge. The problem makes the access to ipv6 sites suffer from random delays, before falling back to ipv4, and so several ptlis01 users have already disabled ipv6 to solve the problem. the problem seems to be in some intermittent routing or connectivity problem in the 2001:b18:0:f:1::5 or 2001:b18:0:f:1::e routers. please check the example below, taken from 2013-03-14. I also pasted the time of day to help check for events on the logs. Example of always failing access: 14:40:51 ~/$ tracepath6 -n www.sixxs.net 1?: [LOCALHOST] 0.022ms pmtu 1492 1: 2001:b18:400f::1 1.320ms 1: 2001:b18:400f::1 1.220ms 2: 2001:b18:400f::1 1.206ms pmtu 1280 2: 2001:b18:2000:22::1 13.874ms 3: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 14.964ms asymm 2 4: 2001:b18:0:1000::1 15.187ms asymm 3 5: 2001:b18:0:f:1::5 19.926ms asymm 4 6: no reply 7: no reply 8: no reply 9: no reply ^C higuita@paquete:130 14:41:15 ~/$ ping6 -n www.sixxs.net PING www.sixxs.net(2001:838:2:1:2a0:24ff:feab:3b53) 56 data bytes ^C --- www.sixxs.net ping statistics --- 7 packets transmitted, 0 received, 100% packet loss, time 6007ms Example of intermittent connectivity: $ host www.google.pt www.google.pt has address 173.194.41.215 www.google.pt has address 173.194.41.216 www.google.pt has address 173.194.41.223 www.google.pt has IPv6 address 2a00:1450:4004:803::1018 One ping per minute, we can see ranges without connectivity $ while true; do date ; ping -c 60 -i 60 2a00:1450:4004:803::1018 ; done Qui Mar 14 12:17:04 WET 2013 PING 2a00:1450:4004:803::1018(2a00:1450:4004:803::1018) 56 data bytes 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=1 ttl=55 time=35.9 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=2 ttl=55 time=39.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=3 ttl=55 time=38.4 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=4 ttl=55 time=37.9 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=5 ttl=55 time=38.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=6 ttl=55 time=37.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=7 ttl=55 time=38.9 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=8 ttl=55 time=35.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=9 ttl=55 time=39.6 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=10 ttl=55 time=36.3 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=11 ttl=55 time=36.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=12 ttl=55 time=36.7 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=16 ttl=55 time=36.6 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=17 ttl=55 time=37.6 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=49 ttl=55 time=43.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=50 ttl=55 time=38.8 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=51 ttl=55 time=36.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=52 ttl=55 time=37.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=53 ttl=55 time=38.2 ms --- 2a00:1450:4004:803::1018 ping statistics --- 60 packets transmitted, 19 received, 68% packet loss, time 3541143ms rtt min/avg/max/mdev = 35.255/37.885/43.548/1.779 ms Qui Mar 14 13:17:05 WET 2013 PING 2a00:1450:4004:803::1018(2a00:1450:4004:803::1018) 56 data bytes 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=19 ttl=55 time=35.3 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=20 ttl=55 time=37.1 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=21 ttl=55 time=37.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=22 ttl=55 time=38.0 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=23 ttl=55 time=36.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=24 ttl=55 time=36.4 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=25 ttl=55 time=37.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=26 ttl=55 time=40.9 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=27 ttl=55 time=39.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=28 ttl=55 time=38.1 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=29 ttl=55 time=38.0 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=30 ttl=55 time=40.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=31 ttl=55 time=41.3 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=32 ttl=55 time=36.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=33 ttl=55 time=38.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=34 ttl=55 time=35.4 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=35 ttl=55 time=38.8 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=36 ttl=55 time=39.4 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=37 ttl=55 time=38.0 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=38 ttl=55 time=39.3 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=39 ttl=55 time=37.0 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=40 ttl=55 time=41.0 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=41 ttl=55 time=37.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=42 ttl=55 time=38.9 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=43 ttl=55 time=39.1 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=44 ttl=55 time=38.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=45 ttl=55 time=39.6 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=46 ttl=55 time=37.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=47 ttl=55 time=39.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=48 ttl=55 time=36.7 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=49 ttl=55 time=37.7 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=50 ttl=55 time=35.9 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=51 ttl=55 time=40.3 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=52 ttl=55 time=38.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=53 ttl=55 time=37.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=54 ttl=55 time=38.4 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=55 ttl=55 time=37.4 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=56 ttl=55 time=38.5 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=57 ttl=55 time=36.1 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=58 ttl=55 time=36.2 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=59 ttl=55 time=40.4 ms 64 bytes from 2a00:1450:4004:803::1018: icmp_seq=60 ttl=55 time=36.7 ms --- 2a00:1450:4004:803::1018 ping statistics --- 60 packets transmitted, 42 received, 30% packet loss, time 3542336ms rtt min/avg/max/mdev = 35.342/38.125/41.385/1.551 ms Qui Mar 14 14:17:08 WET 2013 I manage to grab a traceroute6 before and after failling: 14:41:22 ~/$ while true; do tracepath6 -n www.google.pt ; sleep 60 ; done 1?: [LOCALHOST] 0.082ms pmtu 1492 1: 2001:b18:400f::1 1.185ms 1: 2001:b18:400f::1 1.408ms 2: 2001:b18:400f::1 1.251ms pmtu 1280 2: 2001:b18:2000:22::1 13.217ms 3: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 12.211ms asymm 2 4: 2001:b18:0:1000::1 14.689ms asymm 3 5: 2001:b18:0:f:1::5 25.125ms asymm 4 6: 2001:b18:0:f:1::e 42.122ms asymm 5 7: 2001:7f8:f::23 31.147ms !A Resume: pmtu 1280 1?: [LOCALHOST] 0.086ms pmtu 1492 1: 2001:b18:400f::1 1.226ms 1: 2001:b18:400f::1 1.225ms 2: 2001:b18:400f::1 1.202ms pmtu 1280 2: 2001:b18:2000:22::1 14.520ms 3: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 12.416ms asymm 2 4: 2001:b18:0:1000::1 16.294ms asymm 3 5: 2001:b18:0:f:1::5 16.829ms asymm 4 6: no reply 7: no reply 8: no reply 9: no reply 10: no reply 11: no reply 12: no reply 13: no reply 14: no reply 15: no reply 16: no reply 17: no reply 18: no reply 19: no reply 20: no reply Reverse traceroute from https://mebsd.com/ipv6-ping-and-traceroute to my ip (caravela.motaleite.net) $ traceroute6 -a -q 3 -w 3 -m 30 2001:b18:400f:0:461e:a1ff:fe3b:775b 1 [AS8468] 2001:4d48:1337:5afe::1 0.399 ms 0.380 ms 0.211 ms 2 * * * 3 * * * 4 * * 5 [AS6453] 2001:5a0:c00:100::3e 7.881 ms 4.455 ms 4.425 ms 6 [AS6453] ix-0-1-0.512.mcore3.LDN-London.ipv6.as6453.net 10.198 ms 62.528 ms 127.508 ms 7 [AS6453] 2001:5a0:c00:100::9e 5.361 ms 5.383 ms 5.515 ms 8 [AS2914] ae-4.r23.londen03.uk.bb.gin.ntt.net 5.047 ms 5.677 ms 5.828 ms 9 [AS2914] ae-6.r01.mdrdsp03.es.bb.gin.ntt.net 33.594 ms 35.793 ms 35.791 ms 10 [AS2914] 2001:728:0:5000::283 31.568 ms 10 [AS2914] 2001:728:0:5000::283 31.568 ms * * 11 * * * 12 * * * 13 * * * Other online traceroutes also show 2001:728:0:5000::283 as the last hop thanks in advance for the help Higuita

Routing problem through ptlis01

Carmen Sandiego on Saturday, 16 March 2013 12:46:19

There seems no routing outside the subnet 2001:b18:0:* (ptlis01)

# ping6 www.sixxs.org PING www.sixxs.org(gatey.sixxs.net) 56 data bytes --- www.sixxs.org ping statistics --- 15 packets transmitted, 0 received, 100% packet loss, time 13999ms

# tracepath6 www.sixxs.org 1?: [LOCALHOST] 0.053ms pmtu 1500 1: ipv6-router 2.276ms 1: ipv6-router 1.491ms 2: ipv6-router 1.415ms pmtu 1280 2: ipv6-tunel-remoto 110.140ms 3: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 104.664ms asymm 2 4: 2001:b18:0:1000::1 107.304ms asymm 3 5: 2001:b18:0:f:1::5 105.525ms asymm 4 6: no reply 7: no reply 8: no reply

mercurio:~ # tracepath6 -n www.sixxs.org 1?: [LOCALHOST] 0.053ms pmtu 1280 1: 2001:b18:2000:81f1::1 2.213ms 1: 2001:b18:2000:81f1::1 1.415ms 2: 2001:b18:2000:1f1::1 104.547ms 3: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 104.973ms asymm 2 4: 2001:b18:0:1000::1 105.750ms asymm 3 5: 2001:b18:0:f:1::5 109.616ms asymm 4 6: no reply 7: no reply 8: no reply 9: no reply

# tracepath6 www.google.com 1?: [LOCALHOST] 0.058ms pmtu 1500 1: ipv6-router 1.454ms 1: ipv6-router 1.515ms 2: ipv6-router 1.440ms pmtu 1280 2: ipv6-tunel-remoto 105.260ms 3: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 106.118ms asymm 2 4: 2001:b18:0:1000::1 107.942ms asymm 3 5: 2001:b18:0:f:1::5 106.758ms asymm 4 6: no reply 7: no reply 8: no reply 9: no reply

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 21 March 2013 07:40:37

I still have the same issue with multiple destinations so it isn't solved. tracepath6 www.google.com 1?: [LOCALHOST] 0.182ms pmtu 1472 1: gw-238.lis-01.pt.sixxs.net 43.048ms 1: gw-238.lis-01.pt.sixxs.net 42.348ms 2: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 43.295ms asymm 1 3: 2001:b18:0:1000::1 44.692ms asymm 2 4: 2001:b18:0:f:1::5 43.858ms asymm 3 5: no reply 6: no reply 7: no reply 8: no reply 9: no reply 10: no reply 11: no reply

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 21 March 2013 13:09:54

Hi Javier, I have the same problem. -------------------------------------------- debian:/# traceroute6 ipv6.google.com traceroute to ipv6.google.com (2a00:1450:4007:804::1010), 30 hops max, 80 byte packets 1 gw-501.lis-01.pt.sixxs.net (2001:b18:2000:1f4::1) 68.088 ms 68.833 ms 70.872 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 71.354 ms 73.842 ms 74.842 ms 3 2001:b18:0:1000::1 (2001:b18:0:1000::1) 76.818 ms 78.303 ms 79.784 ms 4 2001:b18:0:f:1::5 (2001:b18:0:f:1::5) 81.273 ms 82.779 ms 83.746 ms 5 * * * 6 * * * -------------------------------------------- debian:/# traceroute6 www.google.pt traceroute to www.google.pt (2a00:1450:4007:803::101f), 30 hops max, 80 byte packets 1 gw-501.lis-01.pt.sixxs.net (2001:b18:2000:1f4::1) 68.319 ms 68.683 ms 70.676 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 72.219 ms 74.091 ms 74.557 ms 3 2001:b18:0:1000::1 (2001:b18:0:1000::1) 77.063 ms 80.736 ms 81.981 ms 4 2001:b18:0:f:1::5 (2001:b18:0:f:1::5) 86.920 ms 87.191 ms 87.838 ms 5 * * * 6 * * * -------------------------------------------- If I reboot the tunnel, It works some time. Regards, Juan Garca

Connections beyond PoP get dropped

Shadow Hawkins on Monday, 08 April 2013 17:12:06

I have read and followed the "Reporting Problems" section on the Contact page. I am removing these pre-filled lines to demonstrate that I really read it. I am providing the full details as requested on the mentioned Contact page. If I do not remove this, then please ignore this message as I didn't read it anyway.
A few days ago I started using the T120294 tunnel and the R217942 subnet on SixXS using the NIC handle WVR1-SIXXS. When it works, it work really well. The problem is that the tunnel PoP doesn't always seem to work properly. The way I test my IPv6 connectivity is by using ping6 on known IPv6 hosts. Pinging my tunnel endpoint always works: $ ping6 -c 2 2001:b18:2000:20e::2 PING 2001:b18:2000:20e::2(2001:b18:2000:20e::2) 56 data bytes 64 bytes from 2001:b18:2000:20e::2: icmp_seq=1 ttl=64 time=0.066 ms 64 bytes from 2001:b18:2000:20e::2: icmp_seq=2 ttl=64 time=0.087 ms --- 2001:b18:2000:20e::2 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.066/0.076/0.087/0.013 ms Pinging the tunnel gateway also works: $ ping6 -c 2 2001:b18:2000:20e::1 PING 2001:b18:2000:20e::1(2001:b18:2000:20e::1) 56 data bytes 64 bytes from 2001:b18:2000:20e::1: icmp_seq=1 ttl=64 time=103 ms 64 bytes from 2001:b18:2000:20e::1: icmp_seq=2 ttl=64 time=100 ms --- 2001:b18:2000:20e::1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 100.333/101.738/103.143/1.405 ms as does traceroute6: $ traceroute6 2001:b18:2000:20e::1 traceroute to 2001:b18:2000:20e::1 (2001:b18:2000:20e::1), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 102.445 ms 105.283 ms 106.488 ms However, when I try to reach something beyond the PoP, the connection seems to be dropped: $ ping6 -c2 ipv6.google.com PING ipv6.google.com(muc03s02-in-x14.1e100.net) 56 data bytes --- ipv6.google.com ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms $ traceroute6 ipv6.google.com traceroute to ipv6.google.com (2a00:1450:4016:801::1014), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 99.686 ms 102.223 ms 105.206 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 106.579 ms 109.338 ms 110.460 ms 3 2001:b18:0:1000::1 (2001:b18:0:1000::1) 113.658 ms 115.352 ms 117.499 ms 4 2001:b18:0:f:1::5 (2001:b18:0:f:1::5) 119.700 ms 121.904 ms 124.102 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * At first I thought the failing connections were due to a failing tunnel. Therefore I restarted AICCU a few times. Sometimes this seemed to help but often it doesn't. As per your "Reporting problems" section in the FAQ, I send you the answers to the list of questions: Output "aiccu test": # aiccu test # i.e. nothing is printed on the console. I am on Debian Wheezy $ uname -a Linux quasar 3.2.0-4-amd64 #1 SMP Debian 3.2.39-2 x86_64 GNU/Linux and I am using the latest version of the Debian aiccu package: # dpkg -l \*aiccu\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=====================================================-===============================-===============================-========================================================================================= ====================== ii aiccu 20070115-15.1 amd64 SixXS Automatic IPv6 Connectivity Client Utility The machine I am uisng the tunnel on is an ordinary AMD64 PC behind a ASL-26555 ADSL modem. The modem is configured to be the IPv4 gateway and the PC is setup to be the IPv6 gateway. Here is an output of "ip addr show" $ ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1b:b9:cd:fb:55 brd ff:ff:ff:ff:ff:ff inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0 inet6 2001:b18:2000:820e::3/64 scope global valid_lft forever preferred_lft forever inet6 fe80::21b:b9ff:fecd:fb55/64 scope link valid_lft forever preferred_lft forever 3: sit0: <NOARP> mtu 1480 qdisc noop state DOWN link/sit 0.0.0.0 brd 0.0.0.0 12: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc pfifo_fast state UNKNOWN qlen 500 link/none inet6 2001:b18:2000:20e::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::818:2000:20e:2/64 scope link valid_lft forever preferred_lft forever and here of "ip -6 route show" $ ip -6 route show 2001:b18:2000:20e::/64 dev sixxs proto kernel metric 256 2001:b18:2000:820e::/64 dev eth0 proto kernel metric 256 fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev sixxs proto kernel metric 256 default via 2001:b18:2000:20e::1 dev sixxs metric 1024 Here a complete list of all iptables rules on the PC $ sudo iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination $ sudo iptables -L -n -t nat Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination target prot opt source destination MASQUERADE !41 -- 0.0.0.0/0 0.0.0.0/0 $ sudo iptables -L -n -t raw Chain PREROUTING (policy ACCEPT) target prot opt source destination NOTRACK 41 -- 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT) target prot opt source destination Is there any way you can help me with this? Many thanks in advance.

Connections beyond PoP get dropped

Shadow Hawkins on Monday, 08 April 2013 23:09:36

Hello I'm experiencing the same problem as reported above for the last few days. I think here a similar problem was reported, but it is already marked as resolved. Following I provide the results of aiccu autotest and a tracepath6 to noc.sixxs.net performed when the connection is failling, and a tracepath when the connection is running. I flushed all iptables rules just in case. The tracepath results when the connection is failling are allways the same showing the connection is droped always after 2001:b18:0:f:1::5. If you need more input I will be glad to help. aiccu autotest:

Tunnel Information for T119706: POP Id : ptlis01 IPv6 Local : 2001:b18:2000:20d::2/64 IPv6 Remote : 2001:b18:2000:20d::1/64 Tunnel Type : ayiya Adminstate : enabled Userstate : enabled ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.128) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 192.168.1.128 (192.168.1.128) 56(84) bytes of data. 64 bytes from 192.168.1.128: icmp_req=1 ttl=64 time=0.184 ms 64 bytes from 192.168.1.128: icmp_req=2 ttl=64 time=0.152 ms 64 bytes from 192.168.1.128: icmp_req=3 ttl=64 time=0.148 ms --- 192.168.1.128 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.148/0.161/0.184/0.019 ms ###### ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (82.102.0.131) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur PING 82.102.0.131 (82.102.0.131) 56(84) bytes of data. 64 bytes from 82.102.0.131: icmp_req=1 ttl=56 time=19.0 ms 64 bytes from 82.102.0.131: icmp_req=2 ttl=56 time=18.8 ms 64 bytes from 82.102.0.131: icmp_req=3 ttl=56 time=21.8 ms --- 82.102.0.131 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 18.871/19.925/21.855/1.371 ms ###### ####### [3/8] Traceroute to the PoP (82.102.0.131) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem traceroute to 82.102.0.131 (82.102.0.131), 30 hops max, 60 byte packets 1 zeus.lan (192.168.1.254) 94.385 ms 93.552 ms 92.915 ms 2 * * * 3 bl3-73-17.dsl.telepac.pt (213.13.73.17) 24.255 ms 25.598 ms 25.446 ms 4 gi11-0-0.lgsr1.telepac.net (194.65.12.90) 33.685 ms 35.366 ms 38.390 ms 5 te1-1.lcat1.telepac.net (213.13.135.174) 34.905 ms 37.996 ms 37.736 ms 6 94.46.208.1 (94.46.208.1) 40.322 ms 22.402 ms 25.163 ms 7 81.92.223.125 (81.92.223.125) 22.187 ms 20.373 ms 33.098 ms 8 81.92.223.102 (81.92.223.102) 23.399 ms 23.162 ms 23.983 ms 9 ptlis01.sixxs.net (82.102.0.131) 27.842 ms 25.614 ms 22.311 ms ###### ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.180 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.177 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.176 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.176/0.177/0.180/0.015 ms ###### ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2001:b18:2000:20d::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2001:b18:2000:20d::2(2001:b18:2000:20d::2) 56 data bytes 64 bytes from 2001:b18:2000:20d::2: icmp_seq=1 ttl=64 time=0.189 ms 64 bytes from 2001:b18:2000:20d::2: icmp_seq=2 ttl=64 time=0.175 ms 64 bytes from 2001:b18:2000:20d::2: icmp_seq=3 ttl=64 time=0.184 ms --- 2001:b18:2000:20d::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.175/0.182/0.189/0.016 ms ###### ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:b18:2000:20d::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was successful then this could be both ### a firewalling and a routing/interface problem PING 2001:b18:2000:20d::1(2001:b18:2000:20d::1) 56 data bytes 64 bytes from 2001:b18:2000:20d::1: icmp_seq=1 ttl=64 time=19.4 ms 64 bytes from 2001:b18:2000:20d::1: icmp_seq=2 ttl=64 time=20.5 ms 64 bytes from 2001:b18:2000:20d::1: icmp_seq=3 ttl=64 time=21.2 ms --- 2001:b18:2000:20d::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 19.438/20.408/21.203/0.749 ms ###### ###### [7/8] Traceroute6 to the central SixXS machine (noc.sixxs.net) ### This confirms that you can reach the central machine of SixXS ### If that one is reachable you should be able to reach most IPv6 destinations ### Also check http://www.sixxs.net/ipv6calc/ which should show an IPv6 connection ### If your browser supports IPv6 and uses it of course. traceroute to noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c), 30 hops max, 80 byte packets 1 * gw-526.lis-01.pt.sixxs.net (2001:b18:2000:20d::1) 22.095 ms 21.920 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 24.911 ms 24.498 ms 25.612 ms 3 2001:b18:0:1000::1 (2001:b18:0:1000::1) 26.713 ms 27.435 ms 28.778 ms 4 2001:b18:0:f:1::5 (2001:b18:0:f:1::5) 30.739 ms 31.350 ms 32.230 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### ###### [8/8] Traceroute6 to (www.kame.net) ### This confirms that you can reach a Japanese IPv6 destination ### If that one is reachable you should be able to reach most IPv6 destinations ### You should also check http://www.kame.net which should display ### a animated kame (turtle), of course only when your browser supports and uses IPv6 traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 gw-526.lis-01.pt.sixxs.net (2001:b18:2000:20d::1) 19.423 ms 20.481 ms 22.416 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 22.360 ms 24.826 ms 24.744 ms 3 2001:b18:0:1000::1 (2001:b18:0:1000::1) 26.432 ms 27.595 ms 28.906 ms 4 2001:b18:0:f:1::5 (2001:b18:0:f:1::5) 36.157 ms 36.061 ms 35.959 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * ###### ###### ACCU Quick Connectivity Test (done)

Failed tracepath to noc.sixxs.net:

1?: [LOCALHOST] 0.123ms pmtu 1280 1: gw-526.lis-01.pt.sixxs.net 33.308ms 1: gw-526.lis-01.pt.sixxs.net 33.146ms 2: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 31.814ms asymm 1 3: 2001:b18:0:1000::1 34.468ms asymm 2 4: 2001:b18:0:f:1::5 45.325ms asymm 3 5: no reply 6: no reply 7: no reply 8: no reply 9: no reply 10: no reply 11: no reply 12: no reply 13: no reply 14: no reply 15: no reply 16: no reply 17: no reply 18: no reply 19: no reply 20: no reply 21: no reply 22: no reply 23: no reply 24: no reply 25: no reply 26: no reply 27: no reply 28: no reply 29: no reply 30: no reply 31: no reply Too many hops: pmtu 1280 Resume: pmtu 1280

Successful tracepath to noc.sixxs.net:

1?: [LOCALHOST] 0.478ms pmtu 1280 1: gw-526.lis-01.pt.sixxs.net 34.636ms 1: gw-526.lis-01.pt.sixxs.net 34.686ms 2: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 33.814ms asymm 1 3: 2001:b18:0:1000::1 35.096ms asymm 2 4: 2001:b18:0:f:1::5 43.635ms asymm 3 5: 2001:b18:0:f:1::e 49.271ms asymm 4 6: xe-0-1-0-5.r01.mdrdsp03.es.bb.gin.ntt.net 49.287ms 7: ae-2.r01.mdrdsp04.es.bb.gin.ntt.net 50.852ms 8: ae-1.r02.mdrdsp04.es.bb.gin.ntt.net 50.838ms 9: ae-5.r23.amstnl02.nl.bb.gin.ntt.net 87.779ms 10: as-0.r22.amstnl02.nl.bb.gin.ntt.net 84.790ms asymm 9 11: ams-ix.ipv6.concepts.nl 215.398ms asymm 8 12: 2001:838:5:a::2 89.760ms asymm 9 13: noc.sixxs.net 86.792ms reached Resume: pmtu 1280 hops 13 back 54

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Tuesday, 09 April 2013 08:06:16

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Tuesday, 09 April 2013 18:40:29

And again no connection beyond the PoP: $ date; ping6 -c 2 2001:b18:2000:20e::2; ping6 -c 2 2001:b18:2000:20e::1; ping6 -c2 www.kame.net Tue Apr 9 20:39:24 CEST 2013 PING 2001:b18:2000:20e::2(2001:b18:2000:20e::2) 56 data bytes 64 bytes from 2001:b18:2000:20e::2: icmp_seq=1 ttl=64 time=0.094 ms 64 bytes from 2001:b18:2000:20e::2: icmp_seq=2 ttl=64 time=0.107 ms --- 2001:b18:2000:20e::2 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.094/0.100/0.107/0.011 ms PING 2001:b18:2000:20e::1(2001:b18:2000:20e::1) 56 data bytes 64 bytes from 2001:b18:2000:20e::1: icmp_seq=1 ttl=64 time=100 ms 64 bytes from 2001:b18:2000:20e::1: icmp_seq=2 ttl=64 time=99.9 ms --- 2001:b18:2000:20e::1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 99.928/100.040/100.153/0.335 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Wednesday, 10 April 2013 09:52:00

For the sake of statistics, this morning I experienced no connections beyond the PoP several times. Here are ping6 and traceroute6 data: $ date; ping6 -c 2 2001:b18:2000:20e::2; ping6 -c 2 2001:b18:2000:20e::1; ping6 -c2 www.kame.net Wed Apr 10 11:49:19 CEST 2013 PING 2001:b18:2000:20e::2(2001:b18:2000:20e::2) 56 data bytes 64 bytes from 2001:b18:2000:20e::2: icmp_seq=1 ttl=64 time=0.148 ms 64 bytes from 2001:b18:2000:20e::2: icmp_seq=2 ttl=64 time=0.147 ms --- 2001:b18:2000:20e::2 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.147/0.147/0.148/0.012 ms PING 2001:b18:2000:20e::1(2001:b18:2000:20e::1) 56 data bytes 64 bytes from 2001:b18:2000:20e::1: icmp_seq=1 ttl=64 time=99.4 ms 64 bytes from 2001:b18:2000:20e::1: icmp_seq=2 ttl=64 time=97.1 ms --- 2001:b18:2000:20e::1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 97.173/98.317/99.461/1.144 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1008ms $ date; traceroute6 -n 2001:b18:2000:20e::2; traceroute6 -n 2001:b18:2000:20e::1; traceroute6 -n www.kame.net Wed Apr 10 11:49:49 CEST 2013 traceroute to 2001:b18:2000:20e::2 (2001:b18:2000:20e::2), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::2 0.134 ms 0.029 ms 0.029 ms traceroute to 2001:b18:2000:20e::1 (2001:b18:2000:20e::1), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 102.238 ms 103.600 ms 106.087 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 99.352 ms 100.811 ms 103.548 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 105.178 ms 108.133 ms 109.240 ms 3 2001:b18:0:1000::1 112.325 ms 115.393 ms 117.064 ms 4 2001:b18:0:f:1::5 129.245 ms 129.325 ms 130.832 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Wednesday, 10 April 2013 20:07:29

I can confirm the problem is not solved yet. I'm having only short periods of connectivity. But I'm wondering whether this affects everyone since I'm only seeing two users reporting issues. Can this be somehow a user side problem?

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 11 April 2013 07:37:05

Interesting remark. Maybe we are the only two seeing this problem. But maybe we are the only two bothering with reporting this. I really don't know. I wonder, however, how this can be a user side problem. As far as I can tell we both can always reach the PoP but sometimes cannot go beyond it. One way to test if this is a user problem is to use a different PoP and see if the problem also happens there. But since I am in Spain, I could only choose one PoP...

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Tuesday, 16 April 2013 15:14:51

I can only use ptlis01 also. I think there is not really a lot we can do. We have to wait for the admins to check it. I have been running a script that checks connectivity with google every five minutes, but this is completely random, so I cannot add any more useful information.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 April 2013 11:56:34

Hi Everything i wrote above, on 14 March 2013 18:59:18 is still happening. i and several contacts i have that use sixxs report this problem, intermittent ipv6 access via this POP. The ticket is marked resolved and i didnt manage to change it status, even posting a new ticket (the 14 March 2013 one, it got moved to here) I assume that that this is a known problem, but hard to solve, as trying to contact NFSI also got no response. I have no ideal why the state of of this ticket isnt switched to open or something else, keeping it as "resolved" only asks for more users to keep reporting the same problem. As far as i can see, this is not a user problem, its a problem in the outer NFSI router, with the ips 2001:b18:0:f:1::e and 2001:b18:0:f:1::d or in the NFSI backbone router, the adm-ipv6-link.telia.net with the ips 2001:2000:3080:19::1 and 2001:2000:3080:19::3. As its the jump between the nfsi and telia that is intermitent, they both should be in contact to solve this... i hope... Sadly this problem is already months old and without any feedback, making it extra anoying...

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 April 2013 12:31:14

Why did you think the problem is with the NFSI/Telia connection? As far as I can see comparing the fail/successful traceroutes, the problem is in the hop between 2001:b18:0:f:1::5 and 2001:b18:0:f:1::e as the latter usually stops pinging when the connectivity is lost. Both are property of NFSI so the problem should be within NFSI only. Can you explain your idea? Thanks

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 April 2013 13:38:14

I really think its the 2001:b18:0:f:1::e that have some problem, but as once i manage to do some traceroute that could reach 2001:b18:0:f:1::e, but not 2001:2000:3080:19::1, i added to the possible list of problems the connection problem... but in the past month, my logs show that it only fails in the 2001:b18:0:f:1::e, so maybe we can discard that traceroute as another problem/plain luck. Right now is failing again and this is the status:

tracepath6 www.google.pt -n 1?: [LOCALHOST] 0.077ms pmtu 1492 1: 2001:b18:400f::1 1.507ms 1: 2001:b18:400f::1 1.302ms 2: 2001:b18:400f::1 1.222ms pmtu 1280 2: 2001:b18:2000:22::1 14.944ms 3: 2001:b18:0:1000:2e0:81ff:fe61:ae0d 12.307ms asymm 2 4: 2001:b18:0:1000::1 14.733ms asymm 3 5: 2001:b18:0:f:1::5 18.858ms asymm 4 6: no reply 7: no reply

Trying from outside (https://mebsd.com/ipv6-ping-and-traceroute) to my server , i get:

traceroute6 -a -q 3 -w 3 -m 30 paquete.motaleite.net 1 [AS8468] 2001:4d48:1337:5afe::1 0.398 ms 0.381 ms 0.217 ms 2 * * * 3 * * * 4 * * 5 [AS6453] 2001:5a0:c00:100::3e 4.471 ms 4.434 ms 4.424 ms 6 [AS6453] ix-0-1-0.512.mcore3.LDN-London.ipv6.as6453.net 5.047 ms 5.226 ms 4.892 ms 7 [AS6453] if-0-0-0.core4.LDN-London.ipv6.as6453.net 5.047 ms 4.907 ms 4.743 ms 8 [AS1299] ldn-b5-link.telia.net 5.830 ms 5.679 ms 5.047 ms 9 [AS1299] mad-b2-v6.telia.net 40.937 ms 10 [AS1299] 2001:2000:3080:19::3 46.700 ms 39.217 ms 40.774 ms 11 * * *

So yes, its the 2001:b18:0:f:1::e/2001:b18:0:f:1::d that is failing I tried to send another email to nfsi, so maybe the status changed is related to this email. either way is good to see any acknowledge in this ticket :)

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 April 2013 12:33:42

BTW, I think we're lucky as the ticket status changed to confirmed. Hope they are able to solve this.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Monday, 15 April 2013 15:20:14

Adding for statistical purposes again. I can do this several times a day. Is there anything anyone can do about this please? $ date; ping6 -c 2 2001:b18:2000:20e::2; ping6 -c 2 2001:b18:2000:20e::1; ping6 -c2 www.kame.net; traceroute6 -n 2001:b18:2000:20e::2; traceroute6 -n 2001:b18:2000:20e::1; traceroute6 -n www.kame.net Mon Apr 15 17:18:13 CEST 2013 PING 2001:b18:2000:20e::2(2001:b18:2000:20e::2) 56 data bytes 64 bytes from 2001:b18:2000:20e::2: icmp_seq=1 ttl=64 time=0.144 ms 64 bytes from 2001:b18:2000:20e::2: icmp_seq=2 ttl=64 time=0.192 ms --- 2001:b18:2000:20e::2 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.144/0.168/0.192/0.024 ms PING 2001:b18:2000:20e::1(2001:b18:2000:20e::1) 56 data bytes 64 bytes from 2001:b18:2000:20e::1: icmp_seq=1 ttl=64 time=102 ms 64 bytes from 2001:b18:2000:20e::1: icmp_seq=2 ttl=64 time=100 ms --- 2001:b18:2000:20e::1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 100.459/101.503/102.547/1.044 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms traceroute to 2001:b18:2000:20e::2 (2001:b18:2000:20e::2), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::2 0.159 ms 0.034 ms 0.031 ms traceroute to 2001:b18:2000:20e::1 (2001:b18:2000:20e::1), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 101.709 ms 103.987 ms 105.433 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 104.648 ms 104.452 ms 106.358 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 107.573 ms 110.645 ms 111.891 ms 3 2001:b18:0:1000::1 115.070 ms 117.018 ms 118.866 ms 4 2001:b18:0:f:1::5 121.134 ms 123.235 ms 125.394 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Wednesday, 17 April 2013 08:35:15

More statistics. Yesterday the connection was a lot better, but today it's back to bad again. $ date; ping6 -c 2 2001:b18:2000:20e::2; ping6 -c 2 2001:b18:2000:20e::1; ping6 -c2 www.kame.net; traceroute6 -n 2001:b18:2000:20e::2; traceroute6 -n 2001:b18:2000:20e::1; traceroute6 -n www.kame.net Wed Apr 17 10:33:59 CEST 2013 PING 2001:b18:2000:20e::2(2001:b18:2000:20e::2) 56 data bytes 64 bytes from 2001:b18:2000:20e::2: icmp_seq=1 ttl=64 time=0.116 ms 64 bytes from 2001:b18:2000:20e::2: icmp_seq=2 ttl=64 time=0.155 ms --- 2001:b18:2000:20e::2 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.116/0.135/0.155/0.022 ms PING 2001:b18:2000:20e::1(2001:b18:2000:20e::1) 56 data bytes 64 bytes from 2001:b18:2000:20e::1: icmp_seq=1 ttl=64 time=100 ms 64 bytes from 2001:b18:2000:20e::1: icmp_seq=2 ttl=64 time=99.8 ms --- 2001:b18:2000:20e::1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 99.884/100.205/100.526/0.321 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms traceroute to 2001:b18:2000:20e::2 (2001:b18:2000:20e::2), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::2 0.169 ms 0.033 ms 0.028 ms traceroute to 2001:b18:2000:20e::1 (2001:b18:2000:20e::1), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 99.198 ms 101.876 ms 102.791 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 99.436 ms 100.920 ms 103.983 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 105.822 ms 108.490 ms 109.771 ms 3 2001:b18:0:1000::1 112.610 ms 114.956 ms 116.713 ms 4 2001:b18:0:f:1::5 121.199 ms 121.189 ms 124.116 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 April 2013 06:50:05

Since there still is no resolution to this ticket, despite frequent reporting of problems, I will increase my reporting efforts. At this moment again there is no connection beyond the PoP. $ date; ping6 -c2 www.kame.net; traceroute6 -n www.kame.net Thu Apr 18 08:49:08 CEST 2013 PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 101.811 ms 103.736 ms 105.043 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 108.243 ms 109.663 ms 112.257 ms 3 2001:b18:0:1000::1 114.747 ms 116.920 ms 119.093 ms 4 2001:b18:0:f:1::5 120.776 ms 122.980 ms 125.736 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 April 2013 12:37:07

Again no connection beyond the PoP: $ date; ping6 -c2 www.kame.net; traceroute6 -n www.kame.net Thu Apr 18 14:35:53 CEST 2013 PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 102.122 ms 105.094 ms 106.229 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 109.773 ms 111.992 ms 113.012 ms 3 2001:b18:0:1000::1 115.928 ms 117.796 ms 120.300 ms 4 2001:b18:0:f:1::5 122.814 ms 124.677 ms 126.387 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 April 2013 13:32:34

And again: $ date; ping6 -c2 www.kame.net; traceroute6 -n www.kame.net Thu Apr 18 15:29:29 CEST 2013 PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 103.785 ms 104.457 ms 107.553 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 108.857 ms 111.221 ms 112.609 ms 3 2001:b18:0:1000::1 116.126 ms 117.845 ms 119.928 ms 4 2001:b18:0:f:1::5 122.086 ms 123.951 ms 126.021 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 April 2013 14:15:59

The connection briefly worked and now is gone again. $ date; ping6 -c2 www.kame.net; traceroute6 -n www.kame.net Thu Apr 18 16:14:14 CEST 2013 PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1008ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 103.077 ms 105.187 ms 106.639 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 109.351 ms 111.058 ms 113.987 ms 3 2001:b18:0:1000::1 115.827 ms 117.965 ms 120.214 ms 4 2001:b18:0:f:1::5 122.436 ms 124.302 ms 126.534 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 07:06:17

There was no connection at the time of this next measurement, but a few minutes later it was back up. Still, for statistical reasons: $ date; ping6 -c2 www.kame.net; traceroute6 -n www.kame.net Fri Apr 19 08:59:07 CEST 2013 PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 103.377 ms 104.793 ms 107.348 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 108.633 ms 111.507 ms 112.893 ms 3 2001:b18:0:1000::1 117.073 ms 117.963 ms 120.005 ms 4 2001:b18:0:f:1::5 132.418 ms 132.476 ms 133.488 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 07:32:03

Connection is down again. $ date; ping6 -c2 www.kame.net; traceroute6 -n www.kame.net Fri Apr 19 09:31:01 CEST 2013 PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 103.527 ms 105.259 ms 107.846 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 109.282 ms 111.177 ms 112.935 ms 3 2001:b18:0:1000::1 115.998 ms 118.160 ms 120.008 ms 4 2001:b18:0:f:1::5 122.386 ms 124.402 ms 126.089 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 07:49:28

At the moment it is back up again.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 09:57:43

It's down again. $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net Fri Apr 19 11:54:27 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=100 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=102 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 100.655/101.393/102.132/0.804 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1008ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 99.537 ms 102.369 ms 103.836 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 107.148 ms 108.547 ms 110.928 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 102.374 ms 104.797 ms 106.419 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 108.490 ms 111.223 ms 113.413 ms 3 2001:b18:0:1000::1 115.052 ms 118.415 ms 119.918 ms 4 2001:b18:0:f:1::5 122.202 ms 124.152 ms 125.882 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 10:21:47

And it's back up.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 13:06:53

The connection was working for a while but it's down again. $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net Fri Apr 19 15:05:10 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=108 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=106 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 106.543/107.715/108.887/1.172 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 107.982 ms 110.139 ms 112.713 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 113.975 ms 116.901 ms 117.792 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 109.786 ms 112.239 ms 113.835 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 116.439 ms 118.016 ms 120.635 ms 3 2001:b18:0:1000::1 122.774 ms 124.918 ms 126.811 ms 4 2001:b18:0:f:1::5 140.049 ms 140.241 ms 140.396 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 13:54:43

And now it's back up again. Been checking a few times in between and this is the first time ping6 is returning a reply since the connection beyond the PoP went down.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 14:30:57

And down again. $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net Fri Apr 19 16:25:33 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=100 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=100 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 100.266/100.519/100.772/0.253 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1006ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 103.030 ms 104.775 ms 107.281 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 108.829 ms 112.084 ms 112.686 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 102.936 ms 104.428 ms 107.087 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 108.539 ms 111.424 ms 112.775 ms 3 2001:b18:0:1000::1 115.480 ms 117.580 ms 119.513 ms 4 2001:b18:0:f:1::5 130.178 ms 131.469 ms 131.545 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 14:34:03

And back up again.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 16:37:23

And down. $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net Fri Apr 19 18:36:13 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=100 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=101 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 100.944/101.104/101.265/0.356 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1008ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 99.548 ms 102.273 ms 104.174 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 109.692 ms 109.691 ms 110.518 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 103.200 ms 104.674 ms 106.870 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 108.061 ms 110.948 ms 112.433 ms 3 2001:b18:0:1000::1 115.543 ms 117.451 ms 119.673 ms 4 2001:b18:0:f:1::5 122.077 ms 123.715 ms 125.873 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 19 April 2013 18:12:25

And it's up again.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Sunday, 21 April 2013 22:15:48

I'm not sure it's already perfect. It is completely usable, but it fails from time to time. I will test this better in the next couple of days. Anyway, thanks very much for SixXs and NFSI.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Monday, 22 April 2013 07:12:13

I second this. Connectivity is much improved now, but let's monitor it for a few days to be sure that all problems have been resolved. At the moment it looks very good indeed. Big thanks to SixXS and NFSI!

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Sunday, 21 April 2013 19:50:43

Sorry, it's not resolved yet. $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net Sun Apr 21 21:49:30 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=102 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=105 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 102.673/104.160/105.648/1.522 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes 64 bytes from 2001:200:dff:fff1:216:3eff:feb1:44d7: icmp_seq=1 ttl=50 time=430 ms --- www.kame.net ping statistics --- 2 packets transmitted, 1 received, 50% packet loss, time 1000ms rtt min/avg/max/mdev = 430.995/430.995/430.995/0.000 ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 110.914 ms * * 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 116.603 ms 117.513 ms 120.619 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 111.187 ms 113.171 ms 114.350 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 117.602 ms 119.445 ms * 3 2001:b18:0:1000::1 123.780 ms * 128.219 ms 4 2001:b18:0:f:1::5 132.133 ms * * 5 2001:b18:0:f:1::e 164.070 ms * 167.039 ms 6 2001:728:0:5000::281 169.774 ms 138.792 ms * 7 * 2001:728:0:2000::76 138.137 ms * 8 2001:728:0:2000::2e 138.380 ms 138.597 ms 138.112 ms 9 * 2001:728:0:2000::79 175.408 ms 174.998 ms 10 * 2001:418:0:2000::1c5 176.177 ms 173.421 ms 11 2001:418:0:2000::16 521.747 ms 518.355 ms 420.797 ms 12 2001:218:0:6000::116 429.275 ms 421.521 ms * 13 2001:218:2000:5000::82 430.201 ms 426.030 ms 426.917 ms 14 2001:200:0:10::141 424.354 ms * * 15 * 2001:200:0:180a:a6ba:dbff:fe1d:19f4 418.391 ms * 16 2001:200:dff:fff1:216:3eff:feb1:44d7 427.759 ms 423.642 ms 426.326 ms

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Sunday, 21 April 2013 20:44:17

Seems to be ok again now.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Wednesday, 24 April 2013 07:38:50

There was a little hickup this morning but the connection was restored very quickly. $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net Wed Apr 24 09:36:32 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=101 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=101 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 101.434/101.647/101.860/0.213 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1007ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 102.832 ms 105.834 ms 107.192 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 109.864 ms 111.354 ms 114.402 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 103.749 ms 106.350 ms 107.431 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 110.286 ms 111.988 ms 114.390 ms 3 2001:b18:0:1000::1 116.743 ms 119.161 ms 121.283 ms 4 2001:b18:0:f:1::5 122.998 ms 125.018 ms 127.702 ms 5 2001:b18:0:f:1::e 145.051 ms 147.919 ms 149.026 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * *

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Friday, 26 April 2013 12:10:00

Over the past five days there was only one very small glitch in connectivity, and otherwise it has been perfect. For me it's ok to close this ticket. Thanks a lot once more SixXS and NFSi! Cheers, Wouter

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Wednesday, 01 May 2013 12:32:57

Something I forgot to mention is that from time to time the latency (as reported in my tunnel's page) is increased, from an average of less than 40ms to something like 90ms to 100ms.

ptlis01 PoP - isolated? - part2

Jeroen Massar SixXS Staff

on Wednesday, 01 May 2013 13:02:01

That latency is between your endpoint and the PoP over an IPv4 path, as such, check your IPv4 connectivity.

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 July 2013 07:07:55

In the past weeks everything has been working really well. However, this morning the connection beyond the endpoint seems to be down again: $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net; wget http://ipv6.google.com && rm index.html Thu Jul 18 09:04:03 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=127 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=124 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 124.669/126.136/127.604/1.509 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1008ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 126.165 ms 129.087 ms 130.497 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 133.167 ms 135.085 ms 137.532 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 130.369 ms 131.673 ms 134.139 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 135.564 ms 138.703 ms 140.206 ms 3 2001:b18:0:1000::1 142.845 ms 145.820 ms 146.727 ms 4 2001:b18:0:f:1::5 148.903 ms 151.074 ms 163.886 ms 5 * * * 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * --2013-07-18 09:04:41-- http://ipv6.google.com/ Resolving ipv6.google.com (ipv6.google.com)... 2a00:1450:4013:c00::68 Connecting to ipv6.google.com (ipv6.google.com)|2a00:1450:4013:c00::68|:80... failed: Connection timed out. Retrying. --2013-07-18 09:06:49-- (try: 2) http://ipv6.google.com/ Connecting to ipv6.google.com (ipv6.google.com)|2a00:1450:4013:c00::68|:80... ^C

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Thursday, 18 July 2013 11:31:29

Now everything is ok again. Cheers, Wouter

ptlis01 PoP - isolated? - part2

Shadow Hawkins on Wednesday, 14 August 2013 11:37:33

The pop had some problems again this morning. At the moment, the connection fails beyond the pop again. $ date; ping6 -c 2 ptlis01.sixxs.net; ping6 -c2 www.kame.net; traceroute6 ptlis01.sixxs.net; traceroute6 -n www.kame.net; wget http://ipv6.google.com && rm index.html Wed Aug 14 13:33:44 CEST 2013 PING ptlis01.sixxs.net(2001:b18:0:1000:2e0:81ff:fe61:ae0d) 56 data bytes 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=1 ttl=64 time=99.4 ms 64 bytes from 2001:b18:0:1000:2e0:81ff:fe61:ae0d: icmp_seq=2 ttl=64 time=105 ms --- ptlis01.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 99.488/102.454/105.420/2.966 ms PING www.kame.net(2001:200:dff:fff1:216:3eff:feb1:44d7) 56 data bytes --- www.kame.net ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 999ms traceroute to ptlis01.sixxs.net (2001:b18:0:1000:2e0:81ff:fe61:ae0d), 30 hops max, 80 byte packets 1 gw-527.lis-01.pt.sixxs.net (2001:b18:2000:20e::1) 105.138 ms 106.315 ms 109.001 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d (2001:b18:0:1000:2e0:81ff:fe61:ae0d) 110.304 ms 113.257 ms 117.435 ms traceroute to www.kame.net (2001:200:dff:fff1:216:3eff:feb1:44d7), 30 hops max, 80 byte packets 1 2001:b18:2000:20e::1 106.108 ms 107.256 ms 109.754 ms 2 2001:b18:0:1000:2e0:81ff:fe61:ae0d 111.841 ms 114.321 ms 115.680 ms 3 2001:b18:0:1000::1 118.881 ms 120.828 ms 122.365 ms 4 2001:b18:0:f:1::5 124.284 ms 125.955 ms 128.350 ms 5 2001:b18:0:f:1::e 145.336 ms 147.024 ms 149.375 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * --2013-08-14 13:34:30-- http://ipv6.google.com/ Resolving ipv6.google.com (ipv6.google.com)... 2a00:1450:4003:804::1012 Connecting to ipv6.google.com (ipv6.google.com)|2a00:1450:4003:804::1012|:80... failed: Connection timed out. Retrying. --2013-08-14 13:36:38-- (try: 2) http://ipv6.google.com/ Connecting to ipv6.google.com (ipv6.google.com)|2a00:1450:4003:804::1012|:80... ^C

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