Yes, the server gets a DHCPREQUEST response to its DHCPOFFER. I took the ethereal advice and found that not only is DHCP working, but TFTP is working as well. I noticed it was loading the nbi.img image (sucessfully), so I switched it to pxelinux.0 and got a different response. The client starts to load the pxelinux.0 image, gets to block 2, and then resets, asks for an address via DHCP again, and starts trying to download the image again until it gets to block 2. It will keep going in this loop forever unless I stop it. When it loads the nbi.img file, it doesn't have the looping problem.
I have included the output from ethereal below hoping that it will shed some light on the situation.
I'm a little puzzled. Should I try another version of Etherboot? I'm using version 5.2.6.
Thanks,
Jeremy
No. Time Source Destination Protocol Info 1 0.000000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe16c0e9 2 0.028507 Cisco-Li_0b:4f:e7 Broadcast ARP Who has 192.168.0.247? Tell 192.168.0.1 3 0.704732 192.168.0.1 192.168.0.247 DHCP DHCP Offer - Transaction ID 0xe16c0e9 4 0.705118 192.168.0.247 255.255.255.255 DHCP DHCP Request - Transaction ID 0xe16c0e9 5 0.737300 192.168.0.1 192.168.0.247 DHCP DHCP ACK - Transaction ID 0xe16c0e9 6 0.737626 Ncr_16:c0:5e Broadcast ARP Who has 192.168.0.1? Tell 192.168.0.247 7 0.737660 192.168.0.1 192.168.0.247 ICMP Echo (ping) request 8 0.737669 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP 192.168.0.1 is at 00:18:f8:0b:4f:e7 9 0.737757 192.168.0.247 192.168.0.1 TFTP Read Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, blksize=1432 10 0.739513 192.168.0.1 192.168.0.247 TFTP Option Acknowledgement, blksize=1432 11 0.739640 192.168.0.247 192.168.0.1 TFTP Acknowledgement, Block: 0 12 0.739770 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 1 13 0.740292 192.168.0.247 192.168.0.1 TFTP Acknowledgement, Block: 1 14 0.740343 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 15 1.740598 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 16 3.776443 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 17 5.736343 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 18 6.736318 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 19 7.736294 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 20 7.812340 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 21 7.981137 192.168.0.247 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe16c176 22 7.981593 192.168.0.1 192.168.0.247 DHCP DHCP Offer - Transaction ID 0xe16c176 23 7.981976 192.168.0.247 255.255.255.255 DHCP DHCP Request - Transaction ID 0xe16c176 24 7.985617 192.168.0.1 192.168.0.247 DHCP DHCP ACK - Transaction ID 0xe16c176 25 7.985927 Ncr_16:c0:5e Broadcast ARP Who has 192.168.0.1? Tell 192.168.0.247 26 7.985959 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP 192.168.0.1 is at 00:18:f8:0b:4f:e7 27 7.986042 192.168.0.247 192.168.0.1 TFTP Read Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, blksize=1432 28 7.987704 192.168.0.1 192.168.0.247 TFTP Option Acknowledgement, blksize=1432 29 7.987824 192.168.0.247 192.168.0.1 TFTP Acknowledgement, Block: 0 30 7.987947 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 1 31 7.988477 192.168.0.247 192.168.0.1 TFTP Acknowledgement, Block: 1 32 7.988554 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 33 8.988357 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 34 11.024306 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 35 12.988160 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 36 13.988134 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 37 14.988108 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 38 15.060153 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 39 15.226659 192.168.0.247 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe16c1f6
...and so on and so on
On Feb 1, 2008 10:43 PM, ron minnich rminnich@gmail.com wrote:
On Feb 1, 2008 2:42 PM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 01.02.2008 23:05, Jeremy Wright wrote:
Can Etherboot load a secondary payload like that?
Sure. I've loaded filo and etherboot with etherboot.
ron