SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1070650
Ticket Status: User

PoP: deham01 - Easynet (Hamburg)

2001:6f8:900:85a::2 is not responding
[de] Shadow Hawkins on Sunday, 26 April 2009 21:44:05
Hello, since 2009-04-21, i get every night a mail, that the host 2001:6f8:900:85a::2 is not responding of your ICMPv6 ping. But the host can be pinged - test with the join testtools, and i can ping e.g. google or sixxs. there is no firewall rule. thank you for your help Here are some informations: Handle : MRV1-SIXXS PoP Name : deham01 (de.easynet [AS4589]) Your Location: Nuernberg, de SixXS IPv6 : 2001:6f8:900:85a::1/64 Your IPv6 : 2001:6f8:900:85a::2/64 SixXS IPv4 : 212.224.0.188 Your IPv4 : 212.112.227.139 ping result from the JOIN-RZ: Result of 'ping6 -s 56 -W 10 -c 5 2001:6f8:900:85a::2 ': PING 2001:6f8:900:85a::2(2001:6f8:900:85a::2) 56 data bytes 64 bytes from 2001:6f8:900:85a::2: icmp_seq=1 ttl=52 time=49.3 ms 64 bytes from 2001:6f8:900:85a::2: icmp_seq=2 ttl=52 time=50.3 ms 64 bytes from 2001:6f8:900:85a::2: icmp_seq=3 ttl=52 time=50.9 ms 64 bytes from 2001:6f8:900:85a::2: icmp_seq=4 ttl=52 time=49.7 ms 64 bytes from 2001:6f8:900:85a::2: icmp_seq=5 ttl=52 time=50.9 ms --- 2001:6f8:900:85a::2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 49.319/50.255/50.964/0.708 ms # ping6 -c2 ipv6.google.com PING ipv6.google.com(fx-in-x68.google.com) 56 data bytes 64 bytes from fx-in-x68.google.com: icmp_seq=1 ttl=55 time=43.0 ms 64 bytes from fx-in-x68.google.com: icmp_seq=2 ttl=55 time=41.5 ms --- ipv6.google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1002ms rtt min/avg/max/mdev = 41.508/42.266/43.025/0.785 ms # ping6 -c2 noc.sixxs.net PING noc.sixxs.net(noc.sixxs.net) 56 data bytes 64 bytes from noc.sixxs.net: icmp_seq=1 ttl=52 time=43.4 ms 64 bytes from noc.sixxs.net: icmp_seq=2 ttl=52 time=43.6 ms --- noc.sixxs.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 43.401/43.530/43.659/0.129 ms # uname -a Linux zion 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686 GNU/Linux # route -n Kernel-IP-Routentabelle Ziel Router Genmask Flags Metric Ref Use Iface 212.112.227.128 0.0.0.0 255.255.255.192 U 0 0 0 eth0 0.0.0.0 212.112.227.129 0.0.0.0 UG 0 0 0 eth0 # route -6 -n Kernel-IPv6-Routentabelle Destination Next Hop Flag Met Ref Use If 2001:6f8:900:85a::/64 :: Un 256 0 5 sixxs fe80::/64 :: Un 256 0 0 sixxs ::/0 2001:6f8:900:85a::1 UG 1024 0 5 sixxs ::/0 :: !n -1 1 11 lo ::1/128 :: Un 0 1 6 lo 2001:6f8:900:85a::2/128 :: Un 0 1 9 lo fe80::d470:e38b/128 :: Un 0 1 0 lo fe80::2e0:4cff:fec4:e241/128 :: Un 0 1 0 lo ff00::/8 :: U 256 0 0 eth0 ff00::/8 :: U 256 0 0 sixxs ::/0 :: !n -1 1 11 lo
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 26 April 2009 23:02:24
Message is Locked
The state of this ticket has been changed to user
2001:6f8:900:85a::2 is not responding
[ch] Jeroen Massar SixXS Staff on Sunday, 26 April 2009 23:03:50
Look at the statistics in your tunnel page, indeed now it pings, but it seems that it did not do that before. Please read: FAQ: Tunnel endpoint didn't ping
2001:6f8:900:85a::2 is not responding
[de] Shadow Hawkins on Sunday, 26 April 2009 23:18:33
Yes, after a restart it works for 3-4 h and then boom...it stops. But this is the first time, that the stats recognize the ping. So please lets wait a few days and see what happend. Thanks :)
2001:6f8:900:85a::2 is not responding
[ch] Jeroen Massar SixXS Staff on Monday, 27 April 2009 08:50:31

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

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