#10541 NORM Not Tri: XO-1.5 os852 USB ethernet RFC3927 IP address not assigned

[Zarro Boogs per Child]

#10541: XO-1.5 os852 USB ethernet RFC3927 IP address not assigned
------------------------------------+---------------------------------------
           Reporter:  Quozl         |       Owner:               
               Type:  defect        |      Status:  new          
           Priority:  normal        |   Milestone:  Not Triaged  
          Component:  not assigned  |     Version:  not specified
         Resolution:                |    Keywords:               
        Next_action:  never set     |    Verified:  0            
Deployment_affected:                |   Blockedby:               
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by mikus):

 I believe this is the correct ("as designed") architectural behavior.

 In three years of using physical ethernet connectivity for XOs, my
 experience has been that when an ethernet cable (with adapter) gets
 plugged in to the XO, the XO attempts to contact a DHCP server (presumed
 to exist somewhere at the other end of that cable).  If this attempt is
 successful, it is that DHCP server which assigns an IP address to the
 "joining" XO.  If this attempt to contact a DHCP server is unsuccessful,
 it is up to the "joining" XO to set its own IP address (e.g., by invoking
 zeroconf).

 [Whether there has been a regression (between 10.1 and 8.2) regarding
 ethernet self-assignment of IP address I haven't noticed -- on my LAN I
 always explicitly set the ethernet IPv4 address if a system has failed to
 connect because it doesn't have the proper IP address.]

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