192.0.0.64 ist die Standard-IP der Hikvision Cams. Wenn man sie reseted.
Schaut mal hier:

Wäre Additional IP Subnet eine Möglichkeit?
Also die Kamera kann ich nur vernünftig erreichen, wenn der Router IP 192.168.1.1 hat und die DHCP-Range.33-.64 beträgt. Ich bei Ubuntu eine virtuelle IP 192.0.0.128 vergebe (muss man dann halt immer machen) und die Kamera auf IP 192.0.0.64 lasse (factory default). Arp-scan zeigt dann die IP 192.0.0.64 zwar nicht an, aber ich kann sie so problemlos pingen und über den Browser erreichen.
Die Ports sind dann konsistent:
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 08:30 CEST
Nmap scan report for 192.0.0.64
Host is up (0.00087s latency).
Not shown: 991 closed ports
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
80/tcp open http
443/tcp open https
554/tcp open rtsp
7001/tcp open afs3-callback
8000/tcp open http-alt
8200/tcp open trivnet1
49152/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 1.42 seconds
nuc@nuc:~$ nmap 192.0.0.64
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 08:30 CEST
Nmap scan report for 192.0.0.64
Host is up (0.0011s latency).
Not shown: 991 closed ports
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
80/tcp open http
443/tcp open https
554/tcp open rtsp
7001/tcp open afs3-callback
8000/tcp open http-alt
8200/tcp open trivnet1
49152/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 2.50 seconds
nuc@nuc:~$ nmap 192.0.0.64
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 08:30 CEST
Nmap scan report for 192.0.0.64
Host is up (0.00092s latency).
Not shown: 991 closed ports
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
80/tcp open http
443/tcp open https
554/tcp open rtsp
7001/tcp open afs3-callback
8000/tcp open http-alt
8200/tcp open trivnet1
49152/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 2.45 seconds
nuc@nuc:~$ nmap 192.0.0.64
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 08:30 CEST
Nmap scan report for 192.0.0.64
Host is up (0.0030s latency).
Not shown: 991 closed ports
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
80/tcp open http
443/tcp open https
554/tcp open rtsp
7001/tcp open afs3-callback
8000/tcp open http-alt
8200/tcp open trivnet1
49152/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 2.51 seconds
nuc@nuc:~$ nmap 192.0.0.64
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 08:30 CEST
Nmap scan report for 192.0.0.64
Host is up (0.13s latency).
Not shown: 991 closed ports
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
80/tcp open http
443/tcp open https
554/tcp open rtsp
7001/tcp open afs3-callback
8000/tcp open http-alt
8200/tcp open trivnet1
49152/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 3.46 seconds
nuc@nuc:~$
Als ich die IP des Routers gemäss Ratschlag unten auf 192.0.0.1 (Range 192.0.0.101-.199) vergeben und dann nmap ausgeführt habe. Sind die Ports der Kamera ständig hin und hergeswitcht. Auch bei.64. Schaut selbst:
nuc@nuc:~$ nmap 192.168.1.100
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 00:01 CEST
Nmap scan report for 192.168.1.100
Host is up (0.0012s latency).
Not shown: 991 closed ports
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
80/tcp open http
443/tcp open https
554/tcp open rtsp
7001/tcp open afs3-callback
8000/tcp open http-alt
8200/tcp open trivnet1
49152/tcp open unknown
Nmap done: 1 IP address (1 host up) scanned in 16.66 seconds
nuc@nuc:~$ nmap 192.168.1.100
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 00:03 CEST
Nmap scan report for 192.168.1.100
Host is up (0.0016s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
Code:
nuc@nuc:~$ nmap 192.168.1.100
Starting Nmap 6.40 ( http://nmap.org ) at 2014-08-14 00:16 CEST
Nmap scan report for 192.168.1.100
Host is up (0.00084s latency).
Not shown: 989 closed ports
PORT STATE SERVICE
21/tcp filtered ftp
23/tcp filtered telnet
2399/tcp filtered fmpro-fdal
3971/tcp filtered lanrevserver
4006/tcp filtered pxc-spvr
7001/tcp open afs3-callback
8083/tcp filtered us-srv
9917/tcp filtered unknown
18101/tcp filtered unknown
27352/tcp filtered unknown
49160/tcp filtered unknown
Sehr merkwürdiges Verhalten dieses Swisscom-Motorola-Routers. Mögliche Ursache?
Puh, ich habe noch einen blauen Netopia im Keller. Mal versuchen? Allerdings habe ich da wohl kein Adminpasswort mehr.