SO_BINTIME was ENOTSUPP with IPv6 from the day one. In general I think it's safe to advise to use SO_TIMESTAMP instead, which is also more flexible interface. I'd suggest SO_BINTIME is marked as obsoleting one instead.
-Max On Tue, Jun 6, 2017 at 8:39 AM, Andrey V. Elsukov <[email protected]> wrote: > On 06.06.2017 09:40, Hal Murray wrote: > > > > I'm cleaning up some code. SO_BINTIME works with IPv4. SO_TIMESTAMP > works > > with IPv4 and IPv6. > > > > But SO_BINTIME doesn't work with IPv6. setsockopt works, but recvmsg > doesn't > > return any cmsg data. > > > > If this is a known problem, I'll just use SO_TIMESTAMP and accept the > reduced > > resolution. If somebody has a working example, I'll work harder on > finding a > > bug/quirk and/or making a simple test case. > > Hi, > > it seems like a bug, that is easy to fix, but Maxim has already > implemented another option in this patch > https://reviews.freebsd.org/D9171 > > -- > WBR, Andrey V. Elsukov > > -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts Tel (Canada): +1-778-783-0474 <(778)%20783-0474> Tel (Toll-Free): +1-855-747-7779 <(855)%20747-7779> Fax: +1-866-857-6942 <(866)%20857-6942> Web: http://www.sippysoft.com MSN: [email protected] Skype: SippySoft _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[email protected]"
