Please help me to install a Hikvision 2032-I under Ubuntu

empedokles · August 12, 2014

The Hikvision model is DS-2CD2032-I and it is powered with PoE over my Motorola Internet-Router (I could see IR-Leds on after I connected the cable, they went off after some time). I installed arp-scan and below is what I can find in the terminal. Tatung Company is my digital TV-box and not the IP-cam.

nuc@nuc:~$ sudo arp-scan --localnet
Interface: eth0, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.8.1 with 256 hosts (http://www.nta-monitor.com/tools/arp-scan/)
192.168.1.1 00:22:10:82:61:40   Motorola Mobility, Inc.
192.168.1.33    00:80:3f:3a:d6:79   TATUNG COMPANY
192.168.1.38    84:a6:c8:c3:2b:e3   (Unknown)

3 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.8.1: 256 hosts scanned in 1.467 seconds (174.51 hosts/sec). 3 responded
nuc@nuc:~$

CBX · August 12, 2014

How about

ifconfig eth0:0 192.0.0.128
ping 192.0.0.64

?

Make sure your firewall isn't blocking anything on that interface

empedokles · August 12, 2014

nuc@nuc:~$ ifconfig eth0:0 192.0.0.128
SIOCSIFADDR: Operation is not allowed
SIOCSIFFLAGS: Operation is not allowed
nuc@nuc:~$ sudo ifconfig eth0:0 192.0.0.128
[sudo] password for nuc: 
nuc@nuc:~$

and

PING 192.0.0.64 (192.0.0.64) 56(84) bytes of data.
64 bytes from 192.0.0.64: icmp_seq=1 ttl=64 time=2.80 ms
64 bytes from 192.0.0.64: icmp_seq=2 ttl=64 time=1.14 ms
64 bytes from 192.0.0.64: icmp_seq=3 ttl=64 time=1.14 ms
64 bytes from 192.0.0.64: icmp_seq=4 ttl=64 time=1.14 ms
64 bytes from 192.0.0.64: icmp_seq=5 ttl=64 time=1.11 ms
64 bytes from 192.0.0.64: icmp_seq=6 ttl=64 time=1.02 ms
64 bytes from 192.0.0.64: icmp_seq=7 ttl=64 time=1.13 ms
64 bytes from 192.0.0.64: icmp_seq=8 ttl=64 time=1.12 ms
64 bytes from 192.0.0.64: icmp_seq=9 ttl=64 time=1.10 ms
64 bytes from 192.0.0.64: icmp_seq=10 ttl=64 time=1.16 ms
64 bytes from 192.0.0.64: icmp_seq=11 ttl=64 time=1.12 ms
64 bytes from 192.0.0.64: icmp_seq=12 ttl=64 time=1.12 ms
64 bytes from 192.0.0.64: icmp_seq=13 ttl=64 time=1.20 ms
64 bytes from 192.0.0.64: icmp_seq=14 ttl=64 time=1.11 ms
64 bytes from 192.0.0.64: icmp_seq=15 ttl=64 time=1.10 ms
64 bytes from 192.0.0.64: icmp_seq=16 ttl=64 time=1.11 ms
64 bytes from 192.0.0.64: icmp_seq=17 ttl=64 time=1.08 m
..

..goes on forever

Is there an integrated firewall in Ubuntu? I guess not. I haven't a Hardwarefirewall.

Edited August 12, 2014 by Guest

CBX · August 12, 2014

This is a successful test - you can ping the camera (192.0.0.64) OK.

Just connect to the web page and configure.

empedokles · August 12, 2014

Wow, brilliant. Thank you. Now it's all Chinese. Where do I set the language? It seems I can't?

Maybe this will help you:

Web: 3.1.3.140318

Plugin: 3.0.5.10

Edited August 12, 2014 by Guest

mkkoskin · August 12, 2014

To explain this to op and anyone else reading this:

In the beginning OP has a 192.168.1.0 network and PC in this network (probably the 192.168.1.38 IP). By default Hikvision cameras have static IP 192.0.0.64.

So since (i assume) this is a small home network, there is no network management inbetween, and connecting from 192.168.1.0 network to 192.0.0.0 network is impossible.

The command CBX gave makes a virtual NIC on top of the physical one, with IP 192.0.0.128, which can be used to connect to the camera at 192.0.0.64.

empedokles · August 12, 2014

And why can it be used? Isn't it still in a different network? 192.0.0.128

Connecting to 192.0.0.64 over my browser did work out. The problem I have now, is that there is obvisiously a Chinese firmware on this aliexpresss-cam and I can't switch it to English.

buellwinkle · August 12, 2014

You do know that you can't see the live stream through the web interface on Linux right? And yes, you put your PC IP in that subnet, use that to change the IP of the camera to your home network, then change your PC back to your home network because the SADP program most people use to do this is only on Windows. Of course if you have access to a Windows system, you can run SADP and set the IP address using their tool, much easier.

empedokles · August 12, 2014

You do know that you can't see the live stream through the web interface on Linux right?

? - But I can see it.

BTW: Maybe I just hit the reset button. However: I now see the firmware in English.

Which IP shall I use? And can I leave the subnet and prefered DNS entries?

buellwinkle · August 12, 2014

That's great. Last I heard the plugin did not work with Linux, but maybe they fixed that. For IP, you likely have a home router with other devices on it. That has a subnet (the first 3 numbers in an IP address) that you use. For example, if you use DHCP assign the IP, you could run the ifconfig -a command on Linux or OSX to see what IP, gateway and subnet mask are for your router. If it's Windows, it's ipconfig. You'll see something like say 192.168.1.12 for the PC, then make the camera something with the first 3 numbers, the last number can be 1-254, so make it high to avoid any conflict with DHCP like 100 or 200.

empedokles · August 12, 2014

use that to change the IP of the camera to your home network

This was a pretty dangerous advice. After setting the camera to 192.164.1.41 I lost my camera completely. I tried the reset button on camera, but CBX advice won't work anymore:

nuc@nuc:~$ sudo ifconfig eth0:0 192.0.0.128
[sudo] password for nuc: 
nuc@nuc:~$ ping 192.0.0.64
PING 192.0.0.64 (192.0.0.64) 56(84) bytes of data.
From 192.0.0.128 icmp_seq=1 Destination Host Unreachable
From 192.0.0.128 icmp_seq=2 Destination Host Unreachable
From 192.0.0.128 icmp_seq=3 Destination Host Unreachable
From 192.0.0.128 icmp_seq=4 Destination Host Unreachable
From 192.0.0.128 icmp_seq=5 Destination Host Unreachable
From 192.0.0.128 icmp_seq=6 Destination Host Unreachable
From 192.0.0.128 icmp_seq=7 Destination Host Unreachable
From 192.0.0.128 icmp_seq=8 Destination Host Unreachable
From 192.0.0.128 icmp_seq=9 Destination Host Unreachable
From 192.0.0.128 icmp_seq=10 Destination Host Unreachable
From 192.0.0.128 icmp_seq=11 Destination Host Unreachable
From 192.0.0.128 icmp_seq=12 Destination Host Unreachable

When I unconnect ethernet and reconnect on the PoE-Injector I will receive:

From 192.0.0.128 icmp_seq=138 Destination Host Unreachable
From 192.0.0.128 icmp_seq=139 Destination Host Unreachable
64 bytes from 192.0.0.128: icmp_seq=142 ttl=255 time=626 ms
64 bytes from 192.0.0.128: icmp_seq=143 ttl=255 time=0.678 ms
64 bytes from 192.0.0.128: icmp_seq=144 ttl=255 time=0.708 ms
From 192.0.0.128 icmp_seq=177 Destination Host Unreachable

But soon after it looses the connection again.

Edited August 12, 2014 by Guest

empedokles · August 12, 2014

Okay I could reset the camera with that 10 second reset push-advice in another thread. Now I can access it again.

My router is accessable over 192.168.1.1. here some images of my network:

nuc@nuc:~$ ifconfig -a
eth0      Link encap:Ethernet  Hardware Adresse c0:3f:d5:64:0a:2f  
         inet Adresse:192.168.1.41  Bcast:192.168.1.255  Maske:255.255.255.0
         inet6-Adresse: fe80::c23f:d5ff:fe64:a2f/64 Gültigkeitsbereich:Verbindung
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
         RX-Pakete:5709 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
         TX-Pakete:5365 Fehler:0 Verloren:0 Überläufe:0 Träger:0
         Kollisionen:0 Sendewarteschlangenlänge:1000 
         RX-Bytes:3005952 (3.0 MB)  TX-Bytes:711040 (711.0 KB)
         Interrupt:20 Speicher:f7c00000-f7c20000 

lo        Link encap:Lokale Schleife  
         inet Adresse:127.0.0.1  Maske:255.0.0.0
         inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
         UP LOOPBACK RUNNING  MTU:65536  Metrik:1
         RX-Pakete:990 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
         TX-Pakete:990 Fehler:0 Verloren:0 Überläufe:0 Träger:0
         Kollisionen:0 Sendewarteschlangenlänge:0 
         RX-Bytes:83885 (83.8 KB)  TX-Bytes:83885 (83.8 KB)

Edited August 12, 2014 by Guest

empedokles · August 12, 2014

I tried to give my camera the IP 192.168.1.100, which seemed to work after a reboot I could spot it.

Unfortunately I can't access it over my browser though:

nuc@nuc:~$ sudo arp-scan --localnet
[sudo] password for nuc: 
Interface: eth0, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.8.1 with 256 hosts (http://www.nta-monitor.com/tools/arp-scan/)
192.168.1.1	00:22:10:82:61:40	Motorola Mobility, Inc.
192.168.1.33	00:80:3f:3a:d6:79	TATUNG COMPANY
192.168.1.35	d0:66:7b:9e:1f:ad	(Unknown)
192.168.1.38	84:a6:c8:c3:2b:e3	(Unknown)
192.168.1.100	44:19:b6:2d:13:a8	(Unknown)

5 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.8.1: 256 hosts scanned in 1.474 seconds (173.68 hosts/sec). 5 responded
nuc@nuc:~$ ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=1.20 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=1.00 ms
64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=1.06 ms
From 192.168.1.100 icmp_seq=34 Destination Host Unreachable
From 192.168.1.100 icmp_seq=38 Destination Host Unreachable
From 192.168.1.100 icmp_seq=39 Destination Host Unreachable
From 192.168.1.100 icmp_seq=40 Destination Host Unreachable
From 192.168.1.100 icmp_seq=41 Destination Host Unreachable
64 bytes from 192.168.1.100: icmp_seq=42 ttl=64 time=2287 ms
64 bytes from 192.168.1.100: icmp_seq=43 ttl=64 time=1287 ms
64 bytes from 192.168.1.100: icmp_seq=44 ttl=64 time=287 ms
64 bytes from 192.168.1.100: icmp_seq=45 ttl=64 time=0.889 ms
64 bytes from 192.168.1.100: icmp_seq=46 ttl=64 time=0.946 ms
64 bytes from 192.168.1.100: icmp_seq=47 ttl=64 time=0.889 ms
64 bytes from 192.168.1.100: icmp_seq=48 ttl=64 time=0.891 ms
64 bytes from 192.168.1.100: icmp_seq=49 ttl=64 time=1.07 ms
64 bytes from 192.168.1.100: icmp_seq=50 ttl=64 time=1.07 ms
64 bytes from 192.168.1.100: icmp_seq=51 ttl=64 time=1.40 ms
64 bytes from 192.168.1.100: icmp_seq=52 ttl=64 time=1.27 ms
64 bytes from 192.168.1.100: icmp_seq=53 ttl=64 time=1.12 ms
64 bytes from 192.168.1.100: icmp_seq=54 ttl=64 time=1.11 ms
64 bytes from 192.168.1.100: icmp_seq=55 ttl=64 time=1.08 ms
64 bytes from 192.168.1.100: icmp_seq=56 ttl=64 time=1.14 ms
64 bytes from 192.168.1.100: icmp_seq=57 ttl=64 time=1.26 ms
64 bytes from 192.168.1.100: icmp_seq=58 ttl=64 time=1.09 ms
64 bytes from 192.168.1.100: icmp_seq=59 ttl=64 time=0.996 ms
64 bytes from 192.168.1.100: icmp_seq=60 ttl=64 time=0.896 ms
64 bytes from 192.168.1.100: icmp_seq=61 ttl=64 time=1.24 ms
64 bytes from 192.168.1.100: icmp_seq=62 ttl=64 time=1.08 ms
64 bytes from 192.168.1.100: icmp_seq=63 ttl=64 time=1.08 ms
64 bytes from 192.168.1.100: icmp_seq=64 ttl=64 time=1.13 ms
64 bytes from 192.168.1.100: icmp_seq=65 ttl=64 time=0.943 ms
64 bytes from 192.168.1.100: icmp_seq=66 ttl=64 time=1.12 ms
64 bytes from 192.168.1.100: icmp_seq=67 ttl=64 time=1.33 ms
64 bytes from 192.168.1.100: icmp_seq=68 ttl=64 time=1.04 ms
64 bytes from 192.168.1.100: icmp_seq=69 ttl=64 time=1.03 ms
64 bytes from 192.168.1.100: icmp_seq=70 ttl=64 time=0.886 ms
64 bytes from 192.168.1.100: icmp_seq=71 ttl=64 time=1.18 ms
64 bytes from 192.168.1.100: icmp_seq=72 ttl=64 time=1.08 ms
64 bytes from 192.168.1.100: icmp_seq=73 ttl=64 time=0.885 ms
64 bytes from 192.168.1.100: icmp_seq=74 ttl=64 time=1.04 ms
64 bytes from 192.168.1.100: icmp_seq=75 ttl=64 time=0.979 ms
64 bytes from 192.168.1.100: icmp_seq=76 ttl=64 time=1.09 ms
64 bytes from 192.168.1.100: icmp_seq=77 ttl=64 time=0.885 ms
64 bytes from 192.168.1.100: icmp_seq=78 ttl=64 time=1.02 ms
64 bytes from 192.168.1.100: icmp_seq=79 ttl=64 time=0.884 ms
64 bytes from 192.168.1.100: icmp_seq=80 ttl=64 time=0.998 ms
64 bytes from 192.168.1.100: icmp_seq=81 ttl=64 time=0.944 ms
64 bytes from 192.168.1.100: icmp_seq=82 ttl=64 time=0.932 ms
64 bytes from 192.168.1.100: icmp_seq=83 ttl=64 time=0.932 ms
64 bytes from 192.168.1.100: icmp_seq=84 ttl=64 time=0.958 ms
64 bytes from 192.168.1.100: icmp_seq=85 ttl=64 time=1.18 ms
64 bytes from 192.168.1.100: icmp_seq=86 ttl=64 time=1.03 ms
^C
--- 192.168.1.100 ping statistics ---
93 packets transmitted, 48 received, +5 errors, 48% packet loss, time 92076ms
rtt min/avg/max/mdev = 0.884/81.446/2287.235/372.298 ms, pipe 4

(interestingly the PoE injector seems to get it's own IP?)

buellwinkle · August 12, 2014

What's the IP address of your router, because on your PC it shows 192.168.1.255, if that's it, make sure you specify that in your camera as the gateway address.

empedokles · August 12, 2014

What's the IP address of your router, because on your PC it shows 192.168.1.255, if that's it, make sure you specify that in your camera as the gateway address.

Where do you read this? I can access my routers webinterface over: 192.168.1.1

Is that it?

mkkoskin · August 13, 2014

If you just want the camera installed locally, no internet access from/to it, you dont need to set the gateway for the camera at all.

The first time you tried to change the ip and lost the camera so you had to reset it, was because you gave it an address from wrong subnet. Your home network is 192.168.1.* and you gave your camera 192.164.1.41.

ipconfig -a does not show the default gateway, "route -n" does, look for a line that says 0.0.0.0 under Destination.

Judging from what you've posted so far:

Your PC:

IP: 192.168.1.41

Netmask: 255.255.255.0

Gateway: 192.168.1.1 (Indeed, this is the router ip you used, not the broadcast address from ifconfig -a print)

So camera ip settings should be for example:

IP: 192.168.1.100

Netmask: 255.255.255.0

Gateway: 192.168.1.1 (this is optional, only required if you want the camera to have a connection to internet, rather than LAN only)

Since you can ping the camera, you should be able to access it thru browser aswell.

empedokles · August 13, 2014

So camera ip settings should be for example:

IP: 192.168.1.100

Netmask: 255.255.255.0

Gateway: 192.168.1.1 (this is optional, only required if you want the camera to have a connection to internet, rather than LAN only)

Hello mkkoskin

Yes, I've found out about my 164-error when I did change it the first time. That my change to IP: 192.168.1.100 (can't access it over a browser) didn't work out the second time though, seems strange. If I remember correctly, the netmask was set to 255.255.255.0 already.

nuc@nuc:~$ route -n
Kernel-IP-Routentabelle
Destination   Router          Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
192.168.1.0     0.0.0.0         255.255.255.0   U     1      0        0 eth0
nuc@nuc:~$

Do you mean by a connection to the internet, that I could include my cam in a website? This would indeed be preferable, because it's a birdy-cam.

Edited August 13, 2014 by Guest

empedokles · August 13, 2014

Went over everything again (Camera-Reset, IP-altering). Here are two screenshots how the admin panel looked originally and a third one with the changes (first image) I made.

After a reboot of my NUC it appears two times(?). I still can't access it over my browser though:

nuc@nuc:~$ sudo arp-scan --localnet
[sudo] password for nuc: 
Interface: eth0, datalink type: EN10MB (Ethernet)
Starting arp-scan 1.8.1 with 256 hosts (http://www.nta-monitor.com/tools/arp-scan/)
192.168.1.1	00:22:10:82:61:40	Motorola Mobility, Inc.
192.168.1.33	00:80:3f:3a:d6:79	TATUNG COMPANY
192.168.1.100	44:19:b6:2d:13:a8	(Unknown)
192.168.1.100	44:19:b6:2d:13:a8	(Unknown) (DUP: 2)

4 packets received by filter, 0 packets dropped by kernel
Ending arp-scan 1.8.1: 256 hosts scanned in 1.519 seconds (168.53 hosts/sec). 4 responded
nuc@nuc:~$

And if I ping it it gives me the IP of my computer (192.168.1.41) back:

nuc@nuc:~$ ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
From 192.168.1.41 icmp_seq=10 Destination Host Unreachable
From 192.168.1.41 icmp_seq=11 Destination Host Unreachable
From 192.168.1.41 icmp_seq=12 Destination Host Unreachable
From 192.168.1.41 icmp_seq=13 Destination Host Unreachable
From 192.168.1.41 icmp_seq=14 Destination Host Unreachable
From 192.168.1.41 icmp_seq=17 Destination Host Unreachable
From 192.168.1.41 icmp_seq=18 Destination Host Unreachable
From 192.168.1.41 icmp_seq=22 Destination Host Unreachable
From 192.168.1.41 icmp_seq=23 Destination Host Unreachable
From 192.168.1.41 icmp_seq=24 Destination Host Unreachable
From 192.168.1.41 icmp_seq=25 Destination Host Unreachable
From 192.168.1.41 icmp_seq=26 Destination Host Unreachable
From 192.168.1.41 icmp_seq=27 Destination Host Unreachable
From 192.168.1.41 icmp_seq=30 Destination Host Unreachable
From 192.168.1.41 icmp_seq=31 Destination Host Unreachable
From 192.168.1.41 icmp_seq=32 Destination Host Unreachable
From 192.168.1.41 icmp_seq=35 Destination Host Unreachable
64 bytes from 192.168.1.41: icmp_seq=36 ttl=64 time=1738 ms
64 bytes from 192.168.1.41: icmp_seq=37 ttl=64 time=738 ms
64 bytes from 192.168.1.41: icmp_seq=38 ttl=64 time=1.00 ms
64 bytes from 192.168.1.41: icmp_seq=39 ttl=64 time=0.913 ms
64 bytes from 192.168.1.41: icmp_seq=40 ttl=64 time=0.931 ms
64 bytes from 192.168.1.41: icmp_seq=41 ttl=64 time=0.916 ms
64 bytes from 192.168.1.41: icmp_seq=42 ttl=64 time=0.916 ms
64 bytes from 192.168.1.41: icmp_seq=43 ttl=64 time=0.998 ms
64 bytes from 192.168.1.41: icmp_seq=44 ttl=64 time=1.28 ms
64 bytes from 192.168.1.41: icmp_seq=45 ttl=64 time=1.28 ms
64 bytes from 192.168.1.41: icmp_seq=46 ttl=64 time=1.29 ms
64 bytes from 192.168.1.41: icmp_seq=47 ttl=64 time=1.14 ms
64 bytes from 192.168.1.41: icmp_seq=48 ttl=64 time=1.15 ms
64 bytes from 192.168.1.41: icmp_seq=49 ttl=64 time=1.11 ms
64 bytes from 192.168.1.41: icmp_seq=50 ttl=64 time=1.12 ms
64 bytes from 192.168.1.41: icmp_seq=51 ttl=64 time=1.09 ms
64 bytes from 192.168.1.41: icmp_seq=52 ttl=64 time=1.29 ms
64 bytes from 192.168.1.41: icmp_seq=53 ttl=64 time=0.941 ms
64 bytes from 192.168.1.41: icmp_seq=54 ttl=64 time=0.923 ms
64 bytes from 192.168.1.41: icmp_seq=55 ttl=64 time=0.930 ms
64 bytes from 192.168.1.41: icmp_seq=56 ttl=64 time=1.09 ms
64 bytes from 192.168.1.41: icmp_seq=57 ttl=64 time=1.18 ms
64 bytes from 192.168.1.41: icmp_seq=58 ttl=64 time=0.923 ms
64 bytes from 192.168.1.41: icmp_seq=59 ttl=64 time=1.09 ms
64 bytes from 192.168.1.41: icmp_seq=60 ttl=64 time=0.921 ms
64 bytes from 192.168.1.41: icmp_seq=61 ttl=64 time=1.09 ms
64 bytes from 192.168.1.41: icmp_seq=62 ttl=64 time=0.915 ms
64 bytes from 192.168.1.41: icmp_seq=63 ttl=64 time=0.997 ms
64 bytes from 192.168.1.41: icmp_seq=64 ttl=64 time=0.915 ms
64 bytes from 192.168.1.41: icmp_seq=65 ttl=64 time=0.908 ms
64 bytes from 192.168.1.41: icmp_seq=66 ttl=64 time=0.986 ms
64 bytes from 192.168.1.41: icmp_seq=67 ttl=64 time=0.923 ms
64 bytes from 192.168.1.41: icmp_seq=68 ttl=64 time=1.07 ms
64 bytes from 192.168.1.41: icmp_seq=69 ttl=64 time=0.905 ms
64 bytes from 192.168.1.41: icmp_seq=70 ttl=64 time=1.11 ms
64 bytes from 192.168.1.41: icmp_seq=71 ttl=64 time=0.913 ms
64 bytes from 192.168.1.41: icmp_seq=72 ttl=64 time=1.13 ms
64 bytes from 192.168.1.41: icmp_seq=73 ttl=64 time=0.998 ms
64 bytes from 192.168.1.41: icmp_seq=74 ttl=64 time=0.924 ms
64 bytes from 192.168.1.41: icmp_seq=75 ttl=64 time=1.09 ms
64 bytes from 192.168.1.41: icmp_seq=76 ttl=64 time=0.923 ms

A second ping gave:

nuc@nuc:~$ ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100) 56(84) bytes of data.
64 bytes from 192.168.1.100: icmp_seq=1 ttl=64 time=5.66 ms
64 bytes from 192.168.1.100: icmp_seq=2 ttl=64 time=0.974 ms
64 bytes from 192.168.1.100: icmp_seq=3 ttl=64 time=1.09 ms
64 bytes from 192.168.1.100: icmp_seq=4 ttl=64 time=1.14 ms
64 bytes from 192.168.1.100: icmp_seq=5 ttl=64 time=1.29 ms
64 bytes from 192.168.1.100: icmp_seq=6 ttl=64 time=1.11 ms
64 bytes from 192.168.1.100: icmp_seq=7 ttl=64 time=1.10 ms
64 bytes from 192.168.1.100: icmp_seq=8 ttl=64 time=1.09 ms
64 bytes from 192.168.1.100: icmp_seq=9 ttl=64 time=1.13 ms
64 bytes from 192.168.1.100: icmp_seq=10 ttl=64 time=1.16 ms
64 bytes from 192.168.1.100: icmp_seq=11 ttl=64 time=1.09 ms
64 bytes from 192.168.1.100: icmp_seq=12 ttl=64 time=1.13 ms
64 bytes from 192.168.1.100: icmp_seq=13 ttl=64 time=1007 ms
64 bytes from 192.168.1.100: icmp_seq=14 ttl=64 time=1.12 ms
64 bytes from 192.168.1.100: icmp_seq=15 ttl=64 time=1.14 ms
64 bytes from 192.168.1.100: icmp_seq=16 ttl=64 time=1.10 ms
64 bytes from 192.168.1.100: icmp_seq=17 ttl=64 time=1.19 ms
64 bytes from 192.168.1.100: icmp_seq=18 ttl=64 time=1.09 ms
64 bytes from 192.168.1.100: icmp_seq=19 ttl=64 time=0.944 ms
64 bytes from 192.168.1.100: icmp_seq=20 ttl=64 time=0.913 ms
64 bytes from 192.168.1.100: icmp_seq=21 ttl=64 time=0.881 ms
64 bytes from 192.168.1.100: icmp_seq=22 ttl=64 time=0.931 ms
64 bytes from 192.168.1.100: icmp_seq=23 ttl=64 time=0.907 ms
64 bytes from 192.168.1.100: icmp_seq=24 ttl=64 time=1.03 ms
64 bytes from 192.168.1.100: icmp_seq=25 ttl=64 time=0.921 ms
64 bytes from 192.168.1.100: icmp_seq=26 ttl=64 time=1.15 ms
64 bytes from 192.168.1.100: icmp_seq=27 ttl=64 time=0.910 ms
64 bytes from 192.168.1.100: icmp_seq=28 ttl=64 time=1.09 ms
64 bytes from 192.168.1.100: icmp_seq=29 ttl=64 time=0.923 ms
64 bytes from 192.168.1.100: icmp_seq=30 ttl=64 time=0.921 ms
64 bytes from 192.168.1.100: icmp_seq=31 ttl=64 time=1.06 ms
64 bytes from 192.168.1.100: icmp_seq=32 ttl=64 time=0.959 ms
64 bytes from 192.168.1.100: icmp_seq=33 ttl=64 time=0.898 ms
64 bytes from 192.168.1.100: icmp_seq=34 ttl=64 time=0.921 ms
64 bytes from 192.168.1.100: icmp_seq=76 ttl=64 time=3.25 ms
64 bytes from 192.168.1.100: icmp_seq=77 ttl=64 time=0.833 ms
64 bytes from 192.168.1.100: icmp_seq=78 ttl=64 time=0.856 ms
64 bytes from 192.168.1.100: icmp_seq=79 ttl=64 time=0.855 ms
64 bytes from 192.168.1.100: icmp_seq=80 ttl=64 time=0.836 ms
64 bytes from 192.168.1.100: icmp_seq=81 ttl=64 time=0.843 ms
64 bytes from 192.168.1.100: icmp_seq=82 ttl=64 time=22.6 ms
^C
--- 192.168.1.100 ping statistics ---
82 packets transmitted, 41 received, 50% packet loss, time 81030ms
rtt min/avg/max/mdev = 0.833/26.261/1007.537/155.190 ms, pipe 2

Won't I have to change eth0 back to something else? I remember that I had to change it from what CBX told me with:

nuc@nuc:~$ sudo ifconfig eth0:0 192.0.0.128

mkkoskin · August 13, 2014

No idea why the camera shows up 2 times in the arp-scan, usually thats the case only if it has 2 different IPs.

Won't I have to change eth0 back to something else? I remember that I had to change it from what CBX told me with:
nuc@nuc:~$ sudo ifconfig eth0:0 192.0.0.128

No, this was only a temporary "virtual ip/nic".

eth0 = your physical NIC

eth0:0 = the first virtual ip/nic of the physical device

Every setting seems to be ok now. Ping seems to go thru just fine on the second try.

I have no idea why you cant access the camera over a browser, what does the browser say?

What does "nmap 192.168.1.100" tell you? (you might have to install nmap, "sudo apt-get install nmap")

Also what are you trying to do with this NUC+Ubuntu+Hikvision combo?

Do you mean by a connection to the internet, that I could include my cam in a website? This would indeed be preferable, because it's a birdy-cam.

Without gateway, the camera cannot connect to WAN, thus has no access/visibility to the internet, outside your LAN. If your website is in your LAN (some local webserver that is already visible from internet), you dont need gateway for camera, if not, you probably do.

One last step to try is after you've set up the ip to camera (192.168.1.100) is to reboot both devices, just to make sure the virtual ip does not interfere with the setup. Then see if browser connection works.

empedokles · August 13, 2014

No, this was only a temporary "virtual ip/nic".
eth0 = your physical NIC

eth0:0 = the first virtual ip/nic of the physical device

I see, so it's lost on reboot.

I have no idea why you cant access the camera over a browser, what does the browser say?

I receive follwing screen in Firefox. It translates to:

Error: Connection failed

Firefox can not establish a connection to server 192.168.1.100.

This website could not be reachable temporarily, please try later.

If you can't connect to other website, check your network/internetconnection.

If your computer or network is protected with a firewall or proxy, please ensure, that firefox can connect to the internet.

What does "nmap 192.168.1.100" tell you? (you might have to install nmap, "sudo apt-get install nmap")

nuc@nuc:~$ nmap 192.168.1.100
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-13 12:24 CEST
Nmap scan report for 192.168.1.100
Host is up (0.0010s latency).
Not shown: 824 closed ports, 175 filtered ports
PORT     STATE SERVICE
7001/tcp open  afs3-callback

Nmap done: 1 IP address (1 host up) scanned in 57.46 seconds

Also what are you trying to do with this NUC+Ubuntu+Hikvision combo?

Watching and record crows while collecting food. It might be handy to make it public on the internet.

One last step to try is after you've set up the ip to camera (192.168.1.100) is to reboot both devices, just to make sure the virtual ip does not interfere with the setup. Then see if browser connection works.

Do you mean by reboot the camera reconnect (cause there is no reboot button)? If yes, I did that.

After seeing the firefox screen above I right hit enter on the browser address once and got the usual hikvision login-screen (it didn't work every time):

But when I enter login and password. I receive a message: "network unormal".

mkkoskin · August 13, 2014

Code:

nuc@nuc:~$ nmap 192.168.1.100

Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-13 12:24 CEST

Nmap scan report for 192.168.1.100

Host is up (0.0010s latency).

Not shown: 824 closed ports, 175 filtered ports

PORT STATE SERVICE

7001/tcp open afs3-callback

Nmap done: 1 IP address (1 host up) scanned in 57.46 seconds

Something surely is incorrect, it seems there are no http port open in the camera. Factory reset the camera and try to put it on DHCP (check the DHCP from camera network settings), the power down the camera (unplug or w/e), power it back up, wait a minute, run "arp-scan --localnet" to figure out what IP DHCP assigned for it. If you can access thru this IP, go to your router settings and make a rule so router always assigns the same IP to this same MAC address.

--Just a guessing below!--

Trying to figure out why the static ip isnt working makes me wonder if the router you're using allows static IPs at all? If it doesnt allow any traffic from static IPs for some odd security reason, then that might cause it to "lock up". It could be "protecting" the 192.168.1.* network, explains why 192.0.0.* works.

empedokles · August 13, 2014

Factory reset the camera and try to put it on DHCP (check the DHCP from camera network settings), the power down the camera (unplug or w/e), power it back up, wait a minute, run "arp-scan --localnet" to figure out what IP DHCP assigned for it. If you can access thru this IP, go to your router settings and make a rule so router always assigns the same IP to this same MAC address.

Set it to DHCP. I can't access IP 192.168.1.43 if that's the IP it assigned (there is no other).

nuc@nuc:~$ sudo arp-scan --localnet
Interface: eth0, datalink type: EN10MB (Ethernet)

Starting arp-scan 1.8.1 with 256 hosts (http://www.nta-monitor.com/tools/arp-scan/)

192.168.1.1 00:22:10:82:61:40 Motorola Mobility, Inc.

192.168.1.33 00:80:3f:3a:d6:79 TATUNG COMPANY

192.168.1.43 44:19:b6:2d:13:a8 (Unknown)

3 packets received by filter, 0 packets dropped by kernel

Ending arp-scan 1.8.1: 256 hosts scanned in 1.360 seconds (188.24 hosts/sec). 3 responded

nuc@nuc:~$

--Just a guessing below!--
Trying to figure out why the static ip isnt working makes me wonder if the router you're using allows static IPs at all? If it doesnt allow any traffic from static IPs for some odd security reason, then that might cause it to "lock up". It could be "protecting" the 192.168.1.* network, explains why 192.0.0.* works.

I have posted some router screenshots on the first page of this thread. I repost them here:

catseyenu · August 13, 2014

Keep an eye on Adblock Plus, it's been known to block scripts and xml rquests in the Hik browser gui.

empedokles · August 13, 2014

Here some more router Pics:

IP Passtrough maybe?

empedokles · August 13, 2014

And a last one:

Sign In

Please help me to install a Hikvision 2032-I under Ubuntu

Recommended Posts

empedokles 0

Share this post

Link to post

Share on other sites

CBX 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

CBX 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

mkkoskin 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

buellwinkle 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

buellwinkle 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

buellwinkle 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

mkkoskin 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

empedokles 0

Share this post

Link to post

Share on other sites

mkkoskin 0

Share this post

Link to post

Share on other sites

empedokles 0