Jump to content

mroek

Members
 View Profile  See their activity

  • Content Count

    150

  • Joined

  • Last visited

Posts posted by mroek

  3. Posted

    Should you buy a 3200S, yes, if you need more illuminators, LOL. Seriously, for a better value get the Hikvision mini IR bullet, $169, you can run it at 1080P or 3MP and get it from a U.S. distributor/reseller, so you get a warranty with it and is the same size as the HFW2100. You can even telnet into it, same user/password as the browser user/password, why you want to telnet I don't know but you can.

    Sounds good, but I'm not in the U.S, so I'd probably better look for a different source. Thanks for the tip, anyway.

    There is one possible drawback compared to the 3200S, and that is the lens focal length. The 3200S goes down to 3.6 mm, while the Hikvision is 4 mm with the shortest lens option.

  4. Posted

    When I telnet'ed into the camera I'm pretty sure there wasn't an ftpd running as I was trying to figure out how to change the logo on it for fun but possibly ssh. Also, much of the camera's OS was on a zipped mounted file system that is read only meaning you can't write to individual files but you can write over the entire volume and remount it. At best I thought you can take an image on an SD card and copy it over, but this model does not have an SD card slot.

     

    The best use of a bricked HFW2100 honestly is as an IR illuminator. They have a pretty bright LED illuminator and if I bricked one, that's what I would do. And it's setup to light up a night independent of camera functionality and small enough. Check the price of a PoE IR illuminator from Raytec for $400, makes this a bargain. When life deals you lemons, make lemonade.

    Well, I won't go bankrupt from this, so I might just have to take you up on that advice.

    I'm considering whether I should replace the camera with a 3200S instead. A bit more resolution, but still pretty small.

  5. Posted

    Can you FTP a new copy of sonia onto the cam? I spent a bit of time with a different Dahua and was unable to get FTP running on it, but I'm no expert in these matters.

     

    If you think there's some corruption at the hardware level, you could rename the existing sonia and copy a new one so it goes into a new location. I don't know if there's a TFTP serial interface on the 2100 like there is on the 3300, but if there is, that might be helpful.

     

    If all else fails, there's the famous Dahua trash-can warranty.

    It is possible that there is a physical fault on the internal flash memory, if so there really isn't much to do.

     

    I could probably get a new copy of sonia onto the camera, but not in the location where it normally resides. The file system is read-only, so to do that you'd need to flash the entire filesystem to the correct address in the flash. That's easier said than done, but not impossible if you have the knowledge.

     

    There is a tftp-daemon running on the camera, but I'm not sure if it is meant to work on IP or serial/rs232. And even if I knew, I'd also need to know which file it would want.

  6. Posted

    Hi,

     

    During the night one of my HFW2100-cameras had gone wonky, and refused to supply any video stream. It was possible to get into the web interface, but no video stream there either, just some message (with a big font in the video window) in chinglish stating something along the lines of "resource limited". When trying to get into some of the other menus, popups with messages about "config read failed" appeared.

     

    My initial thought was that the internal flash memory had been corrupted, and since I saw that newer firmwares had appeared online (on this forum in the Dahua firmware thread), I tried upgrading the firmware (from the web interface). This seemed to work, at least the camera came back online with the new version, but unfortunately there were still error messages regarding the config.

     

    I then tried to reset the camera with the physical reset button on the back, which was a big mistake. The web interface is no longer available, but I can login via telnet. However, the connection is lost after a short while, probably because the camera crashes and goes into a reboot loop. I can see that it tries to start the main executable sonia, but I hink this is what kills it. This is the list of the running processes:

     

    # ps

    PID Uid VSZ Stat Command

    1 root 2812 S init

    2 root SW [posix_cpu_timer]

    3 root SW [softirq-high/0]

    4 root SW [softirq-timer/0]

    5 root SW [softirq-net-tx/]

    6 root SW [softirq-net-rx/]

    7 root SW [softirq-block/0]

    8 root SW [softirq-tasklet]

    9 root SW [softirq-hrtimer]

    10 root SW [softirq-rcu/0]

    11 root SW< [desched/0]

    12 root SW< [events/0]

    13 root SW< [khelper]

    14 root SW< [kthread]

    26 root SW< [kblockd/0]

    27 root SW< [cqueue/0]

    28 root SW< [kseriod]

    35 root SW< [khubd]

    84 root SW [pdflush]

    85 root SW [pdflush]

    86 root SW< [kswapd0]

    87 root SW< [aio/0]

    88 root SW< [cifsoplockd]

    89 root SW< [cifsdnotifyd]

    686 root SW [mtdblockd]

    692 root SW< [dm_spi.0]

    774 root SWN [jffs2_gcd_mtd7]

    778 root SWN [jffs2_gcd_mtd8]

    819 root 2816 S /utils/telnetd

    826 root SW< [motord]

    830 root 2276 S /utils/upgraded

    831 root 10348 S /utils/syshelper 120

    964 root 2812 S /bin/sh /etc/init.d/appd

    973 root 1596 S pppd

    1005 root 2816 S /bin/sh

    1006 root 2816 S -sh

    1009 root 2816 R ps

     

    If I try to manually launch sonia, I can see that it fails with a segmentation fault:

     

    # /usr/bin/sonia

     

    [libdvr] libdvr.so Build on Dec 19 2012 at 10:36:51.

    [libdvr] SVN NUM: 4322.

    [libdvr] no new hwid scheme!

    00:34:23|[libInfra] warn Some [ONVIF2.2] files are not commit to SVN server. It compied wtih local modified files.

    00:34:23|[libInfra] info check include version:manager

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Component 81001

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Database 78701

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/ezutil 4497

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/gtest 42100

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Infra 94250

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Json 64221

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Lua 518

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Manager 95833

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Memory 63431

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Branches/P_Include_Ultimate_2011.05.09/NetProtocol 82093

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Pal 94690

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/RPCServer 82105

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Stream 80720

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Utils 70561

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Zlib 82304

    00:34:23|[libInfra] info check include version:Infra

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Component 91309

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Infra 94250

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Memory 63431

    00:34:23|[libInfra] info URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Utils 88482

    00:34:23|[libInfra] error check include version failed

    00:34:23|[libInfra] error manager URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Component 81001

    00:34:23|[libInfra] error Infra URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Component 91309

    00:34:23|[libInfra] error manager URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Utils 70561

    00:34:23|[libInfra] error Infra URL: http://10.6.5.2/svnpl/Renascence/Include/Trunk/Utils 88482

    00:34:23|[libInfra] error check include version failed, assert

    [libaudio] libaudio build @ Aug 4 2012 15:54:42

    [libaudio] svn info:·¾¶: Trunk URL: http://10.6.5.2/svn/Camera_api/libaudio_DM365/Trunk °æ±¾¿â¸ù: http://10.6.5.2/svn/Camera_api °æ±¾¿â UUID: 83ec8bce-ee28-0410-b94f-c8a3b29becdd °æ±¾: 5569 ½ÚµãÖÖÀà: ?¼ ×îºóÐ?jÄ×÷Õß: wang_kefu ×îºóÐ?jI?: 5569 ×îºóÐ?jÄʱ¼ä: 2012-08-04 15:39:00 +0800 (Áù, 2012-08-04)

    [libaudio] FRAME_SIZE=1600

    [libenc] =========libenc version @V0.06_HD@20100820 build time: Apr 17 2012:20:12:59========

    [libenc] build options:tags2.0 SUP_MJEG

    00:34:23|trace main( /usr/bin/sonia)

    00:34:23|trace ******************app lib info******************

    00:34:23|[libInfra] info [*] Function 1.1.0.116752 Built in 2013/ 5/16 [*]

    00:34:23|[libInfra] info [*] Function 1.1.0.116752 Built in 2013/ 5/16 [*]

    00:34:23|[libInfra] info [*] Manager 1.0.0.105127 Built in 2013/ 3/ 9 [*]

    00:34:23|[libInfra] info [*] Function 1.1.0.116752 Built in 2013/ 5/16 [*]

    00:34:23|[libInfra] info [*] Storage 1.0.0.0 Built in 2013/ 5/17 [*]

    00:34:23|[libInfra] info [*] Function 1.1.0.116752 Built in 2013/ 5/16 [*]

    00:34:23|[libInfra] info [*] Function 1.1.0.116752 Built in 2013/ 5/16 [*]

    00:34:23|trace ******************app lib info******************

    00:34:23|[libInfra] trace CThreadManager::CThreadManager()>>>>>>>>>

    00:34:23|[libInfra] info [*] Infra 1.0.0.94251 Built in 2012/12/22 [*]

    00:34:23|[libInfra] trace CThreadManager::CThreadManager()>>>>>>>>>

    00:34:23|[libInfra] debug ThreadBody Enter name = NetFramework, id = 1011, prior = N64, stack = 0x406a1e24

    00:34:23|[libInfra] debug ThreadBody Enter name = NetFramework, id = 1012, prior = N64, stack = 0x408a1e24

    00:34:23|[libInfra] debug ThreadBody Enter name = NetFramework, id = 1013, prior = N64, stack = 0x40aa1e24

    00:34:23|[libInfra] debug ThreadBody Enter name = NetFramework, id = 1014, prior = N64, stack = 0x40ca1e24

    00:34:23|info R3Server Start @port[42323]

    00:34:23|[Manager] trace CMagicBox::config '/var/tmp/pd/ProductDefinition'

    [libfvideo] ############: g_videoin_channels = 1

    00:34:23|[libInfra] debug ThreadBody Enter name = TimerManager, id = 1015, prior = N1, stack = 0x40ffee24

    [libdvr] info->deviceType:IPC-HFW2100

    [libdvr] devalias:IPC-HFW2100

    [libdvr] armrate = 270

    [libdvr] @@@@ buf = TZC2LV05000081

    [libdvr] thread_led_helper_hf3030 create success

    [libdvr] PID (thread_led_helper_hf3030 |pid = 1019 ):

    [libdvr] getproc_ifnet6:589

    [libdvr] get value from /proc/net/if_inet6

    [libdvr] 00000000000000000000000000000001 bef44798 bef447a4 bef447a0 bef4479c lo

    [libdvr] get value from /proc/net/if_inet6

    [libdvr] 20010250300000010000000000010002 bef44798 bef447a4 bef447a0 bef4479c eth0

    [libdvr] get value from /proc/net/if_inet6

    [libdvr] fe800000000000009202a9fffe0b2e73 bef44798 bef447a4 bef447a0 bef4479c eth0

    [libdvr] set success

    [libdvr] set success

    pppoe enable have Disabled!

    Start Upnp Mini Server success! listen port: 49152

    DHBonjour: Registered service[0x4047ef00] name 'TZC2LV05000081', type '_http._tcp.', port 80

    ==============> libWireless version: 1.0 - Complie time Nov 19 2012 13:33:54 SvnVersion = 4167<=============

    [libWifi]hotplug_thd pid=1025--../wifi_lib/wifi_api.c(3397)wlan_hotplug_thd

    [libWifi]watch_thd pid=1026--../wifi_lib/wifi_api.c(4284)wlan_watch_thd

    DHBonjour: Callback: Registered

    [libdisk] WARN : before----------------

    [libdisk] Open /sys/bus/mmc/devices/ failed

    [libdisk] Find 0 device

    [libdisk] WARN : before----------------

    [libdisk] Snap a hotplug

    umount: Invalid argument

    ==>videoout_channels=0

     

     

    [libfvideo] =========libfvideo Build on May 16 2013 at 16:24:48.=========

    [libfvideo] SVN NUM: 9011.

     

    [libfvideo] priv->caps.multiOptions 1

    ##: analyse = 1

    msghander->msgkey 269422157, /tmp/msgPipe

    ------: msgInit Create DSpborad ----

    [libfvideo]: create key sucess /tmp/msg2ato648

    msgget sucess

    [libfvideo]: FUN-> lib_send_data_to_dsp, pthread_id : 1031

    [libfvideo] priv->caps.whiteBalance 2

    [libfvideo] maxWidth 1920,maxHeight 1080

    [libfvideo] WARN (../../src/videoin/chips/imx03x/videoin_imx03x.c|videoin_create_series|839): Failed to open device errno=2

    [libfvideo] ERROR (../../src/videoin.c|do_videoin_creat|738): videoin_create failed,fchip=3

    =========================== TRACE START ===================================

    Tid:1010, Exception type : SIGSEGV

    PC:[0x0003af70] (0x0003aee8--0x0003af8b) Unknown

    PC:[0x402947c0] (0x0003aee8--0x0003af8b) __default_rt_sa_restorer_v2 + [0x0]

    PC:[0x003d845c] (0x0003aee8--0x0003af8b) Unknown

    PC:[0x003d89a4] (0x003d80b4--0x003d86df) Unknown

    PC:[0x003d8cb4] (0x003d86e0--0x003d8a1b) Unknown

    PC:[0x00400358] (0x003d8a1c--0x003d8ebf) Unknown

    PC:[0x004003f8] (0x00400338--0x004003cf) Unknown

    PC:[0x00035a14] (0x004003d0--0x0040042b) Unknown

    PC:[0x4027dbec] (0x00035104--0x00035f17) __libc_start_main + [0x104]

    PC:[0x00034a80] (0x4027dae8--0x4027df53) Unknown

    =========================== TRACE END ===================================

    #

     

    Any suggestions that I can try, or should I just admit defeat and shed a few tears?

  8. Posted

    The next firmware for the 2100 has quite a few improvements, including BLC/HLC/WDR like on some of it's siblings, and also customizable white balance, so that you can choose a specific area in the image you want it to use to calculate white balance. That's quite useful if you have some neutral area in the image.

     

    And the most important: They have fixed the noise reduction issue that caused a lot less detailed images.

  11. Posted

    Does anyone know if it's possible to open up a Dahua HDW2100 IP Camera and change lens? I'm not quire sure how to get the ball part of the camera open.

     

    Any help or links would be appreciated

    You don't have to do anything with the "ball part". There are three recessed screws that hold the housing together, and after opening that, you have to remove the tree philips screws that attach the lens board to the front part of the housing. You can see some pictures in this thread: http://www.cam-it.org/index.php?topic=3882.0

  13. Posted

    What's not so great is that there seems to be no easy way of fixing the builtin security vulnerability that admin/admin seems to be hardcoded for login via Onvif. In the current latest release, Onvif sits at port 9988, so you can at least avoid exposing that port to the internet even if you want to set up access to the web interface (at port 80). Unfortunately, it may seem as if Dahua has moved Onvif to port 80 in later test versions, and if admin/admin still works for Onvif, then anyone can actually reboot your camera or reset the config (in addition to other stuff) if you have set up internet access to your camera on port 80.

     

    What they need to do, is to allow the user to decide which port Onvif should work with, and they also really, really, really need to link the Onvif account info to the actual accounts defined in the camera, not a hardcoded value.

  15. Posted

    I know I'm doing something wrong. Do you mind pointing me in the right direction ?

     

     

    (none) login: root

    Password:

    # cd /mnt/mtd/Config

    # ftpget /mnt/mtd/Config/Account1

    BusyBox v1.9.1 (2011-10-28 09:19:04 CST) multi-call binary

     

    Usage: ftpget [options] remote-host local-file remote-file

     

    Retrieve a remote file via FTP

     

    Options:

    -c,--continue Continue previous transfer

    -v,--verbose Verbose

    -u,--username Username

    -p,--password Password

    -P,--port Port number

     

    #

     

    You can't FTP into the cameras. You must login to a shell with telnet, and then use the builtin commands ftpget and ftpput to move files to and from an FTP server in your network.
    First, do you actually have an FTP-server in your network? If yes, then you must run this command to get the file onto that server:

     

    ftpput -u -p Account1 Account1

     

    You must of course substitute user/password and server-ip with the appropriate values for your server. It is possible that you also need to supply a target directory on your server, but since you should be in control of that server, you'd be the one to know that.

     

    If I'm going to be brutally honest with you, it does not sound like you have enough knowledge to be doing these things. That's precisely why I did not supply any detailed instructions, because anyone with the required knowledge would immediately understand what to do.

     

    In any case I will not be responsible if you brick your camera.

  17. Posted

    Some simple tips:

    3. Ask about firmwares and firmware policy; usually, an official DAHUA distribuitor will not give you the firmware, but it will update your product (via Internet) for free

    That sounds dubious. I would most definitely NOT want to have ANY firmware updated by anyone else over the internet. Firmware updates should most definitely be performed locally.

     

    I still think that Dahua's firmware policy is unwise. I can't really see any problems in them posting the official firmwares on their own site. If they are worried about cross-updating with branded products (like Q-See) it is no problem for them to add functionality in their firmware to make sure that's impossible (at least by normal updating from the web interface).

     

    Firmwares will always leak, so why not maintain a reliable source instead?

  18. Posted

    Secondly, you can't fix any bugs... the whole system of DAHUA runs in a single binary format file... you can't modify it. But you can add to the embedded system some stuff.
    I've looked a bit at this lately, and you are (of course) correct that Dahua packs most of their system in a single binary. What I found amusing, is that they seemingly named that binary after the DM365 (DaVinci SoC) product line manager at Texas Instruments. The binary application is called sonia, and the name of the lady at Texas Instruments is... drumroll... Sonia Ghelani. Here she is in a
    too. Could of course be coincidental, but I am quite convinced that it isn't, so I'm declaring this to be a Fun Fact.

     

    I've also looked a bit at Dahuas firmware images, and while it is possible to extract the different image files from the binary, Dahua seems to have added an additional (and probably proprietary) header to those images, making it more difficult to manipulate. Your standard open source tools (like Firmware Mod Kit) can't work on them out of the box. The names are also confusing, they all include "Cramfs" in the names, but not all of them are actually Cramfs-images.

  19. Posted

    Yes, it is a real shame that they don't just post new firmware versions on their own site, instead of forcing everyone to go to their distributors to get firmwares. There are no valid reasons to do it this way, as far as I can tell. Virtually every other manufacturer of devices that can be updated with new firmware will allow users to download the relevant files from their own site.

  21. Posted

    I have now spent some time tinkering with the cameras, and I have found a way to modify (and delete) the accounts even if the web interface does not allow that. The camera config is stored in two locations:

     

    /mnt/backup/Config

    /mnt/mtd/Config

     

    The backup location appears to be just that, a backup of the config. The config that is actually used is the latter, but files will be copied to the backup folder automatically.

     

    The accounts are stored in this file:

    /mnt/mtd/Config/Account1

     

    Unfortunately, Dahua has not included any text editor (not even vi, can you believe it), so to edit the file you need to have a FTP server in your network, and then use ftpput to copy the file to the FTP, modify it on your computer, and ftpget it back onto the camera.

     

    The account file is clear text, and easy to read. This is how it looks by default (serial number has been edited by me):

     

    // ÄÈϾÄÕʧÅäÖãÄÈϾÄ×é°üº×éÃûºÍ×éÃèÊö¾È¹ØÌîÏî£ÄÈϾÄÓç°üºÓçÃû£Óç
