SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #513337
Ticket Status: Invalid

PoP: iedub01 - HEAnet (Dublin)

Tunnel stats incorrect?
[ie] Shadow Hawkins on Sunday, 29 April 2007 13:31:19
I've noticed that my tunnel stats (T10907) since last night are reporting 100% packet loss (bar one moment when it reported 80% loss) However I did get credits for uptime today and I can ping my endpoint from my home pc and get a response from it:
Pinging 2001:770:100:ae::1 from 2001:770:100:90::2 with 32 bytes of data: Reply from 2001:770:100:ae::1: bytes=32 time=12ms Reply from 2001:770:100:ae::1: bytes=32 time=13ms Reply from 2001:770:100:ae::1: bytes=32 time=12ms Reply from 2001:770:100:ae::1: bytes=32 time=12ms
Pinging 2001:770:100:ae::2 from 2001:770:100:90::2 with 32 bytes of data: Reply from 2001:770:100:ae::2: bytes=32 time=14ms Reply from 2001:770:100:ae::2: bytes=32 time=14ms Reply from 2001:770:100:ae::2: bytes=32 time=14ms Reply from 2001:770:100:ae::2: bytes=32 time=15ms
State change: invalid Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 29 April 2007 13:33:53
Message is Locked
The state of this ticket has been changed to invalid
Tunnel stats incorrect?
[ch] Jeroen Massar SixXS Staff on Sunday, 29 April 2007 13:37:01
The latency stats are fine according to the latency stats page as such, if the stats mention downtime, most likely your tunnel was not responding to ICMP. Please read the FAQ and also of course the "Reporting Problems" section of the contact page, as indicated in the big clear green bar in the forum page. the FAQ on endpoints not pinging and the FAQ on NAT's and loosing connectivity

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

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