From owner-freebsd-stable@FreeBSD.ORG  Fri Dec  9 18:01:50 2011
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5431E106564A
	for <freebsd-stable@freebsd.org>; Fri,  9 Dec 2011 18:01:50 +0000 (UTC)
	(envelope-from brett@lariat.net)
Received: from lariat.net (lariat.net [66.62.230.51])
	by mx1.freebsd.org (Postfix) with ESMTP id DB4C08FC0A
	for <freebsd-stable@freebsd.org>; Fri,  9 Dec 2011 18:01:49 +0000 (UTC)
Received: from WildRover.lariat.net (IDENT:ppp1000.lariat.net@lariat.net
	[66.119.58.2] (may be forged))
	by lariat.net (8.9.3/8.9.3) with ESMTP id KAA08794;
	Fri, 9 Dec 2011 10:31:07 -0700 (MST)
Message-Id: <201112091731.KAA08794@lariat.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 09 Dec 2011 10:30:43 -0700
To: Johan Hendriks <joh.hendriks@gmail.com>,
	freebsd-stable <freebsd-stable@freebsd.org>
From: Brett Glass <brett@lariat.net>
In-Reply-To: <4EE1DEAD.2040108@gmail.com>
References: <201112090913.CAA03333@lariat.net>
 <4EE1DEAD.2040108@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 
Subject: Re: Two problems still present in RC3
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Dec 2011 18:01:50 -0000

At 03:10 AM 12/9/2011, Johan Hendriks wrote:

>After a /etc/netstart, i get the following:
>ifconfig: create: bad value.

I get the "create: bad value" messages as well. What's more, if I 
change rc.conf to assign variables of the form ifconfig_*, such as

ifconfig_re0_1="inet 192.168.0.1"
ifconfig_re0_1_alias0="inet 192.168.0.2"
...

instead of using an ip_addrs_* variable, I still get those messages.

I have confirmed that if I run /etc/netstart after booting, I lose 
connectivity just as you do.

I recognize the challenge of specifying the network configuration 
in a declaratory rather than a procedural environment, because 
there are so many contingencies and possible combinations of 
parameters. But there doesn't seem to be any combination of 
variables I can assign in rc.conf that doesn't cause errors when I 
try to create VLANs.

--Brett Glass