#4152 NORM MP Star: 'boot net' fails

[Zarro Boogs per Child]

#4152: 'boot net' fails
----------------------------------+-----------------------------------------
  Reporter:  dwmw2                |       Owner:  wmb at firmworks.com
      Type:  defect               |      Status:  reopened         
  Priority:  normal               |   Milestone:  MP Start         
 Component:  ofw - open firmware  |     Version:                   
Resolution:                       |    Keywords:                   
  Verified:  0                    |    Blocking:                   
 Blockedby:                       |  
----------------------------------+-----------------------------------------

Comment(by Blaketh):

 Hi,

 I use the following command:
 {{{
 ok debug-net " http://172.18.0.1/fs.zip" open-dev
          or
 ok debug-net try-fs-update
 }}}

 OFW asks for two DHCP leases and must receive both in order to succeed.
 The first it requests from 255.255.255.255, the second from 172.18.0.255.
 One of my DHCP servers doesn't respond to requests directed at
 172.18.0.255.  This DHCP server is clearly broken.  It would be nice,
 though, if OFW didn't ask for the second lease.  Then it would work even
 with my broken server.

 Is there an easier way to get OFW's output into this ticket than for me to
 hook up a serial adapter?  NS: seems to mean Name Server.

 I've been trying to figure out a way to leave the FILE section of the DHCP
 packet blank but I don't know enough about Open Firmware to do so.   I
 tried:

 {{{
 ok debug open
 open ?
 ok dev /http
 ok debug open
 Stepper keys: <space> Down Up Continue Forth Go Help ? See $tring Quit
 ok select http
 Scan for: OLPCOFW found
 Associate with: OLPCOFW
 }}}

 and it didn't break on open.  I am clearly doing something wrong.

 Differences between a working and a non-working DHCP request packet:

 {{{
 17:35:00.379940
 IP (tos 0x0, ttl 123, id 1,
  offset 0, flags [none], proto: UDP (17), length: 576) 0.0.0.0.68 >
 255.255.255.255.67:
 [no cksum] BOOTP/DHCP, Request from 00:17:c4:03:56:c3 (oui Unknown),
 length: 548,
 xid:0xc403301f, flags: [none] (0x0000)
           Client Ethernet Address: 00:17:c4:03:56:c3 (oui Unknown)
 +         file "OLPC"
           Vendor-rfc1048:
             DHCP:DISCOVER
             VC:"OLPC"
         0x0000:  ffff ffff ffff 0017 c403 56c3 0800 4500
 //Broadcast address changes from 255.255.255.255 to 172.18.0.255
 //The packet id changes from 1 to 5, that's ok, 3dad->9097 is differing
 // IP header checksum, that's ok too.
 -       0x0010:  0240 0001 0000 7b11 3dad 0000 0000 ffff
 +       0x0010:  0240 0005 0000 7b11 9097 0000 0000 ac12
 // From nulls to the characters OLPC.  This is the boot file
 // area of the DHCP packet.
 -       0x0090:  0000 0000 0000 0000 0000 0000 0000 0000
 +       0x0090:  0000 0000 0000 4f4c 5043 0000 0000 0000
 }}}

-- 
Ticket URL: <http://dev.laptop.org/ticket/4152#comment:10>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system