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] Feature Request to consider: DNS response IP header
- Previous message (by thread): [atlas] Feature Request to consider: DNS response IP header
- Next message (by thread): [atlas] RFC1918 probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Fri May 31 16:51:09 CEST 2019
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
- Previous message (by thread): [atlas] Feature Request to consider: DNS response IP header
- Next message (by thread): [atlas] RFC1918 probes
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]