Need help picking out Equipment for remote Location- Needs to boot back up easily

[zero-degrees]

you have to put the NVR and the Cameras on the same IP Range. Since you already have your Network with the cameras on the 192.168.20.x range, you should probably just change the ips of your cameras to 192.168.20.x.

This is incorrect - you may leave your cameras on the NVR's own internal network and this will not cause any issues. The NVR is controlling the cameras and if you are not concerned with accessing them directly there is no need to start playing with IP settings unless you are conformable and experienced with networks and subnets.

Further more if you want to access them directly I have to believe Dahua NVR's support something like HIK's do in regards to "virtual host" so that you may simply access the cameras directly by passing the NVR.

 

[bogi]

ok did not know about that, thanks

 

[Q™]

This is incorrect - you may leave your cameras on the NVR's own internal network and this will not cause any issues. The NVR is controlling the cameras and if you are not concerned with accessing them directly there is no need to start playing with IP settings unless you are conformable and experienced with networks and subnets.

Further more if you want to access them directly I have to believe Dahua NVR's support something like HIK's do in regards to "virtual host" so that you may simply access the cameras directly by passing the NVR.

Mr. Zero definitely knows a lot more than Ol' Q...but... I' most certainly figure out how to change the camera ip addresses to the same 192.168.29.x range as your other LAN devices so that if -- in the future -- you need to log into the cameras directly via your VPN connection it will be an easy proposition. I'd also keep a log of each resource on your LAN and the IP address that each resource has been assigned.

 

[smoothie]

I'm sorry, I have read this several times and googled a lot of questions, but this was above my head. I don't plan on adding any more equipment or computers or switches. I have to make this work with the cameras, NVR, POE+ injector and my nether router.

There must be a simpler way because the youtube videos I am watching make it look a lot easier. I just want to be able to log into the NVR from afar and adjust settings and review footage. So, with that said, should I move forward with the network design above or make everything at the lake house a 192.168.20.x network and dissolve the 10.1.1.x or is it a must to separate the two networks? From your comments, it is my impression that the Netgear Wifi router needs to be one set of addresses and the Dahua something different. Otherwise the cameras will start appearing on the Netgear DHCP network. The Dahua NVR definitely does not have DHCP turned on. It is set to static 192.168.1.108

This is what it looks like in my mind, but I could definitely be wrong about this:

This diagram is accurate, but it would need a VPN to be perfect.

Be careful of the Youtube videos, they might be suggesting an easier way but that could have unforeseen consequences that can include deeply flawed security. They might be suggesting the computer network equivalent of "if you just don't install any doors or windows in your house you won't need to have a house key and you can never be locked out of your own house".

A VPN is the best way to gain remote access to the lake house network. When the VPN in connected your machine will behave as if it is plugged into the network at the lake house. Depending on the exact model of Netgear Router you have it may or may not have this capability built into it already. There are many home routers/firewalls that have VPN capabilities built in. To have a VPN you must have a VPN endpoint at the lake house, this would commonly either be a router/firewall with VPN capabilities or a computer running the required software (free off the Internet). The computer, smart phone or tablet you use to connect to the lake house vpn would have a free software VPN client installed on it. To access the lake house networks and its cameras you would open the VPN software, click connect and leave it running, open the SmartPSS and use it as you wanted to, close the SmartPSS, and finally disconnect then close the VPN software.

 

[CaliGirl]

Mr. Zero definitely knows a lot more than Ol' Q...but... I' most certainly figure out how to change the camera ip addresses to the same 192.168.29.x range as your other LAN devices so that if -- in the future -- you need to log into the cameras directly via your VPN connection it will be an easy proposition. I'd also keep a log of each resource on your LAN and the IP address that each resource has been assigned.

Since the cameras are behind the NVR network, there is no access to them directly. SO I tried plugging them directly into the netgear router and finding them, but they do not show up as attached devices (I powered it via a 12v 1amp transformer since they are POE). I also tried plugging them directly into the computer, turing off wifi, and connecting directly. I also tried the Dahua Config tool and scanning, but nothing appears when you do so. SO, while I would love to do this, I am dumbfounded on how to. The turret camera is powered bc I can see the IR light on.

 

