Question about network setup

Jconerty · Mar 31, 2016

Hello all, I have a question about setting up a Hikvision NVR on a static IP network managed by an outside IT company. I keep getting an IP conflict error message about the NIC address conflicting with the IP address. Here is the set up I am using:

IPV4 Address: 192.168.254.154
IPV4 Subnet Mask: 255.255.255.0
IPV4 Default Gateway: 192.168.254.10
MTU: 1500

Then the DNS setup is

Preferred DNS Server: 192.168.254.254
Alternate DNS Server: 192.168.254.250
Internal NIC IPV4 Address: 192.168.254.10

So this should all be okay but when I click on apply it gives me an error

"Attention: Operation failed, IPv4 addresses of device and Internal NIC conflict. Please set again."

And then is tries changing my IPv4 address to : 192.154.168.154

The way the system is set up is I have two NVRs on the same network, but I'm getting the same error for both. I had the IT company in charge of the network open up ports 80/81/8000/8001/10554/10555 to gain access to the NVRs.

Is this because the internal NIC IP is the same scheme as the external network? I have tried entering a different IP address in the NIC IPv4 spot, but still get the same error regardless. Is this something the IT company needs to change or can it be done through the NVR?

Has anyone ever run into this problem or have any ideas about how I can get around it?

Thanks in advance for the help!
Jim

nayr · Mar 31, 2016

Do you have a DHCP Server running on the network? if so and your using static configuration they can conflict with each-other as the dhcp can easily give out IP address that you've manually configured.

to use manual static configuration with a DHCP service side by side, the DHCP server must be configured to not give out any of the IP's you've reserved for manual config.

Its best now days to use DHCP Static Mapping, you get static IP's with network auto configuration.. win-win.

alastairstevenson · Apr 1, 2016

Is this because the internal NIC IP is the same scheme as the external network?

If the Hikvision NVR has PoE ports and you have not customised their IP address segment from the default 192.168.254.0/24 - the reason for the IP address conflict is that you are using the same address range for the LAN IP address segment. Hence the IP address conflict message.
On the assumption that the LAN IP address segment that you must use is fixed by the environment that you are installing the NVRs in, then you need to change the PoE ports IP address segment to be a different subnet.
In order to do this, you will need to use the HDMI/VGA interface, as the PoE network configuration is not available via the web GUI.
You won't really need to use a different range for each NVR - but it might make sense to do so should you ever need to address any devices on the NVR PoE segments.

You do need to be sure, though, what the scope of the "IP network managed by an outside IT company" is.
You've mentioned a subnet mask of 255.255.255.0 which suggests a /24 range, ie just 255 addresses in total.
In which case you could reconfigure the NVR PoE segments as:
For example - 192.168.253.0/24 and 192.168.252.0/24

Jconerty · Apr 1, 2016

Thanks you so much for the reply guys/gals: I ended up just changing the IP of the NIC Ipv4 address to 172.254.168.10, which to be honest was a total guess but it allowed my IPv4 address to stick and everything worked perfectly. I have local and remote access. I don't exactly know why it worked but it got it going and I'd love to know why so I can apply it to future jobs and add it to the knowledge bank. Any ideas are appreciated.

Thank you,
Jim

alastairstevenson · Apr 2, 2016

I ended up just changing the IP of the NIC Ipv4 address to 172.254.168.10,

Presumably this is the PoE internal NIC you've changed.

I don't exactly know why it worked but it got it going and I'd love to know why so I can apply it to future jobs and add it to the knowledge bank.

The original IP segment of the PoE ports, 192.168.254.1-254 was in conflict because the same range was in use on the LAN that you were adding the NVR to. So you could not set the NVR LAN NIC IP address to one in that range without creating an address conflict.
So by moving the PoE NIC IP address to a different segment, you were then able to match the NVR LAN NIC IP address to the network it was connected to without a conflict.
I hope that makes sense.

Stephan06 · Dec 16, 2017

alastairstevenson said:
Presumably this is the PoE internal NIC you've changed.

The original IP segment of the PoE ports, 192.168.254.1-254 was in conflict because the same range was in use on the LAN that you were adding the NVR to. So you could not set the NVR LAN NIC IP address to one in that range without creating an address conflict.
So by moving the PoE NIC IP address to a different segment, you were then able to match the NVR LAN NIC IP address to the network it was connected to without a conflict.
I hope that makes sense.

Hi I have a similar issue.

Hikvision NVR with poe network camera attached.

The NVR has a static ip address assigned from the router and I can view the cameras internally and externally just fine via the ivms app.

