Feature Request to consider: DNS response IP header
Hello, I have a number of use cases when it would be very useful to have access to the IP header of the measurement response packets. In my scenario I'd like to see TTL/Hop Limit of packets received in DNS measurements. So I'm curious if anyone else think it would be a useful feature and if there is some demand for such a feature - maybe the Atlas team could consider implementing it? Thanks! -- SY, Jen Linkova aka Furry
Hello, On 20. 05. 19 17:08, Jen Linkova wrote:
Hello,
I have a number of use cases when it would be very useful to have access to the IP header of the measurement response packets. In my scenario I'd like to see TTL/Hop Limit of packets received in DNS measurements.
So I'm curious if anyone else think it would be a useful feature and if there is some demand for such a feature - maybe the Atlas team could consider implementing it?
Yes, I think it is occasionally useful. -- Petr Špaček @ CZ.NIC
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. Regards, Grzegorz From: Jen Linkova <furry13@gmail.com> Date: Monday 2019-05-20 at 19:08 To: "ripe-atlas@ripe.net" <ripe-atlas@ripe.net> Subject: [atlas] Feature Request to consider: DNS response IP header Hello, I have a number of use cases when it would be very useful to have access to the IP header of the measurement response packets. In my scenario I'd like to see TTL/Hop Limit of packets received in DNS measurements. So I'm curious if anyone else think it would be a useful feature and if there is some demand for such a feature - maybe the Atlas team could consider implementing it? Thanks! -- SY, Jen Linkova aka Furry
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
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@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
participants (4)
-
Jen Linkova -
Petr Špaček -
Philip Homburg -
Ponikierski, Grzegorz