Sounds like it's using RARP first to translate it's MAC into an IP
address, then hitting the bootp server secondly - already knowing it's IP
address - and just requesting info on the server/file to actually boot
strap itself. Sun boxes work that way. You need to add a static arp
entry for them if they netboot. Otherwise, after about 10 - 15 minutes or
so when other boxes on the net start flushing their arp caches, your
J. Scott Kasten
Email: jsk AT tetracon-eng DOT net
"The only future you have is the one
you choose to make for yourself..."
On Tue, 30 May 2000, Richard van den Berg wrote:
> On Tue, 30 May 2000, Jan-Benedict Glaw wrote:
> > I've now build a kernel which I would like to test on my Indigo;) The
> > problem is that I can't load it;( I tried bootpd as well as ISC dhcpd.
> > The result is actually just the same:
> > >> bootp()parkautomat:/tftpboot/vmlinux.ip12
> > No server for parkautomat:/tftpboot/vmlinux.ip12
> Just after doing this, does the machine show in the server arp table with
> `arp -a`? If so forget this mail, if not issue (of course with the right
> addresses) `arp -s 192.168.1.15 08:00:2B:2D:90:C0`
> DECstation <-> bootp has following quirk: power it on and let
> automatically boot and all goes well. Power it on and leave for a while (a
> quarter of an hour) at the PROM-console and then booting, forget it unless
> I use the arp -s command...