Jump to content

hdo26

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. hdo26

    Mini nvr questions

    Yesterday i played around with different settings for my dahua cam. I did some debugging on the ONVIF protocol and it seems that dahua's onvif implementation is just fine. I guess the ONVIF client on the NVR is fishy. I also cannot get an image with the RTSP protocol Anybody out there with dahua cams connected to the mini nvr? hdo
  2. hdo26

    Mini nvr questions

    Ok, but what can i do to get this camera working For some reason i have the feelding that dahua's ONVIF implementation is crappy. E.g. with Onvif Device Manager i can't get any Event logs Here are my netstat logs: ~ # netstat -na Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:49152 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:9989 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:9990 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:554 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:42323 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:3800 0.0.0.0:* LISTEN tcp 0 0 192.168.2.182:46599 192.168.2.5:21 ESTABLISHED tcp 0 0 :::80 :::* LISTEN tcp 0 0 :::37776 :::* LISTEN tcp 0 0 :::37777 :::* LISTEN tcp 0 0 :::23 :::* LISTEN tcp 0 793 ::ffff:192.168.2.182:23 ::ffff:192.168.2.202:47510 ESTABLISHED udp 0 0 0.0.0.0:20000 0.0.0.0:* udp 0 0 0.0.0.0:20001 0.0.0.0:* udp 0 0 0.0.0.0:20002 0.0.0.0:* udp 0 0 0.0.0.0:20003 0.0.0.0:* udp 0 0 0.0.0.0:20004 0.0.0.0:* udp 0 0 0.0.0.0:20005 0.0.0.0:* udp 0 0 0.0.0.0:20006 0.0.0.0:* udp 0 0 0.0.0.0:20007 0.0.0.0:* udp 0 0 0.0.0.0:59999 0.0.0.0:* udp 0 0 239.255.255.250:1900 0.0.0.0:* udp 0 0 0.0.0.0:3702 0.0.0.0:* udp 0 0 0.0.0.0:37778 0.0.0.0:* udp 0 0 0.0.0.0:37778 0.0.0.0:* udp 0 0 239.255.255.251:37810 0.0.0.0:* udp 0 0 192.168.2.182:37810 0.0.0.0:* udp 0 0 0.0.0.0:5050 0.0.0.0:* udp 0 0 0.0.0.0:40660 0.0.0.0:* udp 0 0 0.0.0.0:5353 0.0.0.0:* udp 0 0 0.0.0.0:54004 0.0.0.0:* hdo! Buddy! You've got the magic password, and you can see which ports are listening on Dahua YPC, not to guess. But I think the latest versions of all tied to the web port. Through it are requests for ONVIF. I think so still trying to bring everything to a common denominator.
  3. hdo26

    Mini nvr questions

    I finally got my mini nvr but i can't get my cameras to work I have 2 Dahua HFW-4200S and both do support ONVIF v2.4.1 and i also have the latest firmware for the cameras. I can find the cameras with the 'search' function and it shows 2 ONVIF camera on port 80. Interestingly i read on the internet that the ONVIF port for dahua is 9989 which is also not working Unfortunately i can't get any image displayed on the nvr. Does anybody also have problems with their dahua cameras? hdo
  4. hdo26

    Mini nvr questions

    Ok, i thought you had a serial cable connected that would be the best. Anyway just enter 'dmesg' after boot up via telnet. You'll get a lot of boot up messages. I like to investigate how to get the XVISION firmware flashed to those mini nvrs. I can't wait to get mine Interesting that this box can't deliver enough Power via USB
  5. hdo26

    Mini nvr questions

    I don't have the mini nvr yet (currently shipping) but i like to do some research beforehand. There is no SSH server in the firmware but you can login via telnet. As far as i remember the login is: root/antslq
  6. hdo26

    Mini nvr questions

    @Ghostrider Can you please post your 'dmsg' after reboot of your nvr? (Maybe on https://gist.github.com/?) Thank you.
  7. Which model are you referring to and how did you try to mount the file system as 'rw' ? We need some more information to help you out. iTuneDVR should be able to help you out since he has a lot of experiences doing those stuffs.
  8. Then how about writing a little tutorial on doing this? I guess a lot of people like to know how to do that
  9. hdo26

    Mini nvr questions

    Just because i'm curious what are you gonna do with an external output?
  10. @iTuneDVR Another topic regarding serial output. On my HFW4200s i can only see the u-boot message. All messages coming from the kernel is suppressed. Do you know how to get them displayed? (dmesg, boot messages) EDIT: FIXED: You have to remove the dh_keyboard=1 variable in u-boot to enable boot messages (thanks for the hint!)
  11. Great, you could have saved me a couple of hours of my freetime Guess you're under NDA or something? As for me i don't have any connections to the manufacturer and i dislike companies who don't release the GPL source code of their products. So i don't mind releasing this information to the public. BTW What is iTuneDVR doing? Unfortunately i can't read russian hdo
  12. Hallo, i've been in the forums as a passive member for quite a while and now i like to contribute some little information to this forum. I noticed that with the v2.4x baseline firmware releases the well known telnet access root/vizxv is gone For me as a linux guy i wasn't happy with it at all so i took some time to reverse enginieer the firmware of my HFW4200s camera. I manage to analyse the telnet authorization part in the firmware. The /etc/passwd is still the same so the old password should work as always but the engineers at dahua changed the authorization so this file is never read for login. First i was able to patch the busybox binary to accept any passwords but a couple of hours later i was able to enter a valid password. In fact the secret login/password consists of a valid user with administrator privileges to the web interface (e.g. admin) and a password with a 'secret' prefix. Long story short as in my case with login 'admin' and password 'admin' my telnet login is like this: login: admin password: 7ujMko0admin So the prefix '7ujMko0' is the important part here. Finally i'm able to telnet login to my cameras again Can any of you double check on that? Happy telnet login! Regards, hdo
  13. I also heard of BlueIris but it only runs on Windows and i'm a linux guy
  14. Hello, i recently bought a IP Webcam (dahua hfw2100) and like it alot. It's a nice piece of hardware but the software is cr*p. The motion detection of this cam is unusable and unreliable. I then discovered the software 'Motion' and that was the solution for me. So here is my setup: - running Motion on a Mac Mini 2011 together with other server applications - on motion detect call a script which optimize the snapshots for email - sending email with 5 snapshot pictures and push a notification to my ios device using 'Pushover' (which is really nice) - trigger a 'record'-script which records the video to HDD in best quality delivered by the cam (720P, 25 FPS) - transfering the video to my NAS where i can watch the videos wireless on my ios device using AirVideo (also a very nice product, no i'm not working for them ) This setup is running very stable ever since. I do reboot the camera once a day during the night though. I'm thinking about putting this setup on a lower powered raspberry pi as easy appliance since not much CPU is needed for this (even with 720P resolution). @jasauders How are you using the dual stream in your setup? Can you actually use those two streams in Motion? Are there any options which i'm missing? I also thought about it before. Is there a way to trigger an alarm manually with motion? This way PIR sensor could be connected via wire or even wireless to the server and trigger the event. BTW: I'm also a Linux guy.
  15. Hello, i recently bought a IPC-HFW2100 camera and played with it for a while. I can completely agree that the built-in motion detection of this camera is really rubbish. I did set up FTP record on motion detection but all it does was recording the whole night filling up my HDD However beside that the camera is very stable and the image quality is quite ok. I do reboot the camera once a day. I'm now using the camera in conjuction with this software for motion detection: http://www.lavrsen.dk/foswiki/bin/view/Motion (it's open source and i'm cheap ) I'm also doing video capture via a custom python script on motion detection (using openRTSP and FFMPEG). It was a little work to get it up and running but it's running stable ever since and it doesn't take too much CPU power. I'm thinking about running this setup on a cheap low power raspberry pi (2W). hdo
×