SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #8918938
Ticket Status: User

PoP: iedub01 - HEAnet (Dublin)

Can't communicate with remote endpoint
[ie] Shadow Hawkins on Friday, 01 March 2013 20:57:41
Hi, Conor Quigley. schro@konundrum.org C90-RIPE Tunnel experiencing the issue: T88978 Using aiccu. I changed my tunnel type from AYIYA to Heartbeat and I cannot communicate with the remote end point anymore. It was working perfectly before I made the change. ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:770:100:1af::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was successful then this could be both ### a firewalling and a routing/interface problem PING 2001:770:100:1af::1(2001:770:100:1af::1) 56 data bytes --- 2001:770:100:1af::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2008ms ###### Did this work? [Y/n] n ::::: aiccu.conf ::: username CQ90-RIPE/T88978 password REMOVED ipv6_interface sixxs tunnel_id T88978 verbose false daemonize true automatic true requiretls false I need this tunnel for a conference tomorrow, can you treat this as urgent ? Kind regards, Conor Quigley.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Friday, 01 March 2013 23:52:01
Message is Locked
The state of this ticket has been changed to user
Can't communicate with remote endpoint
[ch] Jeroen Massar SixXS Staff on Friday, 01 March 2013 23:53:27
I need this tunnel for a conference tomorrow, can you treat this as urgent ?
Your side is broken, not ours, also we do not have ETAs (and it is weekend) even if it was anything on our side. Also, please note that big yellow/orange box which asks for a lot more details than what you are providing.

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

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