SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #7858802
Ticket Status: User

PoP: nzwlg01 - Advanced Computer Solutions (ACSData) (Wellington)

"There is already a tunnel to 202.78.140.111 on this PoP" (DJG1-SIXXS)
[nz] Shadow Hawkins on Saturday, 22 September 2012 03:28:01
Hi I tried repurposing an old tunnel I hadn't used for a while (T53241), and pointed it to 202.78.140.111. Then I changed my mind and deleted it. Now when I try to point T13304 to that same IP, I get the error message in the subject: "There is already a tunnel to 202.78.140.111 on this PoP". Could you either undelete T53241, in which case I'll apply for a new ::/48 and then delete T13304 when I'm finished with it, or clear whatever it is that's generating that error message? What this is all in aid of: I'm going to share an internet connection with my neighbour, so I'm trying to get a tunnel to his router. Once that's all working I'll delete the tunnel to my router, which will no longer have a public IP anyway. Thanks. donald
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 22 September 2012 07:59:47
Message is Locked
The state of this ticket has been changed to user
"There is already a tunnel to 202.78.140.111 on this PoP" (DJG1-SIXXS)
[ch] Jeroen Massar SixXS Staff on Saturday, 22 September 2012 08:02:18
Please note that this is not a problem in our infrastructure, as such, please report these to info@sixxs.net instead.
clear whatever it is that's generating that error message?
What is generating the error is that you had a tunnel already pointing at that endpoint. I've marked T53241 as disabled, you can now change it to for instance an AYIYA type and then move T13304 to the IP address, instead of wasting a /48 subnet.
"There is already a tunnel to 202.78.140.111 on this PoP" (DJG1-SIXXS)
[nz] Shadow Hawkins on Tuesday, 25 September 2012 08:15:11
Hi The error was produced by the SixXS website when I tried to change T13304 to be a 6in4 static tunnel pointing to that IP -- at the time, T53241 was deleted, but I'd previously tried to point it to that IP before changing my mind. It's all sorted now. Thanks. donald

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

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