XPost: comp.mobile.android, alt.os.linux, alt.comp.os.windows-10
From: catwheezel@operamail.com
On 2017-04-12, nospam wrote:
> In article ,
> Whiskers wrote:
>
>> >> >>> Google "address reservation". You don't want a fixed IP address
>> >> >>> on a phone.
>> >> >>
>> >> >> Not true, he does.
>> >> >
>> >> > he might think he does, but he doesn't.
>> >>
>> >> Your opinion noted.
>> >
>> > it's not an opinion. he should *not* have a fixed ip address on his
>> > phone. that is only going to cause a world of problems, especially
>> > since he doesn't understand what he's doing.
>> >
>> > what he wants is a reserved address, which is done at the router.
>>
>> 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? Each
internet connection has its own settings on the phone, each one only
needs to be set up once (as long as you et it correct). DHCP is
probably what you get if you don't try to change it. The settings on
the phone for one network should not (I'd even go as far as MUST NOT)
have any effect on the settings for any other network.
So there would be no need to change any settings each time he goes out
or comes back home. The phone will automatically connect with any
network it already knows about, if that's the way it has been set up.
[...]
--
-- ^^^^^^^^^^
-- Whiskers
-- ~~~~~~~~~~
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
