Search results

You said: The said NVRs were ping-able. Do you mean the ARE pingable now, or they WERE pingable when things worked, but not now?

So you have specifically designed your topology to be in different subnet? In this case what are you using to route between them? Did you set this all up yourself?

With that subnet mask your pc is in a different subnet than the NVR’s. - What has changed since this was last working? - what led you setup with a topology like this?

What is your subnet mask? Those are very unusual addresses for an internal network, can you give a bigger overview of your topology?

I have this question also.

Are you sure there hasn't been a reboot you wasn't aware of?

This happens for me too - same NVR, latest firmware, and has happened on all firmwares since I've used virtual host. I've just learnt to live with it and added it to my "fix this after power cut" list.

Didn't want to start on that route :)

What this is doing is putting the camera side of the NVR onto your local LAN. In theory, there's no technical reason why this wouldn't achieve the objective (that being for the camera's to get to the internet) but the biggest issue I'd have with this (and the one reason alone I wouldn't...

One of these: https://linitx.com/product/linitx-apu2-d4-network-firewall-4gb-ram-(3nic+usb+rtc)-with-pfsense--pre-configured-kit/15318 An added benefit is that pfsense can run an OpenVPN server. Matched with OpenVPN client on iPhone/iPad I can use the app to view NVR remotely without having...

You are correct - I have the SuperHub too. Once you have a decent router - I can recommend PFSense - set the superhub into modem mode.

To allow the cameras to send email directly: Turn on the virtual host feature on the NVR Add a static route on your router/firewall for the network 192.168.254.0/24 pointing to 192.168.1.99. The rest of your settings are ok. The NVR doesn't NAT the camera's addresses, so the firewall needs...

Wanted to come back on this. I've played with a number of settings and somehow have made the interval four seconds rather than two. I have no idea how I did this, so am trying to go back through and reduce the interval. Any pointers on where this value is?

I have noted this too & just thought it was me. Night performance has definitely got worse since my upgrade from: DS-7604NI-K1-4P - v3.4.95 DS-2CD2355FWD-I - v5.4.5 To latest versions

There are no Expert settings for Smart events, only Basic events.

Topology: DS-7604NI-K1-4P - v3.4.98 3 x DS-2C2355FWD-1 -v5.5.61 1 x DS-2CD2555FWD-IS v5.5.61 I have successfully set up email notifications directly from the cameras and received the three captures for the intrusion and line cross events. The problem is that the first capture is two seconds...