Hikvision DS-7616NI-SE/P Firmware Update

[alastairstevenson]

If you have the 'Virtual Host' facility - and you indicated that you do - you shouldn't need to use all this fiddly stuff and get frustrated by it ...

And to your last question - yes, the PoE cameras are fully accessible, including the ability to mess with their internal over SSH, for example:
192.168.1.99 is the PC I'm using for access. 192.168.1.201 is the QNAP NAS box running Surveillance Station, recording the camera's video stream and motion detection alerts.

login as: admin
admin@192.168.254.11's password:

BusyBox v1.19.3 (2014-07-11 11:25:54 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# ifconfig
eth0 Link encap:Ethernet HWaddr C0:56:E3:83:A5:A3
inet addr:192.168.254.11 Bcast:192.168.254.255 Mask:255.255.255.0
inet6 addr: fe80::c256:e3ff:fe83:a5a3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:387711973 errors:0 dropped:24 overruns:0 frame:0
TX packets:419853955 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2520240141 (2.3 GiB) TX bytes:2416335378 (2.2 GiB)
Interrupt:27
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:390 errors:0 dropped:0 overruns:0 frame:0
TX packets:390 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:29640 (28.9 KiB) TX bytes:29640 (28.9 KiB)
# netstat -a
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:9010 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:telnet 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:7001 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9020 0.0.0.0:* LISTEN
tcp 0 52 192.168.254.11:22 192.168.1.99:9058 ESTABLISHED
tcp 0 0 :::8000 :::* LISTEN
tcp 0 0 :::8200 :::* LISTEN
tcp 0 0 :::554 :::* LISTEN
tcp 0 0 :::22 :::* LISTEN
tcp 0 0 :::90 :::* LISTEN
tcp 0 0 :::443 :::* LISTEN
tcp 0 0 ::ffff:192.168.254.11:554 ::ffff:192.168.254.1:35529 ESTABLISHED
tcp 0 0 ::ffff:192.168.254.11:554 ::ffff:192.168.1.201:47178 ESTABLISHED
tcp 0 0 ::ffff:192.168.254.11:90 ::ffff:192.168.1.201:60058 ESTABLISHED
tcp 0 0 ::ffff:192.168.254.11:554 ::ffff:192.168.254.1:57013 ESTABLISHED
tcp 0 0 ::ffff:192.168.254.11:8000 ::ffff:192.168.254.1:39253 ESTABLISHED
udp 0 0 0.0.0.0:47872 0.0.0.0:*
udp 0 0 0.0.0.0:3702 0.0.0.0:*
udp 0 0 0.0.0.0:5353 0.0.0.0:*
udp 0 0 :::3702 :::*
udp 0 0 :::47771 :::*
udp 0 0 :::5353 :::*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ] DGRAM 45 @/org/kernel/udev/udevd
unix 2 [ ACC ] STREAM LISTENING 1625 /var/g_daemon_service
unix 2 [ ACC ] STREAM LISTENING 1629 /var/systemCmd.socket
unix 3 [ ] STREAM CONNECTED 1631 /var/net_worker_process
unix 3 [ ] STREAM CONNECTED 1686 /var/davinci_work_process
unix 2 [ ACC ] STREAM LISTENING 2835 /tmp/aaa
unix 2 [ ] DGRAM 2917 /var/run/wpa_supplicant/eth0
unix 3 [ ] STREAM CONNECTED 1632 /var/g_daemon_service
unix 3 [ ] STREAM CONNECTED 1626 /var/g_daemon_service
#

 

[aster1x]

As I said I cannot telnet to the cameras connected to the NVR.
The ifconfig and netstat you send me is from your camera. Can you please send me the same from your NVR?

 

[aster1x]

This is my netstat -r from within my NVR. If I interpret it correctly the poe interface 192.168.254.0 does not have a gateway. Am I correct?

Can you please remind me how to add the route manually from the command line?

# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
192.168.254.0 * 255.255.255.0 U 0 0 0 poe0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
#

 

[alastairstevenson]

NVR routing table (snap!) and interface config as requested:

dvrdvs login: root
Password:

BusyBox v1.16.1 (2014-05-19 09:41:10 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
can not change to guest!
[root@dvrdvs /] # route -e
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.254.0 * 255.255.255.0 U 0 0 0 eth0
224.0.0.0 * 240.0.0.0 U 0 0 0 eth1
[root@dvrdvs /] # ifconfig
eth0 Link encap:Ethernet HWaddr 8C:E7:48:6F:81:28
inet addr:192.168.254.1 Bcast:192.168.254.255 Mask:255.255.255.0
inet6 addr: fe80::8ee7:48ff:fe6f:8128/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1476500466 errors:0 dropped:0 overruns:0 frame:0
TX packets:252705634 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3427437587 (3.1 GiB) TX bytes:175862076 (167.7 MiB)
Interrupt:59
eth1 Link encap:Ethernet HWaddr 8C:E7:48:6F:81:27
inet addr:192.168.1.210 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::8ee7:48ff:fe6f:8127/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:947332339 errors:0 dropped:682 overruns:0 frame:0
TX packets:591354207 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2348566756 (2.1 GiB) TX bytes:3015876849 (2.8 GiB)
Interrupt:59 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1766 errors:0 dropped:0 overruns:0 frame:0
TX packets:1766 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:301040 (293.9 KiB) TX bytes:301040 (293.9 KiB)
[root@dvrdvs /] #

 

[aster1x]

Now the NVR started forwarding camera traffic through the NVR LAN port to the LAN !!!!!
This is very weird. I will let it work for the tonight and see tomorrow.

Thanks alastair.