XPost: comp.mobile.android, alt.os.linux, alt.comp.os.windows-10   
   From: nospam@nospam.invalid   
      
   In article ,   
   Whiskers  wrote:   
      
   > >> Setting his phone to use a static IP while connected to his home   
   > >> network, would be a good idea   
   > >   
   > > it's a horrible idea because he'd have to change it every time he   
   > > leaves the house and back again when he returns.   
   > >   
   > > that's a shitload of effort for absolutely no reason, since what he   
   > > claims to want can be done entirely automatically.   
   >   
   > I admit that my memory could be faulty, it being some months since   
   > setting up an Android device to access a WiFi access point it hadn't   
   > used before, but doesn't the setting up on the phone of a new access   
   > point give the user the choice between DHCP and static IP?   
      
   sure, but using static ip on a phone is a *really* bad idea because it   
   will be connecting to different networks as a matter of course. that   
   static ip isn't going to work across all of them and changing it each   
   time is crazy. it's virtually guaranteed that there will be a conflict   
   and that's really going to piss off the users of the other networks.   
      
   *if* you want an ip address to always be the same on a given network   
   (which in some cases is useful but not so much on a phone), then use   
   reserved dhcp.   
      
   reserved dhcp is sometimes called static dhcp, perhaps causing the   
   confusion. that's technically a contradiction, but it's not unusual to   
   see it called that.   
      
      
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)