Date: Tue, 6 Jun 2017 13:27:37 -0700 From: Maxim Sobolev <sobomax@sippysoft.com> To: "Andrey V. Elsukov" <bu7cher@yandex.ru> Cc: Hal Murray <hmurray@megapathdsl.net>, FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: Anybody using SO_BINTIME with IPv6? Message-ID: <CAH7qZfv8U6QPaybdzkY=b8UVGnSCrbAq9_jB2--S9ouFuit-sQ@mail.gmail.com> In-Reply-To: <af550944-c84f-6a3c-65eb-60b05259df6b@yandex.ru> References: <20170606064039.4F3FE406063@ip-64-139-1-69.sjc.megapath.net> <af550944-c84f-6a3c-65eb-60b05259df6b@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <bu7cher@yandex.ru> 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: sales@sippysoft.com Skype: SippySoft
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAH7qZfv8U6QPaybdzkY=b8UVGnSCrbAq9_jB2--S9ouFuit-sQ>