From owner-freebsd-current Mon Feb 8 22:39:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14687 for freebsd-current-outgoing; Mon, 8 Feb 1999 22:39:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14678 for ; Mon, 8 Feb 1999 22:39:30 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.8.8/8.8.8) id WAA08295; Mon, 8 Feb 1999 22:39:29 -0800 (PST) (envelope-from sef) Date: Mon, 8 Feb 1999 22:39:29 -0800 (PST) From: Sean Eric Fagan Message-Id: <199902090639.WAA08295@kithrup.com> To: current@FreeBSD.ORG Reply-To: current@FreeBSD.ORG Subject: Re: adding DHCP client to src/contrib/ In-Reply-To: <19990209082922.17759.qmail.kithrup.freebsd.current@rucus.ru.ac.za> References: <199902090553.VAA05212@kithrup.com> from Sean Eric Fagan at "Feb 8, 1999 9:53:11 pm" Organization: Kithrup Enterprises, Ltd. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990209082922.17759.qmail.kithrup.freebsd.current@rucus.ru.ac.za> you write: >- DHCP-WIDE requires you to have bpf configured into your kernel > for a GENERIC kernel, this is VERY BAD - is there a more elegant > way to handle this? I certainly would not like to see the > generic kernel in the distribution going out into the world with > bpf enabled. So does isc-dhcp. There's really no other way to do it: you need the ability to grab packets that come from an unidentified machine, which doesn't have an IP address. You could write some other method of doing this -- and then put it into every single ethernet (et al) device driver -- or you could just use BPF, which really isn't all that large. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message