From owner-freebsd-hackers@freebsd.org Fri Mar 16 17:24:41 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 861FCF5FA43 for ; Fri, 16 Mar 2018 17:24:41 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 29C406A7D9; Fri, 16 Mar 2018 17:24:40 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 402slQ0hTnzCV; Fri, 16 Mar 2018 12:24:34 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 402slP37MvzC47; Fri, 16 Mar 2018 12:24:33 -0500 (CDT) Date: Fri, 16 Mar 2018 12:24:33 -0500 From: "Matthew D. Fuller" To: Patrick Kelsey Cc: freebsd-hackers@freebsd.org Subject: Re: option TCP_RFC7413 is not in GENERIC Message-ID: <20180316172433.GF83683@over-yonder.net> References: <1521062028.2511351.1303413736.6960BF4F@webmail.messagingengine.com> <20180314233811.GA35025@mail.bsd4all.net> <1521216713.99081.55.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2018 17:24:41 -0000 On Fri, Mar 16, 2018 at 04:42:10PM +0000 I heard the voice of Patrick Kelsey, and lo! it spake thus: > > I'm curious as to why you were forced to add the option to your > kernel config when you installed bind911. I suspect it's not quite "forced to", but you otherwise have to ignore all the squawcking it does every time it starts up about failing to set the option on all its sockets... (me, I moved past ignoring it to taking perverse pleasure in it. Haha, silly daemon. You brought this on yourself, so now you must suffffaaaahhhh...) -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.