SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1066204
Ticket Status: User

PoP: deham01 - Easynet (Hamburg)

deham01 seems to be down
[de] Shadow Hawkins SixXS Oper on Monday, 20 April 2009 15:58:39
There seems to be an issue with deham01. The monitoring says it's still online, but i can't reach any host over ipv6. Tracepath6 is only reporting "no reply".
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Monday, 20 April 2009 16:01:55
Message is Locked
The state of this ticket has been changed to user
deham01 seems to be down
[de] Shadow Hawkins SixXS Oper on Monday, 20 April 2009 16:03:43
Three tunnels at that pop were down and another buddy reported the same issue, so it's my own problem? By the way, seems to be back more or less: --- ipv6.google.com ping statistics --- 100 packets transmitted, 51 received, 49% packet loss, time 99542ms rtt min/avg/max/mdev = 132.741/133.743/138.056/0.890 ms
deham01 seems to be down
[ch] Jeroen Massar SixXS Staff on Monday, 20 April 2009 16:08:56
Ping *where* ? Please properly report things. If your 'buddy' also has issues, then let him _properly_ report them. Please actually follow the instructions as asked for in those big orange/yellow boxes. We ask for it to a reason.
deham01 seems to be down
[ch] Jeroen Massar SixXS Staff on Monday, 20 April 2009 16:04:17
You might want to actually include the output of your 'tracepath6' and of course read that big yellow box which links to the contact page which in turn contains a nice long list of items you should supply. Not supplying anything is far from useful. Just in case: jeroen@noc:~$ tracepath6 deham01.sixxs.net 1?: [LOCALHOST] pmtu 1500 1: ge-1-3-0.breda.ipv6.concepts-ict.net 1.200ms asymm 2 1: ge-1-3-0.breda.ipv6.concepts-ict.net 1.186ms asymm 2 2: 2001:838:0:10::1 3.323ms asymm 3 3: 2001:838:5:4::2 2.880ms 4: ams-ix-1.ip.tiscali.net 3.209ms asymm 5 5: xe-9-0-0.ams20.ip6.tiscali.net 3.446ms asymm 6 6: xe-11-3-0.fra20.ip6.tiscali.net 11.088ms asymm 7 7: no reply 8: 2001:6f8:1:0:87:86:77:248 10.741ms asymm 5 9: 2001:6f8:1:0:87:86:71:233 11.244ms asymm 7 10: ge1-13-140.br2.isham.de.easynet.net 19.706ms asymm 6 11: ge7-1.cr20.isham.de.easynet.net 28.825ms asymm 7 12: deham01.sixxs.net 61.898ms reached Resume: pmtu 1500 hops 12 back 57 Which shows that at least works fine.
deham01 seems to be down
[de] Shadow Hawkins SixXS Oper on Monday, 20 April 2009 16:07:33
I know, but all i saw was: root@kaya:~# tracepath6 noc.sixxs.net 1?: [LOCALHOST] pmtu 1280 1: no reply 2: no reply 3: no reply 4: no reply 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 Didn't thought it would be more usefull, to paste all that output into that ticket, so i described it in a little sentence. Was rather busy, so that i keeped that short.
deham01 seems to be down
[ch] Jeroen Massar SixXS Staff on Monday, 20 April 2009 16:09:25
Don't you think that that might be a *LOCAL* issue? Please actually read that big yellow/orange box.
deham01 seems to be down
[de] Shadow Hawkins SixXS Oper on Monday, 20 April 2009 16:25:32
I read it and the issue solved on it's own now. This is a tracepath of a buddy, who got also the same issue: 5. ge9-15.cr20.isham.de.easynet.net 0.0% 15 1.2 1.9 1.2 3.0 0.7 6. deham01.sixxs.net 21.4% 15 45.7 39.1 15.7 45.8 11.8 7. toshima.6bone.de 26.7% 15 132.0 106.4 50.1 134.3 33.2 The Source-Host of that output is 'shodan.eurorings.net'. Don't have any further informations, because the loss is now gone and not reproduceable anymore. If you still think it's a local issue, close that ticket, i'm fed up.
deham01 seems to be down
[ch] Jeroen Massar SixXS Staff on Monday, 20 April 2009 16:28:13
As you are clearly unable to provide any details whatsoever (you didn't even bother to mention the tunnel-id, or for that matter any other useful/identifying information), that is the only conclusion I can make, especially in the view that everything is working from what I can see.
deham01 seems to be down
[de] Shadow Hawkins SixXS Oper on Monday, 20 April 2009 16:33:07
Ah, i hoped that you could see, which tunnels i got at deham01. On my site i got that problem with T12416, T9161, T3900 and perhaps any other at deham01. From my buddy i only know the subnet 2001:6f8:131d::/48, which is connected via a heartbeat-tunnel.

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

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