XPost: comp.mobile.android, alt.os.linux, alt.comp.os.windows-10   
   From: dan@djph.net   
      
   Stephen wrote:   
   >[...]   
   > FWIW most home routers seem pretty brain dead for the optional   
   > subtleties in the DHCP server standards - several types i have used   
   > will merrily hand out the same IP address that is in use by a device   
   > after a reboot.   
      
   Do you mean it'll hand out a previously-assigned address to a different   
   computer, or that it hands out the same IP address to a the same device   
   after the router is rebooted?   
      
   If the former, yeah, that's a problem due to the leases file being wiped   
   out.  More an artifact of non-persistent storage than anything -   
   typically, I've only seen this kind of behavior in cheap SOHO routers   
   though.   
      
   If the latter, that's how DHCP is supposed to work.  Both sides keep a   
   record of how long the lease lasts for.  The DHCP server's record   
   includes the client's MAC address; and as long as the client requests   
   the IP be refreshed before the expiration date/time, the client will   
   receive the same IP address.   
      
   Typically the client refreshes the IP at the lease half-life (for   
   example, every 12 hours on a 24-hour DHCP Lease).   
      
   --   
   |_|O|_| Registered Linux user #585947   
   |_|_|O| Github: https://github.com/dpurgert   
   |O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)