Although IP_RECVTTL is the socket option used to control the reporting, the
value is reported using IP_TTL.
This is intentional, and correct.
Begin forwarded message:
Date: Fri, 19 Mar 2021 07:04:12 +
From: bugzilla-dae...@bugzilla.kernel.org
To: step...@networkplumber.org
Subject: [Bug 212353] New: Requesting IP_RECVTTL via setsockopt returns IP_TTL
via recvmsg()'s cmsghdr
https://bugzilla.kernel.org/show_bug.cgi?id=2
@@ -285,7 +285,7 @@ Expects a boolean integer flag.
.B IP_RECVTTL
When this flag is set
pass a
-.I IP_RECVTTL
+.I IP_TTL
control message with the time to live
field of the received packet as a byte. Not supported for
.B SOCK_STREAM
@@ -789,6 +789,20 @@ received datagrams. Linux has the more g
.
On Tue, Aug 16, 2005 at 12:50:51PM +0300, Hasso Tepper wrote:
> According to man 7 ip:
>
> IP_RECVTTL
> When this flag is set pass a IP_RECVTTL control message with the
> time to live field of the received packet as a byte. Not
> supported for SOCK_STREAM
According to man 7 ip:
IP_RECVTTL
When this flag is set pass a IP_RECVTTL control message with the
time to live field of the received packet as a byte. Not
supported for SOCK_STREAM sockets.
This is not what happens. Instead of control message with type IP_RECVTTL
(12
