How does setting a static IP on a linux Android mobile device prevent the linux router from assigning that IP address to another device?
On any mobile device (iOS, Android, whatever), you can set up an FTP server (eg ES File Explorer on Android) with a static IP address so that Windows "My Network Places" has a permanent "shortcut" to the entire mobile device file system (eg ftp://192.158.1.15:3721).
This is very useful, and I've been using it for a couple of weeks ever since it was discussed here - because it effectively mounts the mobile device as a network drive on Windows without adding any new software on either Android or Windows.
The Android linux mobile device seems to retain the static IP address even after multiple boots of the linux Android phone or of the Linux SOHO router which is set up to serve DHCP addresses.
How does that work? Why doesn't the linux router give another linux device the IP address "192.168.1.15"?
It seems as if it works by "magic" but there must be some logic here.
How does setting the IP address to be static on the Android phone cause the linux router to *accept* that static address permanently?
which can be set up in the mobile device connection settings Android: Settings > WiFi > AP > Modify network config > IP settings > static (IP address = 192.158.1.15)