Something I've never really thought about - I install a new IP cam - it gets a DHCP address. 6 months later there's a power failure - am I going to have to reconfig the camera in ZM? Or am I better off to get a static IP from the start?
an enquiring mind...
Staic IP vs DHCP
Re: Staic IP vs DHCP
Depends ... if you set up zoneminder with the camera as "192.168.X.Y" -- an IP address, and it gets issued a new address (for any reason, DHCP whim, power cut etc.) then Zoneminder will lose the camera, because it's not longer there.
Three solutions:
1) Static IP (tell the camera to use static IP and programme it there, then use that IP at ZM) -- and hope the camera doesn't do a factory reset which sets it back to some default
2) Don't use an IP address. Use a hostname. Tell zoneminder your camera is at "mycam01" or "mycam01.local.domain" and then let your network's name server do its job: Mapping host names to IP addresses.
[I use a combination of 1 and 2, my cameras are at static numeric addresses, my name server knows which hosts are which IP addresses, ZM refers to them by name NOT number, nothing moves on reboot/power cut]
3) Or, give your DHCP server instructions that once an IP address is handed out, it should remain associated with that hardware MAC address forever. Then, it won't hand out random IP addresses when the device disconnects and reconnects. Most DHCP servers will have some kind of table of persistent mappings you can use for fixed devices.
Note: This is all networking-level problems, not ZoneMinder specifically -- any other machine/service will have similar issues (where did my NAS go? etc.)
Three solutions:
1) Static IP (tell the camera to use static IP and programme it there, then use that IP at ZM) -- and hope the camera doesn't do a factory reset which sets it back to some default
2) Don't use an IP address. Use a hostname. Tell zoneminder your camera is at "mycam01" or "mycam01.local.domain" and then let your network's name server do its job: Mapping host names to IP addresses.
[I use a combination of 1 and 2, my cameras are at static numeric addresses, my name server knows which hosts are which IP addresses, ZM refers to them by name NOT number, nothing moves on reboot/power cut]
3) Or, give your DHCP server instructions that once an IP address is handed out, it should remain associated with that hardware MAC address forever. Then, it won't hand out random IP addresses when the device disconnects and reconnects. Most DHCP servers will have some kind of table of persistent mappings you can use for fixed devices.
Note: This is all networking-level problems, not ZoneMinder specifically -- any other machine/service will have similar issues (where did my NAS go? etc.)
Re: Staic IP vs DHCP
Yup nothing to do with zoneminder directly as it does not control your network as stated. I don't use domains or sub-domains I just reserve ip's per device with my router and also mac id's to control access.
Life what's that now back to zoneminder and motion detection hell.
-
dougmccrary
- Posts: 1371
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: Staic IP vs DHCP
ASUS has a similar app.
But that’s not what this is about.
For example I have 20 cameras. I assign IPs such that monitor 1 is IP 192.168.1.201.. up to 192.168.1.220.
So when I want to connect to a camera directly, I don’t need to look up the address. And neither does ZM.
DHCP won’t do that.
You may not find that useful, but I sure do.
But that’s not what this is about.
For example I have 20 cameras. I assign IPs such that monitor 1 is IP 192.168.1.201.. up to 192.168.1.220.
So when I want to connect to a camera directly, I don’t need to look up the address. And neither does ZM.
DHCP won’t do that.
You may not find that useful, but I sure do.
-
dougmccrary
- Posts: 1371
- Joined: Sat Aug 31, 2019 7:35 am
- Location: San Diego
Re: Staic IP vs DHCP
on iOS, it may help to turn off "Private Wi-Fi Address"