From owner-freebsd-net@FreeBSD.ORG Mon Jun 17 23:57:10 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 354D5D81; Mon, 17 Jun 2013 23:57:10 +0000 (UTC) (envelope-from lists@rewt.org.uk) Received: from hosted.mx.as41113.net (hosted.mx.as41113.net [91.208.177.22]) by mx1.freebsd.org (Postfix) with ESMTP id F2CB81895; Mon, 17 Jun 2013 23:57:09 +0000 (UTC) Received: from [172.16.9.23] (bella.stf.rewt.org.uk [91.208.177.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3bZ8V62RTLz6d; Tue, 18 Jun 2013 00:57:01 +0100 (BST) Message-ID: <51BFA24D.70705@rewt.org.uk> Date: Tue, 18 Jun 2013 00:57:01 +0100 From: Joe Holden User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Jason Hellenthal Subject: Re: How not allow setting ip changes interface down status? References: <69CF1AAF-230D-4B2B-9C95-20DDD772997E@dataix.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: h bagade , "freebsd-net@freebsd.org" , Adrian Chadd , Jack Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jun 2013 23:57:10 -0000 Jason Hellenthal wrote: > Off the top of my head I don't know of another OS that does this. > > But yes agreed changing that behavior would probably effect a lot of people in a negative way at this point. > > Not to mention script breakage. > > But a tunable in the stack somewhere would be awesome to change this behavior. Either interface specific or global or both. > > Sometimes installing a new faucet you don't want the water to run until all the nuts, bolts and washers are installed. > The entire notion is ridiculous, it is quite simple - if the interface is down, it isn't in the FIB, you can't arbitarily return an error for setting an IP on an interface that isn't up. The last thing we need is yet more nonsense stack changes, allowing 0/8 to be used was bad enough.