Re: [atlas] Feature Request to consider: DNS response IP header

[Jen Linkova]

Hi Philip,

Sorry, I've realised I did not replied..
Actually I'd be very happy if I can get HopLimit/TTL field.

On Sat, Jun 1, 2019 at 12:51 AM Philip Homburg  wrote:
>
> On 2019/05/30 15:22 , Ponikierski, Grzegorz wrote:
> > Can be useful to estimate proximity between probe and DNS and to detect
> > nasty middle boxes. To limit overhead on Atlas side, IP header can be
> > provided as raw data to decode on end-user side.
>
> As far as I know there is no option provided by the Linux kernel to
> receive the original IP header with recvmsg.
>
> Fields that are returned by recvmsg, such as TTL, can be added without
> to much trouble. I'll make a note to add that that at some point.
>
> Philip
>


-- 
SY, Jen Linkova aka Furry

Re: [atlas] Question about built-in first/second hop latency measurements

[Chris Amin]

Hi Joel,

Results from measurements 1 and 2 are really the first and second hops
of a single traceroute measurement with a max_hops value of 2.

Regards,
Chris Amin
RIPE NCC

On 22/07/2019 00:16, Joel Sommers wrote:
> Hello all,
> 
> For the built-in latency measurements to first/second hops, my assumption has 
> pretty much always been that these are done with hop-limited probes (i.e., 
> with TTL or hop limit set to 1 or 2).  Is that true, or are these 
> measurements taken using “direct” pings?
> 
> Thanks!
> 
> Joel
> 
> 
>