I am trying to us Sighthound and for that I need the rtsp stream which means the ip camera must have a static ip address in the same subnetmask ip class. Sighthound does not pick up the camera because it is in a different subnet/ip class so I must get the camera onto the same subnet /ip class just like the NVR itself. Believe me I have tried everything.

I would like to assign my ip camera a static ip address but the internal NIC of the NVR is set to 192.0.0.1
whereas the router is set to 192.168.3.2.
I get the ipconflict message if I try to change the internal nic to 192.168.3.40
I have Set the camera config from plugnplay to manual and i could assign an ip address in same class as router of 192.168.3.68 for instance but when I use the SADP tool it still show up as 192.0.0.2.

Any help appreciated.

c hris527 · Dec 16, 2017

Is this a poe NVR?, If it is your cams are running behind a subnet on your NVR, they will be invisible to you from 192.168.x.x subnet. This would explain why you can see them through your web gui and NOT from your network.

Stephan06 · Dec 16, 2017

c hris527 said:
Is this a poe NVR?, If it is your cams are running behind a subnet on your NVR, they will be invisible to you from 192.168.x.x subnet. This would explain why you can see them through your web gui and NOT from your network.

Correct , but is there a way to change the internal Ipv4 Nic address so I can assign static ip addresses via the router on the same subnet? Is there a way to use virtual host to obtain the rtsp stream to use in vlc or sighthound?

c hris527 · Dec 16, 2017

The short answer is NO, The only way to do that would be to run a cable to a open port on your NVR(the poe side) and plug that into your switch or router, then you could add another nic card or usb nic to your PC and assign it in the same IP pool as your cameras subnet. Then you should be able to access that cam directly and view your streams. In my work PC and laptops I have that setup so I can access the cams for fine tune settings and firmware upgrades.Keep in mind If you do that you will be exposing those cams to your network and if not locked down might cause some network Inflammation if you do not have them properly locked down.

alastairstevenson · Dec 17, 2017

With a Hikvision NVR with PoE ports and Virtual Host enabled, it is possible to connect directly to cameras attached to the PoE ports.
What's required is to tell the LAN gateway/router how to direct the traffic, by adding a 'static route'.
Assuming that the 'internal NIC' PoE ports IP address range is the default 192.168.254.x range, the router would need a static route added something like this :
"For network 192.168.254.0/24 (ie subnet mask 255.255.255.0) use <NVR_LAN_interface_IP_address> as the gateway."
Confirm that it works by pinging the PoE-connected camera actual address, such as 192.168.254.3, and by pointing the browser at the address.

c hris527 said:
In my work PC and laptops I have that setup so I can access the cams for fine tune settings and firmware upgrades.

On a Hikvision NVR, you can access PoE-connected cameras web GUI directly via 'Virtual Host'.

alastairstevenson · Dec 17, 2017

Stephan06 said:
Is there a way to use virtual host to obtain the rtsp stream to use in vlc or sighthound?

Hikvision NVRs offer each camera channel as an RTSP stream.
For example Channel 3, main stream : rtsp://192.168.1.211:554/Streaming/Channels/301
Channel 3, substream : rtsp://192.168.1.211:554/Streaming/Channels/302

Stephan06 · Dec 17, 2017

alastairstevenson said:
Hikvision NVRs offer each camera channel as an RTSP stream.
For example Channel 3, main stream : rtsp://192.168.1.211:554/Streaming/Channels/301
Channel 3, substream : rtsp://192.168.1.211:554/Streaming/Channels/302

Thanks alastair

Yes I carefully read through your instructions and set up static route on the dd-wrt router , which has several options wan/Lan or eth0 tried both these etc . I could then access the camera settings both ways just like your post in another thread where you described what you have to change in the router and on the camera both but then I could not connect to the internet though could access camera settings. So perhaps I must have added
another static route or ip table firewall rule which is above my head to not affect normal internat acess.

c hris527 · Dec 17, 2017

alastairstevenson said:
With a Hikvision NVR with PoE ports and Virtual Host enabled, it is possible to connect directly to cameras attached to the PoE ports.
What's required is to tell the LAN gateway/router how to direct the traffic, by adding a 'static route'.
Assuming that the 'internal NIC' PoE ports IP address range is the default 192.168.254.x range, the router would need a static route added something like this :
"For network 192.168.254.0/24 (ie subnet mask 255.255.255.0) use <NVR_LAN_interface_IP_address> as the gateway."
Confirm that it works by pinging the PoE-connected camera actual address, such as 192.168.254.3, and by pointing the browser at the address.

