SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #847066
Ticket Status: User

PoP: nlams04 - Stipte B.V. (Amsterdam)

nlams04.sixxs.net down
[mt] Shadow Hawkins on Wednesday, 12 November 2008 09:56:19
It appears that just before midnight of Wed night, the nlams04.sixxs.net server is not tunneling IPv6 traffic anymore for me. The machine is however pingable and contactable on the IPv4 network. The status of the server is marked as up, however the traffic graphs of the server for the past day appear to be flattened to an absolute minimum although there is a slight trickle. I did not touch my configuration since yesterday and I found that the tunnel I had did not ping across the tunnel from my endpoint to the PoP. The output from tcpdump when I ping www.kame.net gives the following: 09:55:05.251708 IP 172.19.0.34.60494 > broker04.ams.nl.sixxs.net.ayiya: UDP, length 148 09:55:05.316671 IP broker04.ams.nl.sixxs.net > 172.19.0.34: ICMP broker04.ams.nl.sixxs.net udp port ayiya unreachable, length 184 09:55:06.266706 IP 172.19.0.34.60494 > broker04.ams.nl.sixxs.net.ayiya: UDP, length 148 09:55:06.335868 IP broker04.ams.nl.sixxs.net > 172.19.0.34: ICMP broker04.ams.nl.sixxs.net udp port ayiya unreachable, length 184
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 12 November 2008 11:36:17
Message is Locked
The state of this ticket has been changed to user
nlams04.sixxs.net down
[ch] Jeroen Massar SixXS Staff on Wednesday, 12 November 2008 11:36:36
Please provide all the details requested on the contact page.
nlams04.sixxs.net down
[mt] Shadow Hawkins on Wednesday, 12 November 2008 11:55:36
Problem appears to be solved on the side of nlams04. Thanks for the response

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

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