From owner-freebsd-current@FreeBSD.ORG Mon Nov 1 11:48:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87F7016A4CE for ; Mon, 1 Nov 2004 11:48:52 +0000 (GMT) Received: from auk1.snu.ac.kr (auk1.snu.ac.kr [147.46.100.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 278D643D48 for ; Mon, 1 Nov 2004 11:48:52 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.44.181] (spamrefuse@yahoo.com) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004110120:48:35:584228.3775.2901175216 for ; Mon, 01 Nov 2004 20:48:35 +0900 (KST) Message-ID: <418622A2.30607@yahoo.com> Date: Mon, 01 Nov 2004 20:48:50 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041017 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current References: <4186168C.1000900@yahoo.com> <20041101110418.GA20594@odin.ac.hmc.edu> In-Reply-To: <20041101110418.GA20594@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: NO (SR:0.97) (by Terrace) Subject: Re: 5.3 + dhclient: bpf needed in kernel config? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 11:48:52 -0000 Brooks Davis wrote: > On Mon, Nov 01, 2004 at 07:57:16PM +0900, Rob wrote: > >>I have left out bpf in the kernel config and >>all of a sudden dhclient (for DHCP) exits with an >>error message, complaining that bpf is not there? >> >>Since when (and why) is bpf needed by /sbin/dhclient? > > > bpf has always been required to run dhclient. We'd love to see that > requirement go away, but we need to modify he network stack to allow > programs to bind to an interface with a 0.0.0.0 address and no one has > done so yet. Aha. So I added bpf to my kernel config, recompiled and installed everything again. Yesterday this PC has been upgraded from 4.10 to most recent 5.3. I have in /etc/rc.conf ifconfig_rl0="DHCP" which worked jsut fine with 4.10, but seems to misserably fail with 5.3. Dhclient binds rl0 to 192.168.1.22 all the time, which seems to be a kind of default for a failing dhclient. Is something else, unusual, needed in 5.3, that is critical to dhclient? Rob.