From owner-freebsd-security Wed Sep 15 20:21:54 1999 Delivered-To: freebsd-security@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id CD8C414DC6 for ; Wed, 15 Sep 1999 20:21:50 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Thu, 16 Sep 1999 13:19:34 +1000 Date: Thu, 16 Sep 1999 13:21:41 +1000 From: Peter Jeremy Subject: Re: BPF on in 3.3-RC GENERIC kernel In-reply-to: <4.2.0.58.19990915201332.048da870@localhost> To: brett@lariat.org Cc: freebsd-security@FreeBSD.ORG Message-Id: <99Sep16.131934est.40325@border.alcanet.com.au> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brett Glass wrote: > Why is DHCP handled through BPF? Please go and read the archives, where this is discussed in detail. Briefly, a DHCP client needs to be able to both send and receive IP packets before its interface has an IP address. Using the standard 4.4BSD IP stack, the only way a user process (the DHCP client) can receive IP packets is using BPF. I believe Linux has some hooks in its IP stack to work around this. Feel free to provide patches to add a similar facility to the FreeBSD IP stack. >Which leads to the idea of a kernel config option, similar to the one >that lets you set flags for syscons. Feel free to supply patches. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message