#7785 HIGH 9.1.0: unreliable ethernet connection

[Zarro Boogs per Child]

#7785: unreliable ethernet connection
---------------------------------------+------------------------------------
           Reporter:  AlbertCahalan    |       Owner:  dcbw         
               Type:  defect           |      Status:  new          
           Priority:  high             |   Milestone:  9.1.0        
          Component:  network manager  |     Version:  not specified
         Resolution:                   |    Keywords:               
        Next_action:  never set        |    Verified:  0            
Deployment_affected:  8.2              |   Blockedby:               
           Blocking:                   |  
---------------------------------------+------------------------------------
Changes (by mikus):

 * cc: mikus (added)
  * owner:  => dcbw
  * component:  not assigned => network manager
  * deployment_affected:  => 8.2


Comment:

 I completely agree with everything Albert Cahalan said :

 I was testing with the 'staging-7' build.  Had XO connected via ethernet
 (its IP was 192.168.1.8).  Happened to click in Neighborhood view on an
 icon for an external radio signal (access point ?).  The icon I had
 clicked on pulsed for a while, never got white rim, then went back to
 static as it was before.

 A little later, I tried to use Browse, but it could not resolve the
 website IP addresses.  I investigated, and found that my ETHERNET adapter
 had now been assigned a (zeroconf?) IP address in the 192.254.x.x range
 (so had the mesh, which before only had an IPv6 address).

 After I rebooted, the XO had no problem again being given the 192.168.1.8
 address by the DHCP server on my ethernet.  I'm guessing that me clicking
 on the AP? caused my system to drop the ethernet connection -- but when
 after failing to create a wireless connection the system went back to
 using the ethernet adapter, it did so with an *internally* assigned IP
 address in the 196.254.x.x range.

 [In other words, I do not believe that the system even *tried* to re-
 contact my external DHCP server when it was trying to re-activate the
 ethernet connection.  There is __NO WAY__ for that 196.254.x.x address to
 have come from the server on the ethernet.  Also, the question has been
 asked before -- I am satisfied that my DHCP server is *quick* acting.]

 ----

 The system should remember which IP address the ethernet connection was
 using when that connection was "broken" (in this case, the "breaking" was
 done by the system itself !).  And if the system does not "remember" the
 former IP address, it ought to do as much DHCP dialoging on a "reconnect"
 as it does on a "reboot".

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