// ÃèÊö£ËùÊô×éÃû£ÃÜÂë£ÊÇ¡ñš²Ïí¾È¹ØÌîÏdefaultÓç²ÓÃдÔÚϹíÖÐ¥£

{
  "DevInformation" : {
     "SerialID" : "TZC2Lxxxxxxxxx"
  },
  "Groups" : [
     {
        "AuthorityList" : [
           "ShutDown",
           "Monitor_01",
           "Replay_01",
           "Record",
           "Backup",
           "MHardisk",
           "Account",
           "Alarm",
           "QueryLog",
           "DelLog",
           "SysUpdate",
           "AutoMaintain",
           "GeneralConf",
           "EncodeConf",
           "RecordConf",
           "ComConf",
           "NetConf",
           "AlarmConf",
           "VideoConfig",
           "DefaultConfig",
           "VideoInputConfig"
        ],
        "Id" : 1,
        "Memo" : "administrator group",
        "Name" : "admin"
     },
     {
        "AuthorityList" : [ "Monitor_01", "Replay_01" ],
        "Id" : 2,
        "Memo" : "user group",
        "Name" : "user"
     }
  ],
  "Users" : [
     {
        "AuthorityList" : [
           "ShutDown",
           "Monitor_01",
           "Replay_01",
           "Record",
           "Backup",
           "MHardisk",
           "Account",
           "Alarm",
           "QueryLog",
           "DelLog",
           "SysUpdate",
           "AutoMaintain",
           "GeneralConf",
           "EncodeConf",
           "RecordConf",
           "ComConf",
           "NetConf",
           "AlarmConf",
           "VideoConfig",
           "DefaultConfig",
           "VideoInputConfig"
        ],
        "Group" : "admin",
        "Id" : 1,
        "Memo" : "admin 's account",
        "Name" : "admin",
        "Password" : "6EFF35CB0D61578D8D0A5351CA74ADB5",
        "Reserved" : true,
        "Sharable" : true
     },
     {
        "AuthorityList" : [
           "ShutDown",
           "Monitor_01",
           "Replay_01",
           "Record",
           "Backup",
           "MHardisk",
           "Account",
           "Alarm",
           "QueryLog",
           "DelLog",
           "SysUpdate",
           "AutoMaintain",
           "GeneralConf",
           "EncodeConf",
           "RecordConf",
           "ComConf",
           "NetConf",
           "AlarmConf",
           "VideoConfig",
           "DefaultConfig",
           "VideoInputConfig"
        ],
        "Group" : "admin",
        "Id" : 2,
        "Memo" : "888888 's account",
        "Name" : "888888",
        "Password" : "261E49200CB8EA1800A9568504FBA0C3",
        "Reserved" : true,
        "Sharable" : true
     },
     {
        "AuthorityList" : [ "Monitor_01", "Replay_01" ],
        "Group" : "user",
        "Id" : 3,
        "Memo" : "666666 's account",
        "Name" : "666666",
        "Password" : "A36040975B36C11630E534AB561D77AD",
        "Reserved" : true,
        "Sharable" : true
     },
     {
        "AuthorityList" : [ "Monitor_01" ],
        "Group" : "user",
        "Id" : 4,
        "Memo" : "default account",
        "Name" : "default",
        "Password" : "B1AF93D7B8D1C96E4563AB36095687FA",
        "Sharable" : true
     }
  ]
}

     

    As you can see, there are four users defined: admin, 888888, 666666 and default. If you just want to be able to delete the users from within the camera web interface, change the "Reserved"-property from true to false. Then, after putting the file back onto the camera, reboot (just use the reboot command from the shell) it to make the changes effective. After the camera has rebooted, you can now do what you want with the accounts. A word of caution, though: I have only tried deleting one of the extra accounts, so I don't know for sure if renaming/deleting the admin account will have any adverse effects (clearly you must retain at least one account with full admin privileges), but I believe it should work just fine. Don't try to edit the passwords manually, they are just hashes (and also salted, I think), only change them from the web interface.

     

    This is just for information, I'm not responsible for anything you might do! I'm not including detailed instructions here, because those that would want to do this already have the required knowledge.

  22. Posted

    Interesting.. Thanks to you, I found a new firmware for my Dahua 2100..

    Actual : Device Type IPC-HFW2100 (PAL)

    Software Version 2.100.0001.0.R, build : 2012-10-31

    WEB Version 3.0.0.0

     

    There : General_IPC-HX2XXX_Eng_P_BootSpi_V2.100.0001.0.R.20121031.bin

    The name doesn't specify if it's a PAL version, but the website is a Spanish one, so a European. It should be a PAL one, isn't it ?

     

    Anyway, I'm a little bit afraid of upgrading it... I don't want a brick...

    First: The Spanish site firmware for the HFW2100 is an older version: General_IPC-HX2XXX_Eng_P_V2.100.0000.8.R.20120523.bin.

    Please note the difference between HFW and HDW, where the latter is the dome version, and the former is the bullet.

     

    The version you found is for the HDW-version, and it has the same version number as you already have on your camera. The latest released version for your camera is the one you already have, which is:

     

    2.100.0001.0.R, build : 2012-10-31

     

    In other words: Don't flash your camera with anything from the Spanish site.

×