More information (with stc instruction instead of callpkt after setmd5): It's definitely getting farther, the network trace shows some packets: No. Time Source Destination Protocol Info 1 0.000000 u06.bwc.ats.ucla.edu ff:ff:ff:ff:ff:ff ARP Who has 128.97.60.207? Tell 128.97.60.205 2 0.000030 s02.bwc.ats.ucla.edu u06.bwc.ats.ucla.edu ARP 128.97.60.207 is at 00:90:27:10:06:59 3 0.000909 u06.bwc.ats.ucla.edu s02.bwc.ats.ucla.edu TFTP Read Request, File: pxelinux.0, Transfer type: octet 4 0.016652 s02.bwc.ats.ucla.edu u06.bwc.ats.ucla.edu TFTP Option Acknowledgement 5 0.016798 u06.bwc.ats.ucla.edu s02.bwc.ats.ucla.edu TFTP Acknowledgement, Block: 0 6 0.017126 s02.bwc.ats.ucla.edu u06.bwc.ats.ucla.edu TFTP Data Packet, Block: 1 7 0.019360 u06.bwc.ats.ucla.edu s02.bwc.ats.ucla.edu TFTP Acknowledgement, Block: 1 8 0.019505 s02.bwc.ats.ucla.edu u06.bwc.ats.ucla.edu TFTP Data Packet, Block: 2 9 0.019944 u06.bwc.ats.ucla.edu s02.bwc.ats.ucla.edu TFTP Acknowledgement, Block: 2 10 0.019980 u06.bwc.ats.ucla.edu s02.bwc.ats.ucla.edu TFTP Error Code, Code: Disk full or allocation exceeded, Message: 11 0.020057 s02.bwc.ats.ucla.edu u06.bwc.ats.ucla.edu TFTP Data Packet, Block: 3 That "Disk full or allocation exceeded" error sent by the netboot machine is strange. It's right after netboot has ACK'ed TFTP block 2. (Or is this normal that netboot ACK's the block and then finds out it doesn't have any place to put it?). Here's the detail on the error packet: Frame 10 (60 on wire, 60 captured) Arrival Time: Jun 7, 2002 12:09:59.324981000 Time delta from previous packet: 0.000036000 seconds Time relative to first packet: 0.019980000 seconds Frame Number: 10 Packet Length: 60 bytes Capture Length: 60 bytes Ethernet II Destination: 00:90:27:10:06:59 (s02.bwc.ats.ucla.edu) Source: 00:90:27:a9:2e:19 (u06.bwc.ats.ucla.edu) Type: IP (0x0800) Trailer: 00000000000000000000000000 Internet Protocol, Src Addr: u06.bwc.ats.ucla.edu (128.97.60.205), Dst Addr: s02.bwc.ats.ucla.edu (128.97.60.207) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 33 Identification: 0x0006 Flags: 0x00 .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 255 Protocol: UDP (0x11) Header checksum: 0x4167 (correct) Source: u06.bwc.ats.ucla.edu (128.97.60.205) Destination: s02.bwc.ats.ucla.edu (128.97.60.207) User Datagram Protocol, Src Port: 1071 (1071), Dst Port: 1030 (1030) Source port: 1071 (1071) Destination port: 1030 (1030) Length: 13 Checksum: 0x7d38 (correct) Trivial File Transfer Protocol Opcode: Error Code (5) Error code: Disk full or allocation exceeded (3) Error message: How is netboot usually debugged? Is there some way of running it under a debugger? (Or under some system?) Any suggestions? =========================================================================== This Mail was sent to netboot mailing list by: Michael Stein <mas@ucla.edu> 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.
For requests or suggestions regarding this mailing list archive please write to netboot@gkminix.han.de.