netboot-0.8.1 does not receive bootImage

[Christopher Ronnewinkel <ronne@neuroinformatik.ruhr-uni-bochum.de>]

Hi everybody,

I'm trying to set up a discless client with netboot-0.8.1.
It seems to me that the client does not receive the bootImage.
I tested the permissions of in.tftpd and the bootImage of course. With
help of tcpdchk and tcpdmatch I checked that permission is granted to the
client to use tftp.
The boot process looks from /var/log/messages of the server (dortmund):

Apr 21 15:01:17 dortmund bootpd[13409]: recvd pkt from IP addr 0.0.0.0
Apr 21 15:01:17 dortmund bootpd[13409]: bootptab mtime: Tue Apr 20 19:42:10 1999
Apr 21 15:01:17 dortmund bootpd[13409]: request from Ethernet address 00:00:E8:DF:7F:AB
Apr 21 15:01:17 dortmund bootpd[13409]: found 134.147.254.107 (bologna)
Apr 21 15:01:17 dortmund bootpd[13409]: bootfile="/netboot/bootImage-bologna"
Apr 21 15:01:17 dortmund bootpd[13409]: vendor magic field is 99.130.83.99
Apr 21 15:01:17 dortmund bootpd[13409]: sending reply (with RFC1048 options)
Apr 21 15:01:17 dortmund bootpd[13409]: setarp 134.147.254.107 - 00:00:E8:DF:7F:AB

On the clients (bologna) console, I get:

-snip---------------------------------------------------------------------

Boot-ROM v0.8.1

BOOTP: Sending request (press ESC to abort): ok

Local IP: ...
Server IP: ... (dortmund)
File name: /netboot/...

Cannot load boot block from disk
Insert boot disk and press a key

########Debug Information######

S 0000E8DF7FAB 4500 0148 0001 0000 FF11 BAA4 0000 0000 FFFF FFFF 0044
R 0000E8DF7FAB 4500 0148 4773 0000 4011 286F 8693 FE30 8693 FE6B 0043
R 0000E8DF7FAB 4500 0148 4774 0000 4011 286E 8693 FE30 8693 FE6B 0043

-snap----------------------------------------------------------------------

So, why does the server not send the bootImage after "setarp"?
There is no "tftpd" message at all.
I checked in /proc/net/arp that the arp-entry is correct.

The network card is a Accton 1208TC (an NE2000 clone).
I also downloaded a packet driver for this card from Accton, and rebuilt
the boot-disk, but the problem remains.
So, it is not a mismatched packet driver.

What do I miss out?
What do the debug-lines mean??


Thanks,
Christopher

 




===========================================================================
This Mail was sent to netboot mailing list by:
Christopher Ronnewinkel <ronne@neuroinformatik.ruhr-uni-bochum.de>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.