XPost: comp.mobile.android, alt.os.linux, alt.comp.os.windows-10   
   From: cariadmenywod@gmail.com   
      
   In , Jeff Liebermann   
   suggested:   
      
   >>However ... this discussion has pointed out useful improvements:   
   >>A. I should reserve some addresses *outside* the range of the DHCP server.   
   >>B. I should use only those reserved addresses on the mobile devices.   
   >>C. And I should set *all* the home APs to that address (not just one AP).   
   >   
   > I'm not sure what you mean by "C".  Setting all the various AP's   
   > (access points) to the same IP address does absolutely nothing to the   
   > function of the AP.   
      
   It's my fault for not being clear.   
      
   While the "lease" seems to make all the difference in practical terms, by   
   default there is nothing (other than the continuingly re-extended lease) to   
   stop the router from assigning the IP address that is currently assigned to   
   the phone to some other device on the local network.   
      
   There are multiple ways to make the IP address remain at 192.168.1.15 on   
   the device, only one of which is done on the phone, and that one is done   
   "per access point" ... which was what "C" was all about.   
      
   Item "C" was really what this question was all about, because I was   
   wondering what "magic" enabled the mobile device to have a say in what its   
   IP address was going to be.   
      
   > Please note that most AP's do not have a DHCP *CLIENT* on the LAN   
   > side, and therefore cannot obtain a DHCP assigned IP address from your   
   > router.   
      
   The "magic" is how an Android mobile device can "ask" for a certain IP   
   address from the access point (e.g., 192.168.1.15).   
      
   A question might be what happens if that access point has already handed   
   out 192.168.1.5 to another device?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)