#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 wmb at firmworks.com):

 Observations:

 a) If 172.18.0.1 is a router, then the fact that it is returning its own
 address (172.18.0.1) in the NS: field could be a problem.  I assume that
 "NS:" is tcpdump's abbreviation for "next server".  Next-server is
 supposed to report that IP address of a TFTP server that can supply a boot
 file.  Routers usually don't have the role of TFTP server.

 b) The trace is missing some important packets, specifically the "OFFER"
 and "ACK" packets from Sonipes.  Lacking those packets, I can't discern
 the value of "next-server" that Sonipes reports.

 c) The DCHP negotiation step seems to have succeeded, as evidence by "arp
 reply 172.18.0.235 is-at 00:17:c4:0d:12:f2".  That shows that the client
 accepted that offered IP address.  But it might not proceed with the next
 step (or might appear not to proceed) if was given a bad "next-server"
 address and therefore could not contact a TFTP server.

 d) The exact firmware command that was used would be useful.  It would be
 especially useful to have the output that results from typing "debug-net"
 prior to running the network access command.  "debug-net" makes the
 firmware network stack verbose.

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