#7271 NORM Never A: NetworkManager-0.6 broken in olpc3

[Zarro Boogs per Child]

#7271: NetworkManager-0.6 broken in olpc3
------------------------------+---------------------------------------------
  Reporter:  dsd              |       Owner:  dcbw          
      Type:  defect           |      Status:  new           
  Priority:  normal           |   Milestone:  Never Assigned
 Component:  network manager  |     Version:  olpc-3        
Resolution:                   |    Keywords:                
  Verified:  0                |    Blocking:                
 Blockedby:                   |  
------------------------------+---------------------------------------------

Comment(by dsd):

 I set up two systems (one F7, one F9) to boot into text-only mode, without
 X/Sugar, and without NetworkManager. I then ran iwevent (logging the
 output) and then started NetworkManager. Both are running version
 0.6.5-0.8.svn3246

 The F7 system quickly settled on a mesh network (with school server) and
 obtained an address over DHCP. dhclient remained running as expected. eth0
 came up with an IPv6 address, msh0 came up with a 172.18.x.x address.
 /etc/resolv.conf was populated with search domain and nameserver.

 The F9 system jumped around networks for a few minutes, settled on the
 same mesh channel, but did not run dhclient. eth0 is down and has no
 addresses. msh0 is up but has IP address 169.254.x.x. /etc/resolv.conf is
 empty except for the "generated by networkmanager" comment.

 If I manually run dhclient on msh0 on the OLPC-3 system once it has
 settled on a network, connectivity is established.

 So the currently unexplained differences seem to be:
  - eth0 not coming up
  - network selection taking ages
  - dhclient not running on msh0

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