From owner-freebsd-net@freebsd.org Tue Jun 6 15:42:01 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04405BEF63F for ; Tue, 6 Jun 2017 15:42:01 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward1j.cmail.yandex.net (forward1j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AD0A70F00; Tue, 6 Jun 2017 15:42:00 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1h.mail.yandex.net (smtp1h.mail.yandex.net [84.201.187.144]) by forward1j.cmail.yandex.net (Yandex) with ESMTP id 60B1F210DD; Tue, 6 Jun 2017 18:41:47 +0300 (MSK) Received: from smtp1h.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1h.mail.yandex.net (Yandex) with ESMTP id B02358C0C02; Tue, 6 Jun 2017 18:41:45 +0300 (MSK) Received: by smtp1h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id rIx0QCJcmG-fiCK4vKw; Tue, 06 Jun 2017 18:41:44 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1496763704; bh=7ytKCuIlIdxP3p7/Yx9R0Uvxvmoj1ZROGQ6Oy3JwIxs=; h=Subject:To:References:Cc:From:Message-ID:Date:In-Reply-To; b=Udg2fl8ucRRoRzlAbtMT7kVR+sWONl3+rG77Ggubx7Um0RcJZ5blN/AA1KAzyJbBV pXe0oMDHo6fSPcChro7j3dleQnbumuSEdjz8fDd2cBtbzqMBn1RkB+iVfT1oLEKR1p b5QKWvxitPw4zDv1Qsr+qh+TDp5NBs/4IIFzapSA= Authentication-Results: smtp1h.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0 Subject: Re: Anybody using SO_BINTIME with IPv6? To: Hal Murray , freebsd-net@freebsd.org References: <20170606064039.4F3FE406063@ip-64-139-1-69.sjc.megapath.net> Cc: Maxim Sobolev From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Tue, 6 Jun 2017 18:39:37 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170606064039.4F3FE406063@ip-64-139-1-69.sjc.megapath.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="D6A1w9K94f36pXb9Mcf8r7rLQUH1JxuA2" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jun 2017 15:42:01 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --D6A1w9K94f36pXb9Mcf8r7rLQUH1JxuA2 Content-Type: multipart/mixed; boundary="I0I8RosmtdR4x8sqXQAAMpGxPA8vV4Q5G"; protected-headers="v1" From: "Andrey V. Elsukov" To: Hal Murray , freebsd-net@freebsd.org Cc: Maxim Sobolev Message-ID: Subject: Re: Anybody using SO_BINTIME with IPv6? References: <20170606064039.4F3FE406063@ip-64-139-1-69.sjc.megapath.net> In-Reply-To: <20170606064039.4F3FE406063@ip-64-139-1-69.sjc.megapath.net> --I0I8RosmtdR4x8sqXQAAMpGxPA8vV4Q5G Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 06.06.2017 09:40, Hal Murray wrote: >=20 > I'm cleaning up some code. SO_BINTIME works with IPv4. SO_TIMESTAMP w= orks=20 > with IPv4 and IPv6. >=20 > But SO_BINTIME doesn't work with IPv6. setsockopt works, but recvmsg d= oesn't=20 > return any cmsg data. >=20 > If this is a known problem, I'll just use SO_TIMESTAMP and accept the r= educed=20 > resolution. If somebody has a working example, I'll work harder on fin= ding a=20 > 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 --=20 WBR, Andrey V. Elsukov --I0I8RosmtdR4x8sqXQAAMpGxPA8vV4Q5G-- --D6A1w9K94f36pXb9Mcf8r7rLQUH1JxuA2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlk2zLkACgkQAcXqBBDI oXof/AgArQL3xslukPoScHlBb+IagKHKxL97U6XWFbdFVhfw70jwRm/kMAIc9lT7 PqhvJ2HrwY3U8nRNr+xSM47+Jz+OIZYQQU2bdZGOWl5f22ggZ2KnNTdhCgbQyp5+ sBCKTkIX4tQT3DxnXIODSI3eEUp/Plfyv8UNvfVnJ5BiXc3J5QblN0LnpgxKXxkc hRJIOfjgyImEw/FndUHYIaUeXU3BtrCFvRbns5TPQKN40HIo5xtpuwMQZYbsI73R +hyhfOCQKdq0WZCiYUxjqjNNU5UHuGNVHfhNTyz+9llP0H1khV14/Zu02fb68uDT CCLzd/xxq64Fo+K3n3Q7AZlNk/2Hgw== =8W5r -----END PGP SIGNATURE----- --D6A1w9K94f36pXb9Mcf8r7rLQUH1JxuA2--