I had lots of issues getting the ISC.org dhcpd to work properly. I switched
to the standard bootpd(slackware) daemon and things worked fine. I think
this may be just how I have the isc.org dhcpd.conf setup but the bootpd
daemon worked just fine out of the box.
Either the isc.org dhcpd sends things the SGIs aren't prepared to get or it
just not implementing bootpd the right way. I think it's just a config issue
but I've yet to get things right with the dhcpd.conf. You'll notice there
are 4 get requests in the log files before the SGI times out.
There is a post on the isc.org message boards about this. I don't have the
URL but I searched on SGI and bootp in the dhcpd client archives.
I'd suggest trying bootpd(rather thand dhcpd) and seeing if the SGI boots
right up. That worked for me after screwing around with dhcpd for a few
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com]On Behalf Of Philippe Chauvat
> Sent: Thursday, May 25, 2000 9:06 AM
> To: Linux Mips
> Subject: [DHCP]
> I'm trying to install Linux on an Indy Box. I need some help to boot
> from my Indy with bootp protocols.
> My configuration is:
> one Indy with Irix 6.2, nfs, dhcp and tftp server (I would like !) --->
> named _cream_ IP=192.0.2.2
> one Indy with Irix 5.2 ----> named _pancake_ IP=192.0.2.3
> one PC box with Mandrake 6.0 nfs, dhcp and tftp server ----> named
> _pie_ IP=192.0.2.1
> one HUB to connect everybody
> I followed instructions from different HowTo's but...
> 1/When I use _cream_ as dhcp server (/usr/sbin/dhcpd -f -d) and try to
> boot _pancake_ I receive a message something like
> BOOT... (not RFC1048)
> and then my _pancake_ does not boot.
> 2/ If I try to use _cream_ as dhcp server nothing appears
> So, I would like to ask a lot of things!
> -- can I use bootp from _pancake_ to boot on _cream_ or _pie_ ?
> -- how can I see some information about bootp connection on _cream_ from
> _pancake_ ?
> Thanks a lot for your help.
> P.S. _cream_, _pancake_ and _pie_ names are only as example.