Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!ig!jade!ucbvax!UDEL.EDU!mminnich
From: mminnich@UDEL.EDU (Mike Minnich)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: bootp/rarp
Message-ID: <8801141129.aa10056@Huey.UDEL.EDU>
Date: 14 Jan 88 16:28:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17

> I'm not sure if 4.2 really accepted
> 0.0.0.0 as a broadcast address, or only net.0, and I no longer have
> virgin 4.2 sources around to check it.  

Robert,

Last I tried using 0.0.0.0 as a BOOTP broadcast address in a 4.2
environment, most if not all of our  Unix UDP servers went belly-up,
into some kind of tight loop.  Since at the time I was interested in
making BOOTP work, I decided to use a hard-wired (non-broadcast) IP
address and wait for 4.3 to resolve the broadcast problem.

Hope this helps.  

mike

PS - I didn't try net.0, but I would strongly suspect that it would work.