TOS is return using wrong control. It should be IP_TOS, IPPROTO_IP not IP_RECVTOS, IPPROTO_IP. The latter is the flag to turn returning the value on or off. Compare with TCLASS in IPv6. The value is returned using IPPROTO_IPV6 and IPV6_TCLASS not IPPROTO_IPV6 and IPV6_RECVTCLASS.
Responsible Changed From-To: freebsd-bugs->freebsd-net Over to maintainer(s).
It was not done by accident. The returned cmsg_type is IP_RECVTOS = instead of IP_TOS to keep it consistent with the handling of the IP_RECVTTL socket = option. I found it more important to be consistent within the same protocol = family than across different ones. I think that unfortunately IP_RECVTOS is not defined in any standard. Best regards Michael=
In message <25EB2335-645C-42ED-B90A-6D07A33280DB@freebsd.org>, Michael Tuexen w rites: > It was not done by accident. The returned cmsg_type is IP_RECVTOS instead > of IP_TOS to keep it consistent with the handling of the IP_RECVTTL socket > option. > I found it more important to be consistent within the same protocol family > than across different ones. > I think that unfortunately IP_RECVTOS is not defined in any standard. > > Best regards > Michael And Linux uses IP_TOS to return the value. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
On Mar 27, 2013, at 12:54 PM, Mark Andrews wrote: >=20 > In message <25EB2335-645C-42ED-B90A-6D07A33280DB@freebsd.org>, Michael = Tuexen w > rites: >> It was not done by accident. The returned cmsg_type is IP_RECVTOS = instead=20 >> of IP_TOS to keep it consistent with the handling of the IP_RECVTTL = socket=20 >> option. >> I found it more important to be consistent within the same protocol = family >> than across different ones. >> I think that unfortunately IP_RECVTOS is not defined in any standard. >>=20 >> Best regards >> Michael >=20 > And Linux uses IP_TOS to return the value. ... which is consistent with the IP_RECVTTL socket option on Linux, = where it returns a cmsg with cmsg_type IP_TTL, which is also different from how this is = handled in FreeBSD. I think Solaris uses for IPv4 socket options the same cmsg_type as the optname for the socket option to enable the reception of the = cmsg. So it looks like there is no standard here, Linux, FreeBSD and Solaris are each consistent with itself, but Linux does it differently from FreeBSD and Solaris. Best regards Michael >=20 > --=20 > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: marka@isc.org >=20
State Changed From-To: open->feedback tuexen@ does not see a need for code change. Waiting for submitter feedback.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped