XPost: comp.mobile.android, alt.os.linux, alt.comp.os.windows-10   
   From: cl@isbd.net   
      
   nospam  wrote:   
   > In article , tlvp   
   >  wrote:   
   >   
   > >   
   > > > How does setting a static IP on a linux Android mobile device prevent the   
   > > > linux router from assigning that IP address to another device?   
   > >   
   > > Each of the very few routers I've ever used has its 192.168.a.* address   
   > > range split into two halves: a lower range ( * running roughly 1-100) which   
   > > are treated as *fixed* addresses, *not* dynamically assignable; and an   
   > > upper range ( * roughly 101-253), dynamically assignable addresses. Here   
   > > the value "a" is either 0 or 1, depending on the router model/maker, and is   
   > > not variable.   
   >   
   > maybe by default it's that way, but you can change the dhcp range to   
   > start/stop at whatever you want as well as the ip block.   
   >   
   > > It is *I* who can assign static addresses, from among the addresses in the   
   > > lower range; and it is the router who assigns the dynamic addresses, from   
   > > among the addresses in the upper range.   
   >   
   > you can assign static addresses to whatever you want, inside or outside   
   > of any range in the router.   
   >   
   > > Addresses 192.168.a.254 and 192.168.a.255 are *not* assignable, not by me,   
   > > not by the router, as they play a fixed role already, as does 192.168.a.0 .   
   >   
   > 254 is.   
      
   254 is often the default router IP, they're usually either 192.168.1.1   
   or (less often) 192.168.1.254 if using the 192.168.1 block.   
      
   --   
   Chris Green   
   ·   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)