In the quiet world of local networks, time flows evenly, packets move through their routes, ARP tables nap peacefully, and video-surveillance engineers sip their coffee while watching stable RTSP streams. Everything seems calm.
But that’s just an illusion.Because somewhere out there, behind the switch, the nightmare begins: that little IP camera above the doorway suddenly decides to change its IP address. Or worse — change its MAC.
Suddenly the VMS sees nothing, ONVIF scanners report “duplicates,” the DHCP server frantically throws out new leases, and the engineer runs across the network like a shepherd chasing a single cow that slipped out of the pen.
This article explains why this happens — and how to stop cameras from behaving like teenagers who forgot their house keys.
1. DHCP: a mechanism invented to make everything harder
DHCP is like a great idea that turned into a sitcom in real life.
The concept was simple:
“Plug in the camera — it gets its IP automatically. Beautiful!”
But network engineers know the truth: automation is a delicate art of keeping chaos barely controlled.
Why do cameras change their IP?
DHCP lease expired.
The camera rebooted.
The router rebooted.
The DHCP server issued an address that was free yesterday but isn’t today.
The network has too many devices and too few addresses.
Every time DHCP “reshuffles the deck,” the camera gets a new IP — and RTSP URLs instantly turn into confetti.
Ultrabudget cameras — and strange “brands with a single firmware” — love this approach: no static IPs, no rules, just DHCP and chaos.
IP changed → RTSP died → recording stopped → engineer’s coffee went cold → life lost its brightness.
2. When the network has two masters: the IP conflict
The real thriller begins when two devices end up with the same IP. The camera, instead of standing its ground, does what it always does:
resets its network interface,
requests a new DHCP address,
or falls back into AutoIP (169.254.x.x),
a digital exile “into the woods.”
For the VMS, it looks like this: “The device vanished. Literally. It moved to a parallel range with no routing and no friends.”
3. New subnet: the camera decides to start life over
Some IT events resemble apartment renovations: never on schedule and always destructive.
The router changes. The IP pool changes. The VLAN changes. The subnet changes.
And the camera — never informed about the new reality — becomes blind and mute. It tries DHCP, receives a new address, or flees into AutoIP.
Then the engineer goes hunting for it like in an old RPG: wandering through locations, collecting clues, praying that ONVIF Discovery reveals something.
4. Factory reset: the button best left untouched
Factory reset brings the comedy:
IP resets,
network stack clears,
and — sometimes (!) — the MAC address changes.
Yes, MAC. Cheap SoCs can store MAC not in ROM but in a config block.
Reset it — and the camera wakes up with a brand new identity like a soap-opera character: “Who am I? Where am I? Why is my address different?”
Firmware updates can do the same. One MAC disappears. A new one appears. DHCP assigns a new IP. RTSP dies again. Engineers suffer.
5. Wi-Fi cameras: the god-tier source of network chaos
If you want a stable security system — Wi-Fi cameras are your enemy.
They change IPs more often than people change passwords — and with the same logic:
the router flips them between 2.4 and 5 GHz,
a signal drop forces a reconnect,
privacy-MAC features activate,
the access point resets their association.
Each reconnection = new MAC (sometimes), new IP (often), new pain (always).
A Wi-Fi camera lives in a parallel universe where stable network parameters are a myth passed down by storytellers.
6. When a MAC address is not carved in stone
By design, the MAC address should be immutable, like a tax code. But the real world ruins everything.
A MAC can change when:
the camera uses a software MAC stored in EEPROM,
the camera was reflashed,
factory reset was performed,
Wi-Fi privacy MAC mode engaged,
the manufacturer cut costs and generates a fresh MAC on every boot.
Yes, some cameras truly generate a random MAC on every startup. Not a bug — a feature, apparently.
7. Consequences: SmartVision trying to keep the world from collapsing
RTSP streams rely on IP. IP relies on MAC. MAC may change.
The result:
the VMS loses the device,
recording breaks,
events stop being logged,
ONVIF shows duplicates under different MACs,
DHCP hands out new addresses like it’s playing bingo.
A surveillance system turns into a cyberpunk plot — just with fewer neon lights and more swearing.
8. Why some cameras forbid setting a static IP
This isn’t a joke: some IP cameras truly won’t let you set a static IP.
Reasons:
stripped-down firmware — the manufacturer saved on everything,
meant to work only with an OEM NVR,
Wi-Fi models rely exclusively on DHCP,
networking code written “just because it compiles.”
Sometimes it feels like the manufacturers fear letting the user configure network settings — what if it breaks?
9. How to tame this zoo
Now the important part: can you force cameras to stop living chaotically?
Yes. But you’ll need engineering finesse.
1. DHCP reservations (must-have)
The golden standard. The camera stays on DHCP, but the DHCP server always gives it the same IP.
If MAC is stable — perfect. If not — you’ve bought the wrong hardware line.
2. ONVIF Device Management for IP assignment
Many cameras that block IP changes in the web interface allow them via ONVIF.
3. Static DNS for RTSP
A brilliant trick:
create entry:
cam01.local → 192.168.1.45
use in RTSP:
rtsp://cam01.local/stream
IP changed? Only the DNS entry changes — not the VMS configuration.
Elegant. Reliable. Engineer-approved.
4. Network segmentation
Cameras get their own VLAN - no conflicts, no noise, DHCP pool only for them. Pure order.
5. Increase DHCP lease time
Never set lease to 10 minutes. That’s a recipe for disaster.
For cameras:
at least 24 hours,
better 7 days,
for large facilities — 30 days.
6. Avoid cameras with “floating MAC”
If MAC “wanders” after every reset - that’s not a camera, that’s a circus act.
Such devices do not belong in production.
The Finale: order is possible — but it requires discipline
IP cameras aren’t simple video boxes.
They’re tiny network creatures — sometimes capricious, sometimes unpredictable, sometimes breaking just because someone looked at them wrong.
They live by their own rules:
DHCP gives — DHCP takes away.
MAC can mutate.
AutoIP appears at the worst possible moment.
Wi-Fi behaves like a wild animal.
But with good architecture, proper reserving, ONVIF control, and reputable manufacturers, chaos becomes a manageable ecosystem.
And systems like SmartVision can automatically retrieve new IPs by MAC, reconnect streams, rediscover devices, and keep engineers sane — even when a tiny camera above the door decides to start life with a brand-new IP.