On Sun, 2020-08-02 at 22:44 +0200, Thorsten Glaser wrote: > On Sun, 2 Aug 2020, Ben Hutchings wrote: > > > The RFC says that the IPV6_TCLASS option's value is an int, and that > > for setsockopt (“option's”), not cmsg > > > No, the wording is *not* clear. > > Agreed. > > So perhaps let’s try to find out what’s actually right… For what it's worth, FreeBSD/Darwin and Windows also put 4 bytes of data in a IPV6_TCLASS cmsg. So whether or not it's "right", it's consistent between three independent implementations. Ben. -- Ben Hutchings For every complex problem there is a solution that is simple, neat, and wrong.
Attachment:
signature.asc
Description: This is a digitally signed message part