[atlas] Feature Request to consider: DNS response IP header
- Previous message (by thread): [atlas] Question about built-in first/second hop latency measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jen Linkova
furry13 at gmail.com
Mon Jul 22 21:51:05 CEST 2019
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 <philip.homburg at ripe.net> 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
- Previous message (by thread): [atlas] Question about built-in first/second hop latency measurements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]