Ok. I've had about 4 replys so far about other people having issues with the
isc.org dhcpd daemon...

I've had great luck using it for other projects so AFAIK this is just an
issue with the way SGI does bootp. Perhaps we can find a workaround for the
ISC dhcpd.

I'll put a sniffer on the wire and watch a bootpd-->SGI exchange vs. a
dhcpd-->SGI exchange and see what's missing.

In the mean time can we get something posted to the FAQ or howto so that
other people don't sufer the same fate?

Thanks!

-----Original Message-----
From: owner-linux@cthulhu.engr.sgi.com
[mailto:owner-linux@cthulhu.engr.sgi.com]On Behalf Of Keith M Wesolowski
Sent: Thursday, May 25, 2000 9:48 AM
To: Eric Watkins
Cc: Philippe Chauvat; Linux Mips
Subject: Re: [DHCP]


On Thu, May 25, 2000 at 09:26:35AM -0700, Eric Watkins wrote:

quoted

Either the isc.org dhcpd sends things the SGIs aren't prepared

to get or it

quoted

just not implementing bootpd the right way. I think it's just a

config issue

quoted

but I've yet to get things right with the dhcpd.conf. You'll

notice there

quoted

are 4 get requests in the log files before the SGI times out.

I also had difficulty using ISC dhcpd to boot SGIs until I did an
unsetenv netaddr before booting. I don't yet know why this works.

--
Keith M Wesolowski			wesolows@chem.unr.edu
University of Nevada			http://www.chem.unr.edu
Chemistry Department Systems and Network Administrator