From owner-freebsd-net@freebsd.org Wed Jun 7 10:20:33 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 55200C08C43 for ; Wed, 7 Jun 2017 10:20:33 +0000 (UTC) (envelope-from hmurray@megapathdsl.net) Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by mx1.freebsd.org (Postfix) with ESMTP id 3D00E6E13C for ; Wed, 7 Jun 2017 10:20:32 +0000 (UTC) (envelope-from hmurray@megapathdsl.net) Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 8C44C406063; Wed, 7 Jun 2017 03:20:26 -0700 (PDT) X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: Maxim Sobolev cc: FreeBSD Net , Hal Murray From: Hal Murray Subject: Re: Anybody using SO_BINTIME with IPv6? In-Reply-To: Message from Maxim Sobolev of "Tue, 06 Jun 2017 13:27:37 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Jun 2017 03:20:26 -0700 Message-Id: <20170607102026.8C44C406063@ip-64-139-1-69.sjc.megapath.net> 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: Wed, 07 Jun 2017 10:20:33 -0000 sobomax@sippysoft.com said: > SO_BINTIME was ENOTSUPP with IPv6 from the day one. Thanks. Is that a literal ENOTSUPP? Should I get an error from setsockopt? Or is that just shorthand for never-got-implemented? Do you want a bug report? If nothing else, the man page should be updated. Just curious... Why wasn't SO_BINTIME implemented for IPv6? Since it works for IPv4 and SO_TIMESTAMP works for IPv4 and IPv6 I'd expect it would be easy to copy a few lines of code. -- These are my opinions. I hate spam.