From owner-freebsd-hackers@FreeBSD.ORG  Mon Jun 27 19:27:08 2005
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: hackers@freebsd.org
Delivered-To: freebsd-hackers@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 50F0716A41C
	for <hackers@freebsd.org>; Mon, 27 Jun 2005 19:27:08 +0000 (GMT)
	(envelope-from dmp@bitfreak.org)
Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 26ECD43D48
	for <hackers@freebsd.org>; Mon, 27 Jun 2005 19:27:08 +0000 (GMT)
	(envelope-from dmp@bitfreak.org)
Received: from SMILEY (mail.bitfreak.org [65.75.198.146])
	by mail.bitfreak.org (Postfix) with ESMTP id 00E8C19F3B;
	Mon, 27 Jun 2005 12:28:55 -0700 (PDT)
From: "Darren Pilgrim" <dmp@bitfreak.org>
To: "'Niki Denev'" <nike_d@cytexbg.com>
Date: Mon, 27 Jun 2005 12:27:06 -0700
Message-ID: <004f01c57b4e$34a289a0$0b2a15ac@SMILEY>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
In-Reply-To: <42C051D3.2080709@cytexbg.com>
Importance: Normal
Cc: hackers@freebsd.org
Subject: RE: How to disable at-boot configuration of a network interface but
	permit manual use of rc.d?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jun 2005 19:27:08 -0000

From: Niki Denev [mailto:nike_d@cytexbg.com] 
> Darren Pilgrim wrote:
> > There are some conditions to the task given by the subject:
> > 
> > 1: The interface must be present at boot.
> > 2: Use of /etc/rc.d scripts to start and stop the interface
> > is desirable.
> > 
> > The first condition poses no problem, just don't include the
> > relevant ifconfig_ifn line in /etc/rc.conf and the interface won't
> > be configured. But rc.d/dhclient and rc.d/netif won't work without
> > an ifconfig line for the interface.
> > 
> > Adding the ifconfig line and then listing every interface but the
> > one I want configured in network_interfaces does prevent it from
> > being configured at boot while having an ifconfig line in rc.conf,
> > but if I try to use rc.d/netif to start the interface, rc.d/netif
> > does nothing because it tests the interface against the contents
> > of network_interfaces and cloned_interfaces, so the interface I
> > left out will be excluded.
> > 
> > Have I overlooked an option somewhere?
> 
> What happens if you configure the interface in 'down' state, like :
> 
> ifconfig_fxp0="inet 192.168.0.10 netmask 0xffffff00 down"

Then rc.d/dhclient won't work.  The "DHCP" keyword must be present in
the ifconfig line in order for dhcpif to test true.  A similar logic is
in place for wpaif based on the "WPA" keyword.