empedokles 0 Posted May 9, 2014 Is it possible to use this camera somehow under Ubuntu Linux? Share this post Link to post Share on other sites
buellwinkle 0 Posted May 9, 2014 What do you mean? If you mean, can you view the video using a browser, then the answer is no as the plugin only works with Windows and Mac. If you mean by any means, sure, you can use VLC to view live streaming video from the cameras. You can also set it up in Zoneminder and do recording and live viewing. Share this post Link to post Share on other sites
empedokles 0 Posted May 9, 2014 Hello How do I set it up in VLC? Can you motion trigger the recording in zoneminder? Share this post Link to post Share on other sites
ranzor 0 Posted May 9, 2014 ZoneMinder does server side motion detection. Meaning it looks at the difference between frames and determines if motion is detected. With ZoneMinder you can record on motion or have it do things like send you emails. To view the camera in VLC you'll need to open the RTSP stream on the camera by telling VLC to "Open Network Stream..." the URL you'll use will look like this: rtsp://admin:12345@putyourcamera'sIPhere:554/Streaming/Channels/1?tcp Share this post Link to post Share on other sites
empedokles 0 Posted May 9, 2014 ZoneMinder does server side motion detection. Meaning it looks at the difference between frames and determines if motion is detected. With ZoneMinder you can record on motion or have it do things like send you emails. rtsp://admin:12345@putyourcamera'sIPhere:554/Streaming/Channels/1?tcp Zone minder currently isn't available for Ubuntu 14.04 as it stands. How do I find out about my cameras IP? Share this post Link to post Share on other sites
ranzor 0 Posted May 9, 2014 Check out this guide for installing ZM under Ubuntu 14.04. This might help you out. http://www.zoneminder.com/wiki/index.php/Ubuntu_Server_14.04_64-bit_with_Zoneminder_1.26.5_the_easy_way For the IP address. I believe the camera will grab an IP address via DHCP from your router. You might be able to find the camera's IP by checking your routers DHCP lease table. Once you get logged into your router you can set a static IP address. Share this post Link to post Share on other sites
buellwinkle 0 Posted May 9, 2014 The IP address of the camera is 192.0.0.64 out of the box. Normally on Windows they provide a program called SADP that finds it lets you change it. But in your case, since you have no access to Windows, you would need to change your server's IP in that subnet, say 192.0.0.128. Then you can connect via a browser but you won't see video. Login with admin/12345, click on Configuration tab, click on Network on the menu on the left, put in what IP you want for the camera, subnet mask, gateway and click save. Then you can change your Ubuntu server back to it's original IP and you can connect to the camera using a browser to verify (still no video). Then you can use Zoneminder or VLC to view the live streaming video. If you can configure Linux, Zoneminder is not much harder. It's purposely made hard to make you feel like you are in Linux. There are commercial grade NVR software for Linux, for example Exacq should work on Ubuntu. They have a low cost entry version called Start. Trade off is CPU costs vs. software cost. Share this post Link to post Share on other sites
CBX 0 Posted May 10, 2014 If you are happy in linux then you can also just assign an IP to an alias of your NIC: root@rl70:~# ifconfig eth0:0 192.0.0.128 When done: root@rl70:~# ifconfig eth0:0 down Also, in terms of configuring the cam, you could use WINE but a linux ONVIF program would be much easier. Share this post Link to post Share on other sites
empedokles 0 Posted May 10, 2014 For the IP address. I believe the camera will grab an IP address via DHCP from your router. You might be able to find the camera's IP by checking your routers DHCP lease table. Once you get logged into your router you can set a static IP address. So I need to disable DHCP in my router for this? The last time I did this my TV box didn't work anymore. Hence it's not something preferable. Where do I find the DHCP lease table? Share this post Link to post Share on other sites
empedokles 0 Posted May 10, 2014 (edited) The IP address of the camera is 192.0.0.64 out of the box. Normally on Windows they provide a program called SADP that finds it lets you change it. But in your case, since you have no access to Windows, you would need to change your server's IP in that subnet, say 192.0.0.128. Then you can connect via a browser but you won't see video. Login with admin/12345, click on Configuration tab, click on Network on the menu on the left, put in what IP you want for the camera, subnet mask, gateway and click save. Then you can change your Ubuntu server back to it's original IP and you can connect to the camera using a browser to verify (still no video). Then you can use Zoneminder or VLC to view the live streaming video. If you can configure Linux, Zoneminder is not much harder. It's purposely made hard to make you feel like you are in Linux. There are commercial grade NVR software for Linux, for example Exacq should work on Ubuntu. They have a low cost entry version called Start. Trade off is CPU costs vs. software cost. Hi. 192.0.0.64 won't work. I had the camera once earlier directly connected to a Mac, but no software existed. I saw there is a software iVMS-4200 linux (beta). Would it help? I don't have a server. I only have a router and the camera is connected to this router. (BTW: I'm pretty new to Ubuntu and don't understand much networking. I would need a bit more step-to-step instructions.) I attached some images of my router webadmin. Accessable over IP 192.168.1.1. Edited May 12, 2014 by Guest Share this post Link to post Share on other sites
ranzor 0 Posted May 12, 2014 You do not need to disable DHCP on your router. From the screen shots you've posted, it appears that your camera has an ip address of 192.168.1.33. I'd try opening your web browser and going to that address. If a login screen pops up for the camera then you're in the right place. Once you've logged in there should be an option to set a static IP address. You can probably set it to something like 192.168.1.10 as long as you don't have another device with the same IP. Share this post Link to post Share on other sites
empedokles 0 Posted May 12, 2014 (edited) Unfortunately that doesn't work. 192.168.1.33 is listed as Tatung Company inside the terminal and is my digital TV-Box and not the IP-Cam. What now? empedokles@empedokles:~$ 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.200 00:18:fe:6d:cb:3e Hewlett Packard 3 packets received by filter, 0 packets dropped by kernel Ending arp-scan 1.8.1: 256 hosts scanned in 1.531 seconds (167.21 hosts/sec). 3 responded Edited May 12, 2014 by Guest Share this post Link to post Share on other sites
CBX 0 Posted May 12, 2014 You can always just use tcpdump on linux or wireshark on Windows to listen for the camera when it's booting - should reveal the IP address (if it's not on 192.0.0.64). Some people also get confused about 192.0.0.64 and think it's 192.168.0.64 (which would have made more sense Hikvision!). Share this post Link to post Share on other sites
empedokles 0 Posted May 12, 2014 You can always just use tcpdump on linux or wireshark on Windows to listen for the camera when it's booting - should reveal the IP address (if it's not on 192.0.0.64). Some people also get confused about 192.0.0.64 and think it's 192.168.0.64 (which would have made more sense Hikvision!). Wait, won't my router (see screenshots above) not exclude 192.0.0.64? I have tcpdump installed. What do I have to do? Share this post Link to post Share on other sites
CBX 0 Posted May 12, 2014 I haven't read the whole thread fully, so I might have posted wrong advice. I am assuming that your camera is on the same subnet as your computer (I don't mean IP - on the same section of network). If it is, then the router functions aren't needed - only the switch/hub part. Since you were using Ubuntu, I assumed good networking knowledge (no offense is intended here). If you have access to Windows, you may be better off with wireshark as is graphical. The idea is that wirehsark/tcpdump listens to the network and reports traffic it sees. The camera when it boots up will be trying to connect to things and you would be able to see what IP address that's from. Here's a tcpdump example where I filter out ssh traffic (otherwise I'll get flooded with results as I'm using ssh to run tcpdump): root@rl70:~# tcpdump -n | grep -v ssh tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 11:46:13.336981 IP 192.168.0.6.22 > 192.168.0.15.2775: Flags [P.], seq 3250769780:3250769976, ack 1301303205, win 43952, length 196 11:46:13.448615 IP 192.168.0.15.2775 > 192.168.0.6.22: Flags [.], ack 196, win 65535, length 0 11:46:13.790055 IP 192.168.0.100.138 > 192.168.0.255.138: NBT UDP PACKET(138) 11:46:19.111707 IP 192.168.0.202.80 > 192.168.0.6.41450: Flags [P.], seq 3497760973:3497763344, ack 638217591, win 8453, options [nop,nop,TS val 454588382 ecr 1165145], length 2371 In the last line uou can see my server (192.168.0.6) get a response from the webserver (port 80) of one of my cameras (192.168.0.202). If this doesn't make sense to you, or I've got your situation wrong, then please ignore me. Share this post Link to post Share on other sites
empedokles 0 Posted May 12, 2014 Currrently I have 4 devices in the router. The notebook (empedokles), a Windows PC, a TV box and the IP-Camera with it's port injector. The camera is on (I can see the infrared LEDs). tcpdump -n | grep -v ssh in Terminal produces nothing here: tcpdump: no suitable device found Share this post Link to post Share on other sites
CBX 0 Posted May 12, 2014 Depending on your linux box you may have to run this as root, as possbility specify the network interface to listen on. Try man tcpdump And you'll then need to power off and back on your camera whilst tcpdump is listening. Share this post Link to post Share on other sites
empedokles 0 Posted May 12, 2014 I've put a sudo in front of your command and got: 17:12:28.163966 IP 192.168.1.40.57739 > 131.130.65.121.80: Flags [P.], seq 509230:509702, ack 26, win 229, options [nop,nop,TS val 5009278 ecr 1139568097], length 472 17:12:28.166454 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [.], ack 496918, win 497, options [nop,nop,TS val 1139568099 ecr 5009260,nop,nop,sack 1 {498286:505126}], length 0 17:12:28.168702 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [.], ack 496918, win 497, options [nop,nop,TS val 1139568101 ecr 5009260,nop,nop,sack 1 {498286:506494}], length 0 17:12:28.170454 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [.], ack 496918, win 497, options [nop,nop,TS val 1139568103 ecr 5009260,nop,nop,sack 1 {498286:507862}], length 0 17:12:28.172728 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [.], ack 496918, win 497, options [nop,nop,TS val 1139568106 ecr 5009260,nop,nop,sack 1 {498286:509230}], length 0 17:12:28.198227 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [.], ack 509230, win 401, options [nop,nop,TS val 1139568131 ecr 5009278], length 0 17:12:28.198452 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [.], ack 509702, win 497, options [nop,nop,TS val 1139568131 ecr 5009278], length 0 17:12:28.199084 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [P.], seq 26:272, ack 509702, win 501, options [nop,nop,TS val 1139568132 ecr 5009278], length 246 17:12:28.199207 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [P.], seq 272:277, ack 509702, win 501, options [nop,nop,TS val 1139568132 ecr 5009278], length 5 17:12:28.199233 IP 192.168.1.40.57739 > 131.130.65.121.80: Flags [.], ack 277, win 237, options [nop,nop,TS val 5009287 ecr 1139568132], length 0 17:12:28.199264 IP 192.168.1.40.57739 > 131.130.65.121.80: Flags [F.], seq 509702, ack 277, win 237, options [nop,nop,TS val 5009287 ecr 1139568132], length 0 17:12:28.199506 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [F.], seq 277, ack 509702, win 501, options [nop,nop,TS val 1139568132 ecr 5009278], length 0 17:12:28.199518 IP 192.168.1.40.57739 > 131.130.65.121.80: Flags [.], ack 278, win 237, options [nop,nop,TS val 5009287 ecr 1139568132], length 0 17:12:28.233199 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [.], ack 509703, win 501, options [nop,nop,TS val 1139568166 ecr 5009287], length 0 17:12:28.464953 IP 131.130.65.121.80 > 192.168.1.40.57739: Flags [F.], seq 277, ack 509703, win 501, options [nop,nop,TS val 1139568398 ecr 5009287], length 0 17:12:28.464982 IP 192.168.1.40.57739 > 131.130.65.121.80: Flags [.], ack 278, win 237, options [nop,nop,TS val 5009353 ecr 1139568166], length 0 17:12:30.591449 IP 192.168.1.40.57364 > 173.194.113.231.80: Flags [F.], seq 374157714, ack 1341113533, win 254, options [nop,nop,TS val 5009885 ecr 2037003195], length 0 17:12:30.606979 IP 173.194.113.231.80 > 192.168.1.40.57364: Flags [F.], seq 1, ack 1, win 670, options [nop,nop,TS val 2037118747 ecr 5009885], length 0 17:12:30.606999 IP 192.168.1.40.57364 > 173.194.113.231.80: Flags [.], ack 2, win 254, options [nop,nop,TS val 5009889 ecr 2037118747], length 0 17:12:31.325936 IP 192.168.1.200.17500 > 255.255.255.255.17500: UDP, length 100 17:12:31.327391 IP 192.168.1.200.17500 > 192.168.1.255.17500: UDP, length 100 17:12:34.034087 IP 192.168.1.1.520 > 255.255.255.255.520: RIPv1, Response, length: 44 17:12:41.091144 IP 192.168.1.40.17500 > 255.255.255.255.17500: UDP, length 102 17:12:41.091469 IP 192.168.1.40.17500 > 192.168.1.255.17500: UDP, length 102 17:12:51.856807 IP 192.168.1.200.1036 > 255.255.255.255.1947: UDP, length 40 17:12:55.869103 IP 192.168.1.200.1036 > 192.168.1.255.1947: UDP, length 40 17:13:01.325264 IP 192.168.1.200.17500 > 255.255.255.255.17500: UDP, length 100 17:13:01.326456 IP 192.168.1.200.17500 > 192.168.1.255.17500: UDP, length 100 17:13:04.833111 IP 192.168.1.1.520 > 255.255.255.255.520: RIPv1, Response, length: 44 17:13:09.090272 IP6 :: > ff02::1:ff27:c2fa: ICMP6, neighbor solicitation, who has fe80::4619:b7ff:fe27:c2fa, length 24 17:13:09.205900 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 17:13:10.076003 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::2: ICMP6, router solicitation, length 16 17:13:11.130244 IP 192.168.1.40.17500 > 255.255.255.255.17500: UDP, length 102 17:13:11.130471 IP 192.168.1.40.17500 > 192.168.1.255.17500: UDP, length 102 17:13:14.086906 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::2: ICMP6, router solicitation, length 16 17:13:18.096763 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::2: ICMP6, router solicitation, length 16 17:13:21.132651 IP 108.160.167.158.80 > 192.168.1.40.54331: Flags [P.], seq 179:358, ack 292, win 83, options [nop,nop,TS val 360203073 ecr 5008614], length 179 17:13:21.134300 IP 192.168.1.40.54331 > 108.160.167.158.80: Flags [P.], seq 292:583, ack 358, win 1141, options [nop,nop,TS val 5022521 ecr 360203073], length 291 17:13:21.313549 IP 108.160.167.158.80 > 192.168.1.40.54331: Flags [.], ack 583, win 83, options [nop,nop,TS val 360203118 ecr 5022521], length 0 17:13:26.137888 ARP, Request who-has 192.168.1.1 tell 192.168.1.40, length 28 17:13:26.138174 ARP, Reply 192.168.1.1 is-at 00:22:10:82:61:40, length 46 17:13:28.273790 ARP, Request who-has 192.0.0.64 tell 192.0.0.64, length 46 17:13:31.324949 IP 192.168.1.200.17500 > 255.255.255.255.17500: UDP, length 100 17:13:31.326157 IP 192.168.1.200.17500 > 192.168.1.255.17500: UDP, length 100 17:13:34.917093 IP 192.168.1.200.1036 > 255.255.255.255.1947: UDP, length 40 17:13:36.817004 IP 192.0.0.64 > 224.0.0.22: igmp v3 report, 2 group record(s) 17:13:36.826706 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 17:13:36.850291 44:19:b7:27:c2:fa > ff:ff:ff:ff:ff:ff, ethertype Unknown (0x8033), length 416: 0x0000: 2101 01f6 0000 0001 0604 0102 fa8e 4419 !.............D. 0x0010: b727 c2fa c000 0040 ffff ffff ffff 0000 .'.....@........ 0x0020: 0000 ffff ff00 4453 2d32 4344 3236 3332 ......DS-2CD2632 0x0030: 462d 4953 3031 3230 3133 3132 3234 4343 F-IS0120131224CC 0x0040: 5252 3434 3632 3635 3332 3200 0000 0000 RR446265322..... 0x0050: 0000 0000 0000 0000 9810 0000 1f40 0000 .............@.. 0x0060: 0001 0000 0000 5635 2e30 2e32 6275 696c ......V5.0.2buil 0x0070: 6420 3133 3038 3035 0000 0000 0000 0000 d.130805........ 0x0080: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0090: 0000 0000 0000 5634 2e30 2c20 6275 696c ......V4.0,.buil 0x00a0: 6420 3133 3034 3131 0000 0000 0000 0000 d.130411........ 0x00b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00c0: 0000 0000 0000 3230 3134 2d30 352d 3132 ......2014-05-12 0x00d0: 2031 363a 3138 3a35 3600 0000 0000 0000 .16:18:56....... 0x00e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00f0: 0000 0000 0000 029c 5a13 0000 0000 0000 ........Z....... 0x0100: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0110: 0000 0000 0000 0000 0000 0000 0000 4007 ..............@. 0x0120: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0130: 0000 0000 0000 0000 0000 0000 0000 0050 ...............P 0x0140: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0150: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0160: 0000 4453 2d32 4344 3236 3332 462d 4953 ..DS-2CD2632F-IS 0x0170: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0180: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0190: 0000 .. 17:13:36.913877 44:19:b7:27:c2:fa > ff:ff:ff:ff:ff:ff, ethertype Unknown (0x8033), length 416: 0x0000: 2101 01f6 0000 0002 0604 0102 f98e 4419 !.............D. 0x0010: b727 c2fa c000 0040 ffff ffff ffff 0000 .'.....@........ 0x0020: 0000 ffff ff00 4453 2d32 4344 3236 3332 ......DS-2CD2632 0x0030: 462d 4953 3031 3230 3133 3132 3234 4343 F-IS0120131224CC 0x0040: 5252 3434 3632 3635 3332 3200 0000 0000 RR446265322..... 0x0050: 0000 0000 0000 0000 9810 0000 1f40 0000 .............@.. 0x0060: 0001 0000 0000 5635 2e30 2e32 6275 696c ......V5.0.2buil 0x0070: 6420 3133 3038 3035 0000 0000 0000 0000 d.130805........ 0x0080: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0090: 0000 0000 0000 5634 2e30 2c20 6275 696c ......V4.0,.buil 0x00a0: 6420 3133 3034 3131 0000 0000 0000 0000 d.130411........ 0x00b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00c0: 0000 0000 0000 3230 3134 2d30 352d 3132 ......2014-05-12 0x00d0: 2031 363a 3138 3a35 3600 0000 0000 0000 .16:18:56....... 0x00e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x00f0: 0000 0000 0000 029c 5a13 0000 0000 0000 ........Z....... 0x0100: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0110: 0000 0000 0000 0000 0000 0000 0000 4007 ..............@. 0x0120: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0130: 0000 0000 0000 0000 0000 0000 0000 0050 ...............P 0x0140: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0150: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0160: 0000 4453 2d32 4344 3236 3332 462d 4953 ..DS-2CD2632F-IS 0x0170: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0180: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0x0190: 0000 .. 17:13:36.931243 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::c: frag (0|1448) 3702 > 3702: UDP, length 2766 17:13:36.931563 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::c: frag (1448|1326) 17:13:36.955295 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::c: frag (0|1448) 3702 > 3702: UDP, length 2766 17:13:36.955640 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::c: frag (1448|1326) 17:13:37.006635 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::c: frag (0|1448) 3702 > 3702: UDP, length 2766 17:13:37.006960 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::c: frag (1448|1326) 17:13:37.163428 IP 192.0.0.64.5353 > 224.0.0.251.5353: 0 [6q] [6n] ANY (QM)? DS-2CD2632F-IS0120131224CCRR446265322.local. ANY (QM)? DS-2CD2632F-IS0120131224CCRR446265322.local. ANY (QM)? DS-2CD2632F-IS0120131224CCRR446265322.local. ANY (QM)? _DS-2CD2632F-IS._PSIA._tcp.local. ANY (QM)? _DS-2CD2632F-IS._CGI._tcp.local. ANY (QM)? _DS-2CD2632F-IS._CGI._tcp.local. (717) 17:13:37.414787 IP 192.0.0.64.5353 > 224.0.0.251.5353: 0 [6q] [6n] ANY (QM)? DS-2CD2632F-IS0120131224CCRR446265322.local. ANY (QM)? DS-2CD2632F-IS0120131224CCRR446265322.local. ANY (QM)? DS-2CD2632F-IS0120131224CCRR446265322.local. ANY (QM)? _DS-2CD2632F-IS._PSIA._tcp.local. ANY (QM)? _DS-2CD2632F-IS._CGI._tcp.local. ANY (QM)? _DS-2CD2632F-IS._CGI._tcp.local. (717) 17:13:37.542906 IP 192.168.1.1.520 > 255.255.255.255.520: RIPv1, Response, length: 44 17:13:37.666045 IP 192.0.0.64.5353 > 224.0.0.251.5353: 0*- [0q] 6/0/0 (Cache flush) A 192.0.0.64, (Cache flush) AAAA fe80::4619:b7ff:fe27:c2fa, (Cache flush) HINFO, (Cache flush) SRV DS-2CD2632F-IS0120131224CCRR446265322.local.:80 0 0, (Cache flush) SRV DS-2CD2632F-IS0120131224CCRR446265322.local.:80 0 0, TXT "path=/" (458) 17:13:38.667485 IP 192.0.0.64.5353 > 224.0.0.251.5353: 0*- [0q] 6/0/0 (Cache flush) A 192.0.0.64, (Cache flush) AAAA fe80::4619:b7ff:fe27:c2fa, (Cache flush) HINFO, (Cache flush) SRV DS-2CD2632F-IS0120131224CCRR446265322.local.:80 0 0, (Cache flush) SRV DS-2CD2632F-IS0120131224CCRR446265322.local.:80 0 0, TXT "path=/" (458) 17:13:38.931168 IP 192.168.1.200.1036 > 192.168.1.255.1947: UDP, length 40 17:13:39.669692 IP 192.0.0.64.5353 > 224.0.0.251.5353: 0*- [0q] 6/0/0 (Cache flush) A 192.0.0.64, (Cache flush) AAAA fe80::4619:b7ff:fe27:c2fa, (Cache flush) HINFO, (Cache flush) SRV DS-2CD2632F-IS0120131224CCRR446265322.local.:80 0 0, (Cache flush) SRV DS-2CD2632F-IS0120131224CCRR446265322.local.:80 0 0, TXT "path=/" (458) 17:13:41.116445 IP6 fe80::4619:b7ff:fe27:c2fa > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 17:13:41.174370 IP 192.168.1.40.17500 > 255.255.255.255.17500: UDP, length 102 17:13:41.174622 IP 192.168.1.40.17500 > 192.168.1.255.17500: UDP, length 102 17:13:46.776320 IP 192.0.0.64 > 224.0.0.22: igmp v3 report, 1 group record(s) 17:14:01.324649 IP 192.168.1.200.17500 > 255.255.255.255.17500: UDP, length 100 I interrupted the power of the IP-Cam twice. Anything suspicious? Share this post Link to post Share on other sites
CBX 0 Posted May 12, 2014 Well there's lot of traffic from your cam on 192.0.0.64 .... I suppose it's possible the cam is running on that IP before it switches to another one, but I'd configure your linux box to be on the 192.0.0.0/24 subnet and try talking to the camera on 192.0.0.64 Share this post Link to post Share on other sites
empedokles 0 Posted May 12, 2014 How will I do that? Will I still be able to have internet-access afterwards? Share this post Link to post Share on other sites
CBX 0 Posted May 12, 2014 You need to change IP (or create an alias) to that on the camera subnet (e.g. 192.0.0.128), login in to the camera and set it's IP to your network. Then change your computer back to normal. Good luck! Share this post Link to post Share on other sites
empedokles 0 Posted May 12, 2014 I need step to step instructions. Share this post Link to post Share on other sites
MaxIcon 0 Posted May 12, 2014 I haven't read the whole thread, but if you've got a Windows box on your network, you might want to run SADP and use that to set the camera's IP address. It worked for me with 2 cams, both using the Hik default IP, and let me set both of them to the subnet I wanted. If you've already tried that, never mind! Share this post Link to post Share on other sites
buellwinkle 0 Posted May 13, 2014 Your biggest problem is you are out of your league running Linux. First understand while Linux is Linux, every distribution is very different so the file name that contains the Ethernet config or a gui that make it easier is different for Redhat, Ubuntu, Debian and so on. You best bet is to go to the Ubuntu forum and ask there - http://ubuntuforums.org/forumdisplay.php?f=327 We can spend a lot of time going back and forth on how to set a static IP on your Ubuntu PC so you can set the IP on your camera or you can find a friend, neighbor or someone with a Windows PC, install SADP and set a static IP on the camera. You cannot move forward without doing that first. Then the second issue is if you go beyond this unsurmountable task of setting the IP address on your camera, it will not be viewable with a browser on any flavor of Linux. So you will have to run something else to view the cameras and it won't be easy because if Ubuntu network scares you, you ain't seen nothing yet, wait for Zoneminder. Share this post Link to post Share on other sites
