From owner-freebsd-net@FreeBSD.ORG  Tue Nov 23 20:33:43 2010
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 6A761106566B
	for <freebsd-net@freebsd.org>; Tue, 23 Nov 2010 20:33:43 +0000 (UTC)
	(envelope-from rfg@tristatelogic.com)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
	[69.62.255.118])
	by mx1.freebsd.org (Postfix) with ESMTP id 4CF918FC08
	for <freebsd-net@freebsd.org>; Tue, 23 Nov 2010 20:33:42 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
	by segfault.tristatelogic.com (Postfix) with ESMTP id E0B71BDC75
	for <freebsd-net@freebsd.org>; Tue, 23 Nov 2010 12:33:41 -0800 (PST)
To: freebsd-net@freebsd.org
In-Reply-To: <20101123133820.GA36224@babolo.ru> 
Date: Tue, 23 Nov 2010 12:33:41 -0800
Message-ID: <45689.1290544421@tristatelogic.com>
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
Subject: Re: Configuring for 1 static and 1 DHCP interface ? 
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Nov 2010 20:33:43 -0000


In message <20101123133820.GA36224@babolo.ru>, 
Aleksandr A Babaylov <.@babolo.ru> wrote:

>On Tue, Nov 23, 2010 at 04:35:42AM -0800, Ronald F. Guilmette wrote:
>> I should say however that even this is going to produce a slightly sub-optim
>al
>> result, because (I guess) the DHCP client is _still_ going to wipe out my
>> eisting /etc/resolve.con file and then write its own.  Now that will at
>> least have the proper IP address in it _however_ there does not seem to
>> be any way to entice the DHCP client to place certain "options" into the
>> /etc/resolv.conf file.  That's a pity, because I wanted one in there.
>> (Oh well, I guss I can append it from my /etc/rc.local file.)
>Does
>chflags schg /etc/resolve.conf
>helps?

Humm... I confess that I hadn't even considered trying that.

Thanks for the suggestion!  I'll try that out.