How does setting a static IP on a mobile device prevent linux router from assigning that IP address?

nospam wrote:
In article , Carlos E.R.
wrote:

You have a device that allows settings for one access point to influence
the settings for any or all other access points? It's faulty.

while it 'can' do that, it's not needed. setting a different
configuration for every ssid is not only nuts, but it's asking for
problems.

However, that is exactly what Android does. And Windows. And Linux. Each
SSID gets its own independent configuration.

strange how leaving it at its default (dhcp) works on any ssid without
any need for independent configs.

Ever heard of keys/passwords?

On 2017-04-14 19:41, Frank Slootweg wrote:
nospam wrote:
In article , Carlos E.R.
wrote:

You have a device that allows settings for one access point to influence
the settings for any or all other access points? It's faulty.

while it 'can' do that, it's not needed. setting a different
configuration for every ssid is not only nuts, but it's asking for
problems.

However, that is exactly what Android does. And Windows. And Linux. Each
SSID gets its own independent configuration.

strange how leaving it at its default (dhcp) works on any ssid without
any need for independent configs.

Ever heard of keys/passwords?

Indeed. Each SSID gets its own independent configuration in every system
I know, and that includes of course setting up the different password
for each SSID.

--
Cheers, Carlos.

nospam wrote:
In article , Frank Slootweg
wrote:

[1] Not to mention that most users wouldn't know what the fsck that
*is*, let alone install and configure one.

and yet they'll know how to configure a static ip?

Yes, because the IP in question is reported by the FTP server when you
start it and it can be configured in the router.

OTOH, your imaginary DNS server is blissfully absent in the described
set up, so it *can* not even be set up.

nothing imaginary about it and is likely already active, so nothing to
set up.

As usual no specifics, so you claim can't be verified, so it's false
until proven (by you) otherwise.

Also you've not catered for - and silentlu snipped - the specified
context (Android device, Windows computer and a simple consumer-type
(NAT) router).

QED.

HTH. HAND. EOD. NK.

you're well over your head, again.

On 2017-04-14 18:35, Tomos Davies wrote:
In , Carlos E.R. suggested:



One open question I have is what happens under the current circumstances
when the Android device requests an IP address of 192.168.1.15 of the
access point ... if ... if the access point has already handed out that IP
address to another device?

Notice that in your configuration your device does not request an IP. It
just uses that IP straight away, no matter if it has been given by DHCP
to another machine by chance. What happens? Collisions. None works.

Notice also that the AP does not hand out addresses. That's the job of
the router.

--
Cheers, Carlos.

On Fri, 14 Apr 2017 16:35:16 -0000 (UTC), Tomos Davies
wrote:

I agree with all of you that it's more elegant to assigned a fixed IP at
the DHCP configuration of the access point.

One open question I have is what happens under the current circumstances
when the Android device requests an IP address of 192.168.1.15 of the
access point ... if ... if the access point has already handed out that IP
address to another device?

I'm jumping in here without having read the whole thread, but I want
to comment on your "open" question:

Devices do NOT request a certain IP address. They can be set to DHCP
and request an IP address OR they can be set to a static IP. If DHCP,
they get whatever the router/AP decides to give them. That could
change every time they join the network or (more likely) end up being
the same each time unless that address has been handed out to another
device. It is often the same each time because the router/AP sees the
MAC address of the device and tried to give it the same IP address it
gave it the last time it saw that MAC. Newer routers often have a
feature which consistently does that called "reserving an IP address".
If you set your device to a static IP, that's what it is. The
router/AP has nothing to do with it. Nothing is requested. Nothing
is provided. If you select a static IP that is the same address your
router/AP assigned to another device, you end up with two devices
using the same IP address and your network will become very erratic.
If you want or need a static IP, learn what range of addresses your
router/AP hands out and pick something outside that range. For
example, if your router/AP's DHCP service assigns addresses from
192.168.1.101 to 192.168.1.150, then pick something like 192.168.1.151
as your static IP. However, if your router/AP is new enough to have
"reservations", just use DHCP on your device and then set the router
to reserve that particular IP address for your device. Your device
then effectively has a static IP whenever it is connected to YOUR
router/AP but acts normally (ie, requests an address via DHCP) on any
other router/AP it encounters. I hope that helps.

On 2017-04-14 15:52, nospam wrote:
In article , Carlos E.R.
wrote:

When I say I need a "static IP" (address) for my device and I have (at
least) my device (which happens to be an Android device) and a (NAT)
router, then:

- What do I mean (by "I need a "static IP" for my device")?

I won't question why you need a static IP address for your device.
Well, maybe I will a little.
...
Things like phones,
tablets, game boxes, gizmos, laptops, PC's, media players, etc work
nicely with DHCP assigned addresses.

Well, you have missed some information. There is some in the first post
of the thread, and more on the previous thread (I don't remember if it
was crosposted to the same groups), and then repeated again on some
other posts in this thread.

The OP is running a small FTP server on his phone, when needed, and
accesses it from his computer. Obviously having the device on the same
IP every day avoids having to find the IP of the day.

as has been explained, that does not require a static ip.

As has been explained, it does.

--
Cheers, Carlos.

On Fri, 14 Apr 2017 20:00:02 +0200, "Carlos E.R."
wrote:



as has been explained, that does not require a static ip.

As has been explained, it does.

