Search results for query: static route 3 things

Not necessarily so, as the song goes. https://ipcamtalk.com/search/135569/?q=static+route+3+things&c[users]=alastairstevenson&o=date And I'd expect Dahua NVRs to behave in the same way. It would be interesting if someone could check this out ...

Given virtual host is active, as you have proven, you should be able to access the NVR PoE-connected cameras directly with a small change to your network routing, instead of going via the NATed connection. This should work better. 3 things required: The PoE-connected camera needs to have the...

This is what you need as the way to gain normal access to cameras connected to NVR POE ports, and for them to access the internet to send email etc ... 3 things needed - Virtual Host enabled on the NVR. Cameras must have the NVR PoE interface as the default gateway, usually 192.168.254.1 To do...

It might be worth trying this when accessing the cameras directly at their actual IP address as opposed to using the NVR NATed address. There is a way to gain normal access to cameras connected to NVR POE ports - 3 things needed - Virtual Host enabled on the NVR. Cameras must have the NVR PoE...

Assuming that you are using the NATted connection provided by the NVR Virtual Host facility : If it's the NATted access that's getting in the way of the ISAPI call, it may be worth experimenting with direct access to the cameras at their actual, not NAT, address. To do this you need 3 things...

There is a way to gain normal access to cameras connected to NVR POE ports ... 3 things needed - Virtual Host enabled on the NVR. Cameras must have the NVR PoE interface add the default gateway, or 192.168.254.1 To do this you'll need to have the PoE channel in manual mode to stop the NVR...

Yes, that's correct. For a Hikvision NVR, 3 things needed to let PoE-connected cameras access the internet so they can send email, access ntp etc. - Virtual Host enabled on the NVR. - Camera default gateway=NVR PoE interface IP address. You have this already, you have them set to 192.168.254.1...

It can also be done with cameras that are connected to NVR PoE ports, if the NVR has the 'Virtual Host' facility, and if a 'static route' is added to the LAN gateway. Multiple how-to posts on the topic. I have a 7816N-E2/8P as a primary NVR with a 7816N-E2 and a QNAP NAS both accessing the...

Do you have 13Virtual Host' enabled on the NVR. That's fine for camera web GUI access. If you want to go further, for full access: If this is 'how to access Hikvision NVR PoE-connected cameras from the LAN', there are quite a few posts on the topic. The essence is as follows:

Multiple how-to posts on this topic - example:

If you're inclined to experiment - you can access PoE-connected cameras directly on a Hikvision NVR. 3 things required : Enable 'Virtual Host' - the tick box under web GUI Network | Advanced Settings | Other. This implicitly activates the Linux kernel 'IP_forward' (not to be confused with port...

You need 3 things configured to allow Hikvision PoE-connected cameras to reach the internet: Assuming the NVR firmware is new enough to have this feature, activate 23Virtual Host'. From what I recall, it's under Network Configuration, Advanced Settings. This provides a set of direct-access links...

Does it work with any other cameras on the NVR? I have 3 non-Hik cameras on a Hikvision 7816 NVR which work OK when their HTTP port is set to 80, but not other values. What's the HTTP port on your Dahua? Assuming Virtual Host on the LTS firmware operates in the same way as the Hikvision...

That's not a valid configuration - the channel numbers don't refer to the NVR channels, I think they are used on some of the higher-end IP cameras. There are a couple of things you may be able to do. Do you need to connect the cameras to the 2nd NVR as cameras (eg with motion detection), or as...

3 things needed: First. The cameras on the PoE ports will have an invalid default gateway set - if using 'Plug30Play31 the GW will be set the same as the NVR LAN NIC. This is not accessible to the cameras - the default GW needs to be on the same subnet as the camera itself. On the assumption that...

OK, a couple of things to check. In the camera, with an internet time service such as time.windows.com set as the NTP service - check if the 32Test33 button gives 34success35. If so - that36s a good indication that both name resolution and connectivity are working OK. If not - try replacing the...

Re: Anyone changed the NVR default network to avoid static routes on router Fend/Alas I must admit I have not tried changing the NVR PoE network IP addresses to be in the same range as the LAN addresses to see what would happen. I suspect to make that work, you37d have to connect one of the PoE...

Re: email alerts to attach image on DS-7108N-SN/P or get camera to communicate outsid Yes, that38s correct. But you39ll probably need to have the PoE port configured as 'Manual' instead of 'Plug43Play' so the NVR doesn't change it back to be the same as the NVR default gateway. But you need a...

From one of a few recent discussions on that topic: And a how-to from a while back. If you have 'Virtual Host' you don't need to activate the kernel 'IP forwarding', handy as it's back to default after a reboot...

When the camera is on the separate network segment that the PoE ports use, by default it's traffic will not reach the internet. You need routing information and name resolution for that to work. I would guess that if you set an internet time source (eg time.windows.com) in the camera config, the...

Hello aster1x - I don53t mean to confuse, apologies. But I do admit that I like tinkering around with these things, so what I did on my setup may not be suitable or useful to all. But hey, it works OK for me, as my NVR is on top of some wall cupboards in a utility room on the end of a gigabit...