On a Hikvision NVR, you can access PoE-connected cameras web GUI directly via 'Virtual Host'.

I stand corrected, I use Dahua stuff thanks alastair for the info, you really are the hik guru

alastairstevenson · Dec 17, 2017

Stephan06 said:
So perhaps I must have added
another static route or ip table firewall rule which is above my head to not affect normal internat acess.

It sounds like you have replaced the routing table as opposed to adding an entry.
But you have confirmed that the camera can be made accessible, you just need to find the way to add the new route without affecting the rest.

Stephan06 · Dec 18, 2017

alastairstevenson said:
It sounds like you have replaced the routing table as opposed to adding an entry.
But you have confirmed that the camera can be made accessible, you just need to find the way to add the new route without affecting the rest.

You are the man alastair, I have it all working and can access the video stream with Sighthound.

I followed your steps on how to set the router and camera up. The problem was the static routing , in the dd-wrt router I chose Lan/Wan option but when I changed that to “Any” , I could then access the cameras on both the internal ip of the camera assigned by the nvr and the nvr ip :65001.

Thanks again for sharing your knowledge.

Took nearly a week but I got there in the end.

Thanks

alastairstevenson · Dec 18, 2017

Stephan06 said:
You are the man alastair, I have it all working and can access the video stream with Sighthound.

Excellent! That's a good result, thanks for sharing, it will help others.

Stephan06 · Jun 22, 2018

Had to configure a new router so here is how I was able to set it up to be able to have access to the camera video stream via the hikvision NVR:
On the NVR
- enable virtual host on the nvr configuration page
- note down the Internal NIC address of the nvr ie 192.0.5.1
- note down the camera ip addressed assigned to the camera an what channel
- note down the static ip of your nvr ie 192.168.1.10
- note down gateway of your router ( on router)

On the router (dd-wrt)
- setup>advanced routing
> give the route a name
> destination LAN NET the would be 192.0.5.0
> subnet mask: 255.255.255.0
> gateway : 192.168.1.10
> interface : Any

In the rtsp video stream url You need to use the ip address of the camera that is assigned by the NVR to the camera ie 192.0.5.2 which is the first camera on the list and thus on channel 1 and make sure you have changed the default password of the actual ip camera as this is the ip address and password you will use to access the video stream. Again change the default password of the camera and write it down!!!!

Save-Apply and then reboot the router

I can now access the video stream in ispy.

Hope this helps anyone having trouble setting it up / I know I did.

slavany · Dec 26, 2018

Stephan06 said:
Had to configure a new router so here is how I was able to set it up to be able to have access to the camera video stream via the hikvision NVR:
On the NVR
- enable virtual host on the nvr configuration page
- note down the Internal NIC address of the nvr ie 192.0.5.1
- note down the camera ip addressed assigned to the camera an what channel
- note down the static ip of your nvr ie 192.168.1.10
- note down gateway of your router ( on router)

On the router (dd-wrt)
- setup>advanced routing
> give the route a name
> destination LAN NET the would be 192.0.5.0
> subnet mask: 255.255.255.0
> gateway : 192.168.1.10
> interface : Any

In the rtsp video stream url You need to use the ip address of the camera that is assigned by the NVR to the camera ie 192.0.5.2 which is the first camera on the list and thus on channel 1 and make sure you have changed the default password of the actual ip camera as this is the ip address and password you will use to access the video stream. Again change the default password of the camera and write it down!!!!

Save-Apply and then reboot the router

I can now access the video stream in ispy.

Hope this helps anyone having trouble setting it up / I know I did.

Can you please post what your rtsp string looks like. I can't get it to work. Thanks

alastairstevenson · Dec 27, 2018

slavany said:
Can you please post what your rtsp string looks like. I can't get it to work.

For what camera or NVR, and for what video player?
What have you tried so far?

Example for Hikvision NVR :

alastairstevenson said:
Hikvision NVRs offer each camera channel as an RTSP stream.
For example Channel 3, main stream : rtsp://192.168.1.211:554/Streaming/Channels/301
Channel 3, substream : rtsp://192.168.1.211:554/Streaming/Channels/302

Search

Question about network setup

Jconerty

n3wb

nayr

alastairstevenson

Jconerty

n3wb

alastairstevenson

Stephan06

Young grasshopper

c hris527

Known around here

Stephan06

Young grasshopper

c hris527

Known around here

alastairstevenson

alastairstevenson

Stephan06

Young grasshopper

c hris527

Known around here

alastairstevenson

Stephan06

Young grasshopper

alastairstevenson

Stephan06

Young grasshopper

slavany

n3wb

alastairstevenson