This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] No address in the results when ping or traceroute fail?
- Previous message (by thread): [atlas] No address in the results when ping or traceroute fail?
- Next message (by thread): [atlas] Ping Fails (ns.ripe.net)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Klaus Darilion
klaus.darilion at nic.at
Tue Jul 23 11:12:21 CEST 2013
On 22.07.2013 16:39, Stephane Bortzmeyer wrote: > On Mon, Jul 22, 2013 at 04:29:52PM +0200, > Philip Homburg <philip.homburg at ripe.net> wrote > a message of 23 lines which said: > >> The probe didn't actually send any packets so there is no point in >> knowing the source address that wasn't used. :-) > I wanted to reply to Dan Wing's criticism > <https://labs.ripe.net/Members/stephane_bortzmeyer/how-many-atlas-probes-believe-they-have-ipv6-but-are-wrong/> > "I have a suspicion that many of these failures are IPv6 tunnels that > have suffered bit rot. Could you analyze the IPv6 address that the > Atlas probe thinks it has and split them into two categories: (a) > known tunnels (e.g., Hurricane Electric, SixXS, 6to4, Teredo) versus > (b) presumably "native" IPv6 addresses. " Yes, this is annoying. Many probes have IPv6 tunnels. Probably they show the "real world" view of IPv6, but often I am interested in native IPv6. When selecting probes manually I only use probes that are located in the same AS for IPv4 and IPv6. regards Klaus
- Previous message (by thread): [atlas] No address in the results when ping or traceroute fail?
- Next message (by thread): [atlas] Ping Fails (ns.ripe.net)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]