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] No address in the results when ping or traceroute fail?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon Jul 22 16:29:52 CEST 2013
On 2013/07/22 16:20 , Stephane Bortzmeyer wrote: > On Mon, Jul 22, 2013 at 11:43:39AM +0200, > Philip Homburg <philip.homburg at ripe.net> wrote > a message of 25 lines which said: > >> The most likely cause for this is that the probe has no IPv6 default >> router. > Well, IMHO, probes without a router should not be eligible for IPv6 > measurements. Yes, but that will be some future change to the system >> Probes also report their network configuration but at the moment >> that is done in a format that is not easy to parse. The next >> firmware should fix that. Then we can see how to make that >> information available. > It would not solve the problem since the probe may renumber between > the moment you fetch the (semi-static) info and the measurement. And > it is even worse for probes with multiple addresses. We really need to > know the adress actually used during the measurement. > That is easy. The probe didn't actually send any packets so there is no point in knowing the source address that wasn't used. :-) Philip
- Previous message (by thread): [atlas] No address in the results when ping or traceroute fail?
- Next message (by thread): [atlas] No address in the results when ping or traceroute fail?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]