From owner-freebsd-stable@FreeBSD.ORG Thu Oct 5 11:59:00 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B441316A416 for ; Thu, 5 Oct 2006 11:59:00 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A72943D53 for ; Thu, 5 Oct 2006 11:58:59 +0000 (GMT) (envelope-from uspoerlein@gmail.com) Received: by wx-out-0506.google.com with SMTP id i27so480266wxd for ; Thu, 05 Oct 2006 04:58:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=HwukpKmiirbsWVDmGAzu8FlphsPXP5YC2sAMzqGoOKNXrp7USpOTI4hSso1AiXzVut5HecF4qgUsovrFQAvfINGm44li9Kcjcv3rd8edaAUzquIoSIRq9gJvmSCUxGWvYhXseK49mtkij8TnfYgsVI6EAWJX2e0kptjuIksYsSU= Received: by 10.90.71.12 with SMTP id t12mr689689aga; Thu, 05 Oct 2006 04:58:59 -0700 (PDT) Received: by 10.90.70.6 with HTTP; Thu, 5 Oct 2006 04:58:59 -0700 (PDT) Message-ID: <7ad7ddd90610050458v6b26aeefs3b72dfc58fa6a608@mail.gmail.com> Date: Thu, 5 Oct 2006 13:58:59 +0200 From: "Ulrich Spoerlein" To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Start system with 'downed' carp interfaces X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Oct 2006 11:59:00 -0000 Hello, I'm looking for a generic way to create and configure carp interfaces upon boot (so daemons can bind against the IP address), but keep the carp interfaces 'down'. This is to allow the administrator to first check every service after the failure, and if deemed ready, put the system back into production by simply issuing: ifconfig carp0 up But there are several problems: ifconfig_carp0="foo bar" will always "up" the interface first via /etc/rc.d/netif ifconfig carp0 foo bar down will ignore the 'down' and up the interface. This is especially announing. I wish ifconfig would honour the down statement, even though the manpage says the interface will always be brought up when assigned its first address. Using a start_if.carp0 with the following contents ifconfig carp0 vhid 1 1.2.3.4/24 ifconfig carp0 down and ifconfig_carp0="down" in rc.conf will result in an 'up' interface. I also disabled devd, as it seems to be running pccard_ether carp0 start as a result of the interface creation. Although it is started sometime after the interface has been created. How are other people handling the startup of carp interfaces? Uli