[pschmehl]

Since the cameras are behind the NVR network, there is no access to them directly. SO I tried plugging them directly into the netgear router and finding them, but they do not show up as attached devices (I powered it via a 12v 1amp transformer since they are POE). I also tried plugging them directly into the computer, turing off wifi, and connecting directly. I also tried the Dahua Config tool and scanning, but nothing appears when you do so. SO, while I would love to do this, I am dumbfounded on how to. The turret camera is powered bc I can see the IR light on.

Leave them connected to the NVR but re-ip them to the same network that the NetGear router is using. You'll also need to re-ip the NVR to the same network as well. Keep in mind. all these addresses are private, so they're not addressable from the internet unless you allow it.

Since you want to be able to access the cameras directly from home, you'll need to setup a VPN (virtual private network) between home and the lake cabin.) Your routers should have that capability built in to them. Google will get you plenty of explanations for how to do it and why you want to do it. You do not want your cameras or NVR accessible from the internet without you controlling WHO has access.

 

[Anto]

@CaliGirl, I stopped using Dahua DDNS because most of the time was unable to access Dahua server. In the meantime if you want to access your cam remotely enable "P2P" in your NVR, see attached. Then you can connect to NVR remotely by using gdMSS lite App. You need to add your NVR to the Devices in your gdMSS lite App, make sure to select "P2P" option. The "P2P" connection works awesome...have never been unable to connect to my NVR to view the cams. I can also control PTZ functions remotely.
I should mention you do NOT need an IP address to use "P2P".

 

[Kawboy12R]

My Asus routers offer their own DDNS service through Asus for free. Never had any problems. I don't remember if router brand has been mentioned but yours may offer the same service.

 

[CaliGirl]

Leave them connected to the NVR but re-ip them to the same network that the NetGear router is using. You'll also need to re-ip the NVR to the same network as well. Keep in mind. all these addresses are private, so they're not addressable from the internet unless you allow it.

Since you want to be able to access the cameras directly from home, you'll need to setup a VPN (virtual private network) between home and the lake cabin.) Your routers should have that capability built in to them. Google will get you plenty of explanations for how to do it and why you want to do it. You do not want your cameras or NVR accessible from the internet without you controlling WHO has access.

I spent 2-3 hrs. re-ipping them to 192.168.20.x to match the NVR and wifi router. Then I realized that everytime I plug them into the NVR they are reverting to 10.1.1.x and loosing their set IP. I had them set on static IP and unchecked the auto aim function.

I took the advice of a member and bought an Asus router that has built in VPN> I spent another 2-3 hrs trying to set up a VPN and got stuck. It connects but the connection comes to such a crawl that I don't have enough speed to do or see anything. I can barely log into the asus router on the first page, then it gets stuck. I tried pptp then switched to OpenVPN using an deported file and openvpn client app. I gave up

I tried the P2p option (great idea) and the app crashes everytime I try to view a camera. I was able to add them with the qr code but the app crashes each and every time. I tried my iPad (different version of app) and it still crashes. Terrible app design and very bad reviews on the app store

I'm just going to put this out there for any other newbies reading this post. Remote connections to an NVR takes significant energy and know how. I have easily spent 20-30hrs on this project reading post, youtube videos, and trying on my own and I'm not making much progress. Had I known it was going to be this hard I wouldn't have even tried. I'm pretty close to giving up.

 

[fenderman]

The camera will always get a new ip address subnet from the NVR..thats how it works, the nvr basically creates its own mini network...when you remote access, you will be accessing the NVR not the camera directly.

 

[Q™]

Opps...sorry for the bad advice I gave you...I feel bad about that Cali...I've never used an NVR and I assumed they work much like NVR software. I'll refrain from making assumptions in the future. Sorry to cause you unneccesary work.

 

[CaliGirl]

Nope, no worries. Just trying to get to the end solution. Here is what it looks like when I try to access a VPN outside my home network. The neighbors borrowed wifi network is fast until I turn on the Open VPN client. Then I can reach any local connection in a reasonable amount of time or at all. As soon as I go back to my home wifi the speed is fast and I can actually reach the connections. Why does the ip address change to 10.1.1.6 when the open vpn client details window is open?

 

