#7785 HIGH 9.1.0: unreliable ethernet connection

[Zarro Boogs per Child]

#7785: unreliable ethernet connection
-----------------------------+----------------------------------------------
   Reporter:  AlbertCahalan  |       Owner:               
       Type:  defect         |      Status:  new          
   Priority:  high           |   Milestone:  9.1.0        
  Component:  not assigned   |     Version:  not specified
 Resolution:                 |    Keywords:               
Next_action:  never set      |    Verified:  0            
  Blockedby:                 |    Blocking:               
-----------------------------+----------------------------------------------

Comment(by AlbertCahalan):

 Replying to [comment:6 pgf]:
 > without having looked at NM, i'm sure the problem is that if the laptop
 doesn't find or hear from a DHCP server on the ethernet within a certain
 (fairly short) time after coming up, then it falls back to doing link-
 local IP autoconfiguration (zeroconf).

 It can also happen later. Remember that a DHCP address lease has a
 timeout; clients try to renew the lease before it expires.

 > albert has been using the term "bogus", but the address isn't "bogus" --
 it's just not an address that's useful in most cases.  (a typical Windows
 pc will choose the exact same sort of address in this circumstance.)

 AFAIK, a Windows PC with a zeroconf address will keep looking for DHCP. In
 any case, that is the useful behavior.

 > if there's a trivial change to the NM configuration that would keep it
 from falling back to zeroconf addressing in the absence of DHCP (for
 ethernet only, of course), then we should make that change.

 This would solve the problems I suppose.

 Zeroconf addresses probably should be chosen by the DHCP client daemon,
 not the NM daemon.

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