SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #5734362
Ticket Status: Remote Problem

PoP: uschi03 - Team Cymru (Chicago, Illinois)

very high ipv6 packet loss, but very good for PoP ipv4 address.
[cn] Shadow Hawkins on Saturday, 15 October 2011 20:50:25
ping 38.229.76.3 is ok, Packets: Sent = 371, Received = 371, Lost = 0 (0% loss). ping 2604:8800:100:d5::1 is very high packet loss, Packets: Sent = 179, Received = 88, Lost = 91 (50% loss). Here is my tunnel info, PoP Nameuschi03 PoP IPv438.229.76.3 TIC Servertic.sixxs.net (default in AICCU) PoP IPv62604:8800:100:d5::1 Your IPv62604:8800:100:d5::2 Mine ip, 114.80.81.29, there is hardware firewall over my server, only accept tcp/udp/icmp outbound, limited tcp/udp ports inbound, no icmp inbound limit, and deny all other protocols.
very high ipv6 packet loss, but very good for PoP ipv4 address.
[cn] Shadow Hawkins on Saturday, 15 October 2011 21:13:12
After restart aiccu, problem solved. Very interesting.
very high ipv6 packet loss, but very good for PoP ipv4 address.
[cn] Shadow Hawkins on Saturday, 15 October 2011 21:17:44
after short time, problem come back. ping PoP ipv6 address, Packets: Sent = 91, Received = 76, Lost = 15 (16% loss). It still high packet loss on ipv6 tunnel.
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 16 October 2011 00:00:47
Message is Locked
The state of this ticket has been changed to remoteproblem
very high ipv6 packet loss, but very good for PoP ipv4 address.
[ch] Jeroen Massar SixXS Staff on Sunday, 16 October 2011 00:02:33
Please realize that there is a very long path between your endpoint and the PoP and that there might be many locations where active filtering and rate limiting is being performed. You might be able to determine part of this with a tool like 'mtr', but likely the network where this is happening is far outside our reach to do anything about it.

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

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