Date: Mon, 1 Nov 2004 03:57:31 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Rob <spamrefuse@yahoo.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: 5.3 + dhclient: bpf needed in kernel config? Message-ID: <20041101115731.GA23712@odin.ac.hmc.edu> In-Reply-To: <418622A2.30607@yahoo.com> References: <4186168C.1000900@yahoo.com> <20041101110418.GA20594@odin.ac.hmc.edu> <418622A2.30607@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 01, 2004 at 08:48:50PM +0900, Rob wrote: > 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. >=20 > Aha. So I added bpf to my kernel config, recompiled and > installed everything again. >=20 > Yesterday this PC has been upgraded from 4.10 to most > recent 5.3. I have in /etc/rc.conf >=20 > ifconfig_rl0=3D"DHCP" >=20 > which worked jsut fine with 4.10, but seems to misserably > fail with 5.3. >=20 > Dhclient binds rl0 to 192.168.1.22 all the time, which > seems to be a kind of default for a failing dhclient. >=20 > Is something else, unusual, needed in 5.3, that is critical > to dhclient? dhclient works with GENERIC and I believe all you need is bpf. There is no default address for dhclient so that's not your problem. Even if there were a default it would almost certaintly be in the Microsoft autoconfig address space which is not part of the 192.168/16 network. It is possiable you are using an unexpired prior lease in /var/db/dhclient.leases. I'd tend to suspect your dhcp server or a NIC driver bug. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBhiSqXY6L6fI4GtQRAmSUAJ9adwlkO4C4lJGC2i6VC1FbGOXM5gCgoFHp IPHWJwKa65DrkmVT7jTcB7I= =ugMR -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041101115731.GA23712>