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 11:43:39 CEST 2013
Hi Stephane, On 2013/07/21 21:34 , Stephane Bortzmeyer wrote: > When a ping or traceroute emasurement fails, we do not know the IP > address of the probe (empty "from" and no "src_addr"), which is > annoying when you want to analyze the possible causes of the failure: > > The most likely cause for this is that the probe has no IPv6 default router. The from field is filled with the address that is used to connect to the controller. If a probe doesn't have IPv6 connectivity then that is address is unknown. The src_addr is not there because of the way the linux kernel works. Most measurements use the bind system call to find out which local address will be used for outgoing packets. But if there is not route to the destination then bind will fail. 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. 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 ]