[atlas] sometimes no RTT?
- Previous message (by thread): [atlas] sometimes no RTT?
- Next message (by thread): [atlas] sometimes no RTT?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Saroyan
alexsaroyan at gmail.com
Fri Jul 8 14:19:49 CEST 2016
Philip, I am a bit confused, is that "late reply from the probe" or it is "late reply from router - basically timed out reply" ? Should it be treated like packet loss ? Regards. /Alex Saroyan On Fri, Jul 8, 2016 at 4:06 PM, Philip Homburg <philip.homburg at ripe.net> wrote: > On 2016/07/08 12:07 , Antranig Vartanian wrote: > > sure! Probe ID: 938. Hop: 12 I uploaded that probe's json part - > > https://antranigv.am/misc/result_prb_id_938.json :) > > Hi, > > There is a 'late' field. Basically that means that the packet arrived > after the traceroute code already timed out. The current implementation > stores just one transmit time. So after it moved on, there is no way to > compute the rtt. > > Philip > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20160708/0bb5e693/attachment.html>
- Previous message (by thread): [atlas] sometimes no RTT?
- Next message (by thread): [atlas] sometimes no RTT?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]