Static ip for cameras

[Anderson7]

I have a Verizon Quantum router.

Because the wifi is weak in parts of the house, I have an ASUS ACRH13 router in another room attached by ethernet cable to it. The ASUS is set as an AP.

Part of my home WLAN includes some ip 2.4 security cameras that go directly to a cam viewer app (not calling outside the home). To ensure continuous connection, I went into the verizon router Advanced Tab/IP Address Distribution/Connection List and set the camera ip addresses to static. I also gave them names to help me remember them.

Just now, the cameras stopped working and I discovered that was because their IPs had changed! Maybe when I rebooted the Verizon or ASUS router but I'm not sure.

So I went back to verizon router Advanced Tab/IP Address Distribution/Connection List. The static addresses were still there and marked as "static" but the cameras now had new IPs they are currently connected to!!! The old IPs no longer work in the camera app. The new IPs were also present in the ASUS connection list but the old static IPs were not there.

I don't understand what I am doing wrong. How do I prevent this from happening? I think the ASUS router is assigning new IPs (even though it is an AP) but I am not sure how to make them static there too.

I "think" I need to

1. In the Verizon router, delete the old static IPs

2. In the Verizon router, mae the new camera IPs static

3. In the ASUS router make the new current camera IPs static

But I'm no good at networks so I may be missing something here. And it is very frustrating.

Help appreciated.

[Anderson7]

Of course wired camera systems solve many of the privacy issues but wiring is just not a practical option for me.

[Edg1]

From you computer, the IP the camera pulls from the router try typing in that IP to your browser. See if you can login to the camera directly. Maybe you will be able configure the IP. Worth a shot.

[Anderson7]

I can. On a browser each camera ip opens a page where I can login using the login/password settings I created in the app.

Attached is what appears in the browser when I enter the IP of one of the cameras.

If I enter the correct login info, the camera image appears just like in the app.

But, the problem is that particular camera's ip does not stay constant for very long because it does not stay static despite being set that way.

You brought up an interesting point. Why does the Verizon router keep the printer IP static? I think it does but will need to check. If it can do it for the printer (on my system too) why not for the individual cameras?

[Anderson7]

Entering the printer ip in a browser just times out. fwiw.

[Edg1]

During setup my network printer, it asked to be DHCP or Static. The IP that I had set up always remained. The same as a PC I have connected. I was thinking if you are able to login to your cameras and set their IPs to static they wouldn't change.

I was also thinking maybe change your DHCP pool to start at 192.168.1.15 and assign statics to the cameras in the range of 192.168.1.2-14.

[Anderson7]

"I was also thinking maybe change your DHCP pool to start at 192.168.1.15 and assign statics to the cameras in the range of 192.168.1.2-14."

That's a brilliant idea! I want to try that. Just went into the router settings but cannot find where to assign the DHCP pool. Where is it? How do I get to that DHCP settings page?

[Edg1]

I believe without looking...

My Network > Network Connections > Network ( Home/Office). 
Once is setting ls scroll down and you will see 192.168.1.2 - 192.168.1.255

If you can’t find it let me know and I’ll plug it in and check. 

[Anderson7]

OK I found it before reading your reply.

It was at Advanced/Network (Home/Office).

I used Edit and changed the distribution to start at 192.168.1.15

I then edited one camera IP from "the orig" to 192.168.1.5

The router accepted and I logged out

That's when I discovered might be the root problem.

--The Verizon router's distribution list shows the camera assigned as 192.168.1.5

--But, the camera in question actually remains connected to "the orig" IP, not the new ip. If I tell a browser to go to 192.168.1.5 it times out. If I tell the browser to go to the "the orig" IP it opens the login screen.

So I thought it might be because the ASUS AP had not yet received the new ip.

--I rebooted the ASUS and

a) the camera is still connected to "the orig" ip (not the new one. If I tell the app to connect to 192.168.1.5, it finds nothing.

b) the rebooted ASUS router shows nothing connected at 192.168.1.5. Indeed 192.168.1.5 is not present in the list of connected devices.

c) the rebooted ASUS router shows that that camera is still connected at "the orig" IP

d) checked the cable connection: the ethernet cable goes from a yellow port oIn the Verizon router to the blue WAN port on the ASUS router. Is that correct?

So, I though the Verizon router needs to be rebooted before it "really" assigns the new ips. I therefore powered off the Verizon router, waited 10 secs and powered it up again.

No change. That camera is still showing an image when connected to the "the orig" IP and nothing appears when connected to 192.168.1.5.

I know nothing about wireless networks and routers and am flying blind, but it seems the verizon is just not assigning ips the way it is told to or something else weird is going on.

Totally at a loss.

[Anderson7]

Additional info:

The Verizon distribution list still shows that camera connected to the original ip, not the new 192.168.1.5 ip. I deleted the 192.168.1.5 static ip entry in the distribution list. (same mac!)

The Verizon distribution list still shows that camera connected to the original ip (not ....1.5) but it is marked as dynamic. (I'm sure I had once set it as static but it is now dynamic).

Did I mention I hate wireless networks?

Just rechecked and that camera is still connected to the original working ip, not the now deleted ......1.5 ip

[Anderson7]

It's after midnight and I'm going to sleep. But I checked and in several instances

1. the Verizon router will assign to the same mac a new ip.

2. The previous static ip is ignored and a new non-static ip is assigned by the router to the same mac address. This has to be a serious bug brought over by the update.

Strangely, on editing the newly assigned ip, the router will not let me change the identifying name (error says name exists) even though it has 2 listing for the same mac. I did not enter these duplicate macs manually. They are read by the router. And this happened for several camera macs. The router seems to have lost the ability to identify or record macs correctly.

This is crazy.

[Edg1]

I would reset the router at for 15 seconds to clear everything out. Then login and change the DHCP pool and set up your static IPs. Don't plug in the cameras until all the configuration is done. 

[gs0b]

There are two types of "static" IP address assignment.  Be sure you aren't mixing them, otherwise confusion can happen.

The first type is an IP address reservation managed in the DHCP server (i.e. router).  With this approach, the DHCP server hands out the reserved IP address anytime the specific client uses DHCP to request an IP address.  The client is identified by it's MAC address.  While this is often labeled "static" on the DHCP server's management interface, to the device it is a dynamic IP request.

The second type is a true static assignment on the device.  In this case, the device is manually configured to use a specific IP address.  This is typically done through a UI or configuration file depending on the device.  The device will not request an IP address from a DHCP server, it will simply use the configured IP address.  If this address conflicts with one used by another device, network problems will occur.  For this reason, it is critical that a DHCP server be configured to avoid the IP address range used for true static addresses and that good documentation of manually assigned IP addresses is used.

In this specific case, you're trying to use the DCHP server IP reservation approach.  This is my preferred approach, too, as it means I don't have to muck around with settings on each device and maintain manual IP address records.  Make sure your cameras should are configured for automatic IP address assignment, otherwise they will use their locally configured address and ignore the settings in the DHCP server.

Also know that when you change an IP address reservation in the DHCP server, the client won't pick that up right away.  It won't get a new IP address until it requests a new one, either due to upcoming DHCP lease expiration, a reset (hopefully), or a manually triggered IP address request.

I've been using a Verizon G1100 with IP address reservations for many years.  I've the latest firmware.  No problems at all.

Good Luck.

[Anderson7]

OK, here's what I have done.

--removed power from all my cameras, so they are offline

--removed power from the ASUS router I'm using as an AP for same reason

--pressed reset button on the Verizon router for 15 seconds

--entered the new router password

--entered the new ssid and passwords

--Went to Advanced/IP Address distribution/connection List

--Edited the Network (Home/Office) distribution to limit the pool as follows:

Server

255.255.255.0

192.168.1.15-192.168.1.254

--Used "add Static Connection +" to add the mac addresses of the cameras with IPs in the range 192.168.1.(4-14)

--That registered correctly in the router.

The app that monitors the IP camera streams has settings for each camera stream where I simply enter the static ip for that camera. (image uploaded previously). The app only looks at that camera ip. If the router generates a different ip, the app shows a blank screen. That's why I need static ips. I've used this app successfully for years.

I'll now see if this nightmare will finally resolve itself.

Questions:

1. I can no longer access my ASUS (AP router) via wifi. The ASUS router is connected by ethernet cable from the Verizon router. How do I determine the new ip address the Verizon router assigned to it? I searched in the distribution list but cannot identify it. The old ip address no longer works.

Thank you guys for helping. This has been a hasstle. Everything worked for years but somehow something changed about a week ago.

[gs0b]

You are confusing a DHCP server reservation (static lease) with a device static IP configuration.  You want a DHCP server reservation (static lease), not a static IP.  The two are quite different and mixing them causes problems.

"Add Static Connection" creates a DHCP reservation on the router.  You need to do that within the DHCP distribution pool, not outside of it.  Otherwise, it won't work.

The range outside of the distribution pool should be used for true static addresses assigned at the device.

Check the cameras to make sure they aren't configured for static IP addresses.  Look for "manual IP address" or similar text.  You want automatic assignment so they get the IP address reserved on the router.  Any changes to IP address reservations won't be picked up until the camera renews it's IP address lease.  You'll have to check the camera documentation to find out how to force a lease renewal.

I haven't followed the details on your Asus AP, so I've little to say about it.  You should be able to find it's IP address by checking the connected devices list on the router.  Look for it's MAC address, which may be printed on it's label.  Once you find it's entry in the DHCP table, you can edit it to make it "static lease," too.

Good Luck.

[Anderson7]

Thank you for your input and clear explanation gs0b.

I think I now see what you mean. You are correct, I am more than a little confused. It's been a frustrating time with the router becoming corrupted and driving me crazy by repeatedly assigning different IPs to the same mac devices with both mac/ip sets appearing in the connection list!! Hopefully, now that I reset the router the router will work correctly. Besides, I'm an end user who does not really understand wireless networks. But I think I now see the difference between a

DHCP server reservation (static lease) and a

static ip.

I was not aware of the difference. 

So, I will delete the static ip setups I made outside the ip pool and remake them within the distribution pool. Hopefully, now that the router has been reset and (perhaps) no longer assigning new ips to the same macs (!), the DHCP server reservation (static lease) will work correctly and the cameras remain connected to their assigned IPs.

Thank you for your help and explanation. 

[Anderson7]

Just wanted to add that the cameras are not set to a static ip. They get an ip assigned to them by the router.

[Edg1]

Ok I came home and plugged in my G1100. I go to...

Advanced > IP Address Distribution > Network(Home/Office) > Edit

• Set my DHCP pool to 192.1681.11 to 192.168.50 then Apply 

Connection list > Add static connection +

• Host Name: Mac ( Make your name something like the camera location or cam1)
• IP Address: 192.168.1.2
• MAC : Mac's MAC Address then Apply

Also set my phone as 192.168.1.3 and both been up and running for over 2 hours. How long is it once you configure the camera until it pulls another IP?

[Anderson7 · Accepted solution]

Things are fixed now (I think).

A reply I sent seems to have gotten lost. So i may repeat myself. What worked was:

--removed power from all my cameras, so they were offline

--removed power from the ASUS router I'm using as an AP for same reason

--pressed reset button on the Verizon router for 15 seconds

--entered the new router password

--entered the new ssid and passwords

--Went to Advanced/IP Address distribution/connection List

--Edited the Network (Home/Office) distribution to limit the pool as follows:

Server 255.255.255.0 192.168.1.15-192.168.1.254
--Used "add Static Connection +" to add the mac addresses of the cameras with IPs in the range 192.168.1.(4-14)

--That registered correctly in the router.

Prior to doing that, the Verizon router would issue new ip addresses every few hours (5-6hrs I think). What's worse, the distribution list would show 2 different IPS for the same Mac device, only the newer one connecting. Weird. So far, this is not happening after the router reset.

Fwiw, I (who know nothing about these things) think that the router was corrupted possibly by interaction with the Asus router I was using as an ap to extend the wlan coverage range. I say that because I noticed and repeatedly mentioned that the list of connected devices and their associated IPs were different in the 2 routers. I don't think that should be if the Asus router is just used as an Access Point. Should it? But, so far things are fine with the 'static IPS' set outside the distribution range. I'll see if things go south again tomorrow. 

[Edg1]

If the Asus is set to AP mode the DHCP server should disabled. It shouldn't be given the out IP addresses. Is the Asus still connected? I'm curious if while still in AP mode can you go to the LAN settings and see if the DHCP is disabled. 

I'll still have the G1100 setup so tomorrow morning I'll let you know if the IP changed. 

[Anderson7]

Currently:

The cameras are still connected correctly to the IPs outside the distribution group.

The Asus is still connected in AP mode.

Asus Lan page: (not sure how to interpret the terminology so here are the contents):

• Get LAN IP Automatically?  Yes / No   Yes is selected
• Connect to DNS Server automatically?  Yes / No   No is selected
• DNS server 1 and 2 fields are empty with no numbers
  

In ASUS 'device connection list', now the camera IPs are correctly displayed with the correct numbers exactly as in the Verizon router.

Things now seem fine since I did what you suggested about resetting the Verizon router and using IPs outside the distribution group.  If this continues, I'm golden . Thank you very very much.

If this persists for another 24-48 hrs, I'll return and mark it as the solution.

What do you think of gs0b's comments higher up about not using the IPs outside the distribution group? His explanation was very persuasive but when I followed his suggestion and reverted to the fixed IPs within the distribution group is when everything went haywire again. So you were correct but his explanation seemed so persuasive.

[Edg1]

I agree with gs0b, I would rather have the static IPs set directly in each camera and outside the DHCP range. But if there is no way to configure the IPs directly into each camera I figured we could try something else. 
Some routers actually won’t let you reserve IPs outside the DHCP range. Luckily the G1100 does let you. 
As far as the Asus that sounds good. It’s getting a dynamic IP from the G1100. Nothing needs to be in the DNS field since the router is taking care of that.