From owner-freebsd-current@FreeBSD.ORG Mon Nov 1 19:34:42 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 7ADF516A4CE for ; Mon, 1 Nov 2004 19:34:42 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 230F743D49 for ; Mon, 1 Nov 2004 19:34:42 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iA1JXub7088188; Mon, 1 Nov 2004 14:33:56 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iA1JXuIG088185; Mon, 1 Nov 2004 19:33:56 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 1 Nov 2004 19:33:56 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Rob In-Reply-To: <418622A2.30607@yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current 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 19:34:42 -0000 On Mon, 1 Nov 2004, Rob wrote: > 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? Other than BPF and, of course, INET, I don't know of specific other dependencies. I would suggest hooking up tcpdump to the interface before running dhclient, and using a command something like the following: tcpdump -p -i rl0 udp port dhcpc or udp port dhcps & And see what packets go out while dhclient runs. BTW, dhclient gets somewhat confused if run more than once, so I might do a "killall dhclient" before experimenting to be on the safe side. If it was upgraded, you might try deleting the old leases database (/var/db/dhclient.leases). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research