Date: Thu, 22 Jul 1999 17:29:47 +0800 From: Peter Wemm <peter@netplex.com.au> To: Luigi Rizzo <luigi@labinfo.iet.unipi.it> Cc: jkh@FreeBSD.org (Jordan K. Hubbard), cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/release/sysinstall tcpip.c Message-ID: <19990722092947.081221C9E@overcee.netplex.com.au> In-Reply-To: Your message of "Thu, 22 Jul 1999 08:39:15 %2B0200." <199907220639.IAA25913@labinfo.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Luigi Rizzo wrote:
> > The ultimate answer here is to make either bpf a loadable kernel module
> > (which security conscious admins will be able to simply remove from /modu
les)
> > or come up with a lighter weight mechanism just for dhcp and other apps t
hat
> > need to see broadcast packets but not otherwise sniff the wire in full
> > bpf glory.
>
> can you briefly summarise your (i.e. dhcp's) needs ? I am curious
> why bootpd works without bpf...
Because bootp only requires the packets be broadcast and can have addresses
like: 172.12.255.255. However, DHCP requires the packets have addresses
of 255.255.255.255, and certain (ie: windows) implementations are rather
pedantic about it and won't accept the packets if they do not have the
addresses as all 255's.
Linux can do it, and our stack can *almost* do it. For this to work I
think we need to be able to send and recieve broadcast UDP packets to
255.255.255.255 from an "up" interface without an ip address.
Cheers,
-Peter
--
Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990722092947.081221C9E>