Urgent.News

What's breaking now, across thousands of outlets.

Tech

Every Guide Says "Reserve the Address on Your Router." What If the Router Is Not Yours?

Almost every guide to running an old Android phone as a security camera — including the ones on this blog — ends at the same place. The live view works, you bookmark an address like 192.168.1.7:8080 , and then a line appears telling you to go into your router's settings and reserve that address so the bookmark never breaks. That advice is correct. It is also written for somebody who can log into…

This guide addresses the issue of maintaining a consistent IP address for an Android phone used as a security camera, particularly when the router is not under the user's control. Many guides suggest reserving an IP address within the router's settings, but this advice may not be applicable in situations where the user cannot access the router's admin page.

In cases where the user cannot log into the router, they can still run the phone as a camera, but will lose the convenience of a permanent, never-changing address. Instead, the user should learn to read the phone's current address from the phone itself, keep the phone continuously on the network to prevent address rotation, and only manually set the address on the phone if necessary.

This is because the phone's IP address changes due to the Dynamic Host Configuration Protocol (DHCP) allocation mechanism, which does not guarantee the same address for an extended period.

The problem lies with the router, not the phone. The router may reuse addresses after the lease has expired, the router might not remember leases after a restart, or the camera may not be assigned the same address if it leaves the network for an extended period. The issue is rarely related to Android's MAC address randomization, as the phone typically presents the same identity to the router every time.

The only real exception is when the developer setting "Wi-Fi non-persistent MAC randomization" is enabled, which re-randomizes the phone's address under specific conditions, such as after the DHCP lease duration has expired or if the MAC address for a network profile is more than 24 hours old.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Property Domain Offboarding — Delete Records Without Whole-Zone Risk

Short answer: retire only the records owned by the departing property, never the whole DNS zone, unless an ownership check proves that the zone itself has no other consumers.

  • Delete DNS records property by property, not entire zone
  • Lower TTL before deletion, wait for old TTL window
  • Maintain rollback data until resolver confirms changes

What `rsync -avz --delete` Actually Does

A lot of people paste rsync -avz --delete into a deploy script and move on without ever unpacking what each letter means. It works, so there's rarely a reason to stop and ask.

More from Friday 18 September →