#12654 HIGH Not Tri: Unexpected IP address change

[Zarro Boogs per Child]

#12654: Unexpected IP address change
--------------------------------+-------------------------------------------
           Reporter:  wad       |       Owner:  shep         
               Type:  defect    |      Status:  new          
           Priority:  high      |   Milestone:  Not Triaged  
          Component:  wireless  |     Version:  not specified
         Resolution:            |    Keywords:  XO-4 WLAN    
        Next_action:  diagnose  |    Verified:  0            
Deployment_affected:            |   Blockedby:               
           Blocking:            |  
--------------------------------+-------------------------------------------

Comment(by wad):

 OK, this means that the client (test laptop) responded to a ping at an
 address which didn't have a valid lease.  I suspect that what is going on
 is that the test laptop has lost too much time (due to being suspended
 most of the past hour), and still thinks the lease is valid.   The server,
 thinking that lease has expired, ping to check it before issuing it.  When
 the laptop responds to the ping, the server discards the address and
 assigns a new one.

 I can verify with an 8686 module in an hour --- it should have the same
 problem.   This is due to kernel time slippage.

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