[pschmehl]

The camera will always get a new ip address subnet from the NVR..thats how it works, the nvr basically creates its own mini network...when you remote access, you will be accessing the NVR not the camera directly.

I did not know that. @CaliGirl, my apologies for creating excess work for you. Hopefully you'll be able to get the VPN tunnel setup and access the NVR to deal with the cameras.

I would try to find a friend in the computer admin business who understands VPNs to give you some assistance. If you can get that up and running, you can (hopefully) get the access you desire so you can monitor the lake house.

 

[pschmehl]

@CaliGirl, you want the VPN server running at the lake house. Then you access it using the client on your Mac. The VPN server then makes all your lake house equipment accessible to you at your home (or from anywhere else for that matter.)

There are a number of free VPN services on the internet. You could use those to test connecting with your Mac client so that you can verify that using your Mac as a VPN client works acceptably. Once connected run a speed test to see if download and upload speeds are affected negatively.

Update, this site will let you test connecting - http://freevpnaccess.com/

I wasn't able to connect to the Chicago server, but Miami connected immediately. Then I ran a speed test, and there was no difference from working without VPN.

 

[CaliGirl]

@CaliGirl, you want the VPN server running at the lake house. Then you access it using the client on your Mac. The VPN server then makes all your lake house equipment accessible to you at your home (or from anywhere else for that matter.)

There are a number of free VPN services on the internet. You could use those to test connecting with your Mac client so that you can verify that using your Mac as a VPN client works acceptably. Once connected run a speed test to see if download and upload speeds are affected negatively.

Ya, but testing to make sure it will work at home before I get all the way to remote location and run into these troubles. Only have 1-2 days to install the cameras and get it running then leave. Thus the reason why I am building it at home, checking that the VPN will actually work from a neighbors connection to my house's network. Then take the router with me and all the cameras and install them. There is very limited access to stores that have internet equipment there. I have already had to buy a new Asus router with VPN that would have been impossible to get there. And it has taken 8x longer to get this far then expected

If the VPN doesn't work at home it is going to have trouble at the cabin. The Dahua software is very buggy. IF you select sub stream on SmartPSS it crashes. And neither IOS Dahua app work for me, they both crash consistently.

 

[mando209]

Dahua app don't crash on me but it's annoying that almost each time I open the app I need to click on the cam to open it.using iphone4.will get android tablet when the time is right.tinycam seems like it's the best mobile app.


Sent from my iPhone using Tapatalk

 

[pschmehl]

Slow response time is often due to DNS issues. Test your Mac client on your neighbor's network to the free vpn service I posted. If that works acceptably, you need to look at the Asus router. Did you replace your home router with the Asus? Or set it up as a client on your home network behind your home router? Best to switch them out and use the Asus at home for the testing. Then make sure you're using a good DNS service (either your ISP or Google (8.8.8.8) on the Asus. If the Asus is behind your home router, that could be the issue.

 

[CaliGirl]

I tried the VPN test and it connected quickly and easily. And the speed test was fast, no difference from home network.

I replaced the home router with this N900 ASUS that has built in VPN. Only one router is being used: https://www.amazon.com/gp/product/B00FK1E46U/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1

I don't know what DNS is but will read about it. Internet is via Xfinity at 120 mbps download. speed.

VPN test (worked well), asus vpn test on home network (worked well), switch to neighbor's wifi to test same VPN (connection error):

 

[pschmehl]

DNS is the internet's address lookup service. When you type in www.amazon.com, DNS converts that to an IP address that computer's understand, and then a connection is requested to that IP address. The router should have a place in the settings where you can designate an appropriate DNS server. The behavior you describe sounds like your computer is not finding what the addresses it's asking for when you're connected through VPN.

 

[CaliGirl]

Ok, looking into the DNS right now. Added Google DNS and no improvement.

I tested the Miami VPN on the other two public networks and it did not connect. But it connected fine on the home network. But, that indicates that I even if my home vpn was working that I wouldn't be able to access it through these wifi networks for whatever reason. One is 12mbps down, 2mbps up consistently. But the Miami vpn will not connect at all. Miami connects perfect on home network. Will try a different/faster public network tomorrow in town.