From owner-freebsd-rc@FreeBSD.ORG Wed Dec 28 07:00:23 2011 Return-Path: Delivered-To: freebsd-rc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08789106566B; Wed, 28 Dec 2011 07:00:22 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebius.int.ru (glebius.int.ru [81.19.64.117]) by mx1.freebsd.org (Postfix) with ESMTP id 75B6F8FC12; Wed, 28 Dec 2011 07:00:13 +0000 (UTC) Received: from cell.glebius.int.ru (localhost [127.0.0.1]) by cell.glebius.int.ru (8.14.5/8.14.5) with ESMTP id pBS6wjkr034958; Wed, 28 Dec 2011 10:58:45 +0400 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebius.int.ru (8.14.5/8.14.5/Submit) id pBS6wj6l034957; Wed, 28 Dec 2011 10:58:45 +0400 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebius.int.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 28 Dec 2011 10:58:45 +0400 From: Gleb Smirnoff To: Doug Barton Message-ID: <20111228065845.GZ8035@glebius.int.ru> References: <4EB6693F.2020102@delphij.net> <4EF93429.4020404@FreeBSD.org> <4EF971E4.4050905@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4EF971E4.4050905@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Pyun Yong-Hyeon , Brooks Davis , freebsd-rc@FreeBSD.org, Eygene Ryabinkin , Dag-Erling Smorgrav , d@delphij.net, Xin LI Subject: Re: Annoying ERROR: 'wlan0' is not a DHCP-enabled interface X-BeenThere: freebsd-rc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion related to /etc/rc.d design and implementation." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Dec 2011 07:00:23 -0000 On Mon, Dec 26, 2011 at 11:21:08PM -0800, Doug Barton wrote: D> > Worse, this solution will ruin host's connectivity in the following D> > scenario: D> > D> > - one runs his remote server with all static configuration and strict, D> > default-to-deny firewall configuration (call this person "Eygene D> > Ryabinkin"); D> > D> > - his upstream provider tells him: listen, we're rearranging our IP D> > space and you should change IP1 to IP2; D> > D> > - administrator is busy changing the configuration of his host; his D> > plan is to substitute IP1 to IP2 everywhere and to reboot his D> > machine to cleanly acquire IP2 and continue operations; D> > D> > - he already substituted IP1 -> IP2 in rc.conf and starts poking D> > the firewall configuration, but here comes the link down event D> > due to the $PROVIDER who reconfigures his $CISCO or whatever; D> > D> > - the system ends up in an unusable state, because link up event D> > will change interface's IP, but firewall isn't ready for this D> > and isn't allowing connections to IP2, but allows them only for D> > IP1 that is already gone from the interface due to devd and netif D> > script. D> D> First, I think what you're describing is a pretty small edge case. This case makes the suggested change unacceptable. This is a common practice to change things with ifconfig w/o modifing rc.conf, and if things go wrong then call server room personnel and ask to reboot a box. So box ma y have different configuration in rc.conf and on interfaces for a long time. Moreover, even if I got the same IP in rc.conf and on an interface, I don't want any address deletion or assignment on link event. This would be spurious messages for routing daemons. -- Totus tuus, Glebius.