It seems like the tunnel machine in .nl is down.
But i can't find a status of the POP's.
Where to find this?
Or can someone confirm that .nl is down?
Confirmed:
ping -c5 216.66.84.46 (ams1)
PING 216.66.84.46 (216.66.84.46) 56(84) bytes of data.
--- 216.66.84.46 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4012ms
tserv11.ams1.ipv6.he.net is currently down and we're working with the facility on getting it back up.
In the meantime if you want to resume IPv6 connectivity, I'd recommend switching to another European tunnel-server in the interim.
Otherwise once the matter is resolved, I'll let you folks know.
i already tried to make a second tunnel using the german pop.
But the ipv4 is already in use ofcourse...
SO if there is another way...
Quote from: pozorjed on October 14, 2008, 12:07:06 PM
i already tried to make a second tunnel using the german pop.
But the ipv4 is already in use ofcourse...
SO if there is another way...
temporarily change the ipv4 endpoint on your ams tunnel, then set up the new tunnel with that endpoint.
Ok due to the amount of time it was taking to get any sort of response from the facility in Amsterdam, we've temporarily moved the tunnels to the Frankfurt tunnel server. The IPv4 endpoint won't need to be changed on your side, and you can still log in and update your IPv4 endpoint for the Amsterdam tunnel if you need to. Right now we aren't allowing any new tunnels to be created for that tunnel-server until the issue is finally resolved.
Once the issue is resolved, we'll migrate the tunnels back.
FYI we've migrated the tunnels back to tserv11.ams1 now that the facility has completed our requests, and the system passes all checks & tests.
Quote from: broquea on October 15, 2008, 02:40:56 PM
FYI we've migrated the tunnels back to tserv11.ams1 now that the facility has completed our requests, and the system passes all checks & tests.
Great. Thanks for the time and effort!