If your have a router that has the "reservations" feature, your get
the advantages of a static IP without setting your device to a static
IP. That's what they mean by "that does not require a static IP". The
OP wants an IP that never changes. You can get that without setting
your device to a static IP.

On 2017-04-14 19:58, Frank Slootweg wrote:
nospam wrote:
In article , Frank Slootweg
wrote:

[1] Not to mention that most users wouldn't know what the fsck that
*is*, let alone install and configure one.

and yet they'll know how to configure a static ip?

Yes, because the IP in question is reported by the FTP server when you
start it and it can be configured in the router.

OTOH, your imaginary DNS server is blissfully absent in the described
set up, so it *can* not even be set up.

nothing imaginary about it and is likely already active, so nothing to
set up.

As usual no specifics, so you claim can't be verified, so it's false
until proven (by you) otherwise.

Also you've not catered for - and silentlu snipped - the specified
context (Android device, Windows computer and a simple consumer-type
(NAT) router).

Apparently he is lucky to have a router where you can assign names to
the reservations, so he thinks we all have.

http://cache-www.linksys.com/support...-007_EN_v8.png

Assuming that is a DNS name and not a BIOS name.


--
Cheers, Carlos.

On 2017-04-14 14:37, Dan Purgert wrote:
Carlos E.R. wrote:
On 2017-04-13 23:58, Dan Purgert wrote:


Well, not so small a chance, it happened to you :-P

Yeah, once over the course of $family and $friend each being AT&T
customers for decades (and having several router upgrades in between).


If they have such a large customer list, they should use longer SSIDs. I
suppose it is a prefix then a decimal or hex number. They just need more
digits. :-)

The default SSID was something like 2WIRE_1a2b3c4d5e6f (the hex at the
tail end changes -- definitely not the device MAC addresses, but some
psuedo-random number)

Not a short number, though. Seems quite long for a repeat. :-?

--
Cheers, Carlos.

On 2017-04-14 20:08, Pat wrote:
On Fri, 14 Apr 2017 20:00:02 +0200, "Carlos E.R."
wrote:



as has been explained, that does not require a static ip.

As has been explained, it does.

If your have a router that has the "reservations" feature, your get
the advantages of a static IP without setting your device to a static
IP. That's what they mean by "that does not require a static IP". The
OP wants an IP that never changes. You can get that without setting
your device to a static IP.

No, this chap thinks that all home/ISP routers have a DNS server
matching the DHCP server, so that the phone gets automatically the same
name, and that you can contact it by such name, without giving it a
fixed or dynamic but reserved IP.

--
Cheers, Carlos.

In article , Frank Slootweg
wrote:

You have a device that allows settings for one access point to
influence
the settings for any or all other access points? It's faulty.

while it 'can' do that, it's not needed. setting a different
configuration for every ssid is not only nuts, but it's asking for
problems.

However, that is exactly what Android does. And Windows. And Linux. Each
SSID gets its own independent configuration.

strange how leaving it at its default (dhcp) works on any ssid without
any need for independent configs.

Ever heard of keys/passwords?

sure. what about it? that has nothing to do with leaving it on dhcp.

In article , Frank Slootweg
wrote:

[1] Not to mention that most users wouldn't know what the fsck that
*is*, let alone install and configure one.

and yet they'll know how to configure a static ip?

Yes, because the IP in question is reported by the FTP server when you
start it and it can be configured in the router.

OTOH, your imaginary DNS server is blissfully absent in the described
set up, so it *can* not even be set up.

nothing imaginary about it and is likely already active, so nothing to
set up.

As usual no specifics, so you claim can't be verified, so it's false
until proven (by you) otherwise.

already explained.

In article , Pat
wrote:


as has been explained, that does not require a static ip.

As has been explained, it does.

If your have a router that has the "reservations" feature,

which nearly all do

your get
the advantages of a static IP without setting your device to a static
IP. That's what they mean by "that does not require a static IP". The
OP wants an IP that never changes. You can get that without setting
your device to a static IP.

yep.

not only that, but you can access the device by name and not have to
memorize its ip.

In article , Carlos E.R.
wrote:


Apparently he is lucky to have a router where you can assign names to
the reservations, so he thinks we all have.

most routers do, but if for some reason the router does not, all is not
lost. there are other ways to use dns rather than ips.

http://cache-www.linksys.com/support...-007_EN_v8.png

Assuming that is a DNS name and not a BIOS name.

bios has nothing to do with it.

In article , Carlos E.R.
wrote:


When I say I need a "static IP" (address) for my device and I have (at
least) my device (which happens to be an Android device) and a (NAT)
router, then:

- What do I mean (by "I need a "static IP" for my device")?

I won't question why you need a static IP address for your device.
Well, maybe I will a little.
...
Things like phones,
tablets, game boxes, gizmos, laptops, PC's, media players, etc work
nicely with DHCP assigned addresses.

Well, you have missed some information. There is some in the first post
of the thread, and more on the previous thread (I don't remember if it
was crosposted to the same groups), and then repeated again on some
other posts in this thread.

The OP is running a small FTP server on his phone, when needed, and
accesses it from his computer. Obviously having the device on the same
IP every day avoids having to find the IP of the day.

as has been explained, that does not require a static ip.

As has been explained, it does.

as has been explained, you are wrong.

a static ip is *not* required and will cause additional problems,
something you even agree with, yet you keep arguing anyway.