SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1124695
Ticket Status: Resolved

PoP: usqas01 - OCCAID Inc. (Ashburn, Virginia)

System reports "tunnel already exists for this endpoint"
[ve] Carmen Sandiego on Saturday, 27 June 2009 00:29:38
Hello, As instructed in the tunnel rejection email, I'm requesting a tunnel for endpoint 204.14.45.42 to usqas01. I already had one disabled, so I enabled it and the tunnel was no longer working. I deleted the tunnel, and tried to request a new one for the same endpoint and PoP, but the system rejects me saying a tunnel already exists for that endpoint. OTOH, I was debited 10 ISKs for requesting a tunnel to uslax01 (since we already had downtime with usqas01) but I was rejected and told to go to usqas01, but I was not credited the 10 ISKs. Thanks for your time and work, Jose
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 27 June 2009 00:30:48
Message is Locked
The state of this ticket has been changed to user
System reports "tunnel already exists for this endpoint"
[ch] Jeroen Massar SixXS Staff on Saturday, 27 June 2009 00:33:07
I already had one disabled, so I enabled it and the tunnel was no longer working.
PoPs are only synced every once in a while, not the very instant you press "enable" there. Static tunnels are static and thus long term. If you want a tunnel that goes on/off all the time use a dynamic tunnel. T15888 re-enabled, and at least the PoP side pings: 64 bytes from 2001:4830:1600:15d::1: icmp_seq=1 ttl=57 time=106 ms
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 27 June 2009 00:33:12
Message is Locked
The state of this ticket has been changed to resolved

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

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