Thanks a lot for you help!!No default passwords on that firmware.
It will set the camera into an 'Inactive' state, that requires you to create your own strong password to 'Activate' it.
This is done easily using SADP, or via the web GUI.
Thanks a lot for you help!!No default passwords on that firmware.
It will set the camera into an 'Inactive' state, that requires you to create your own strong password to 'Activate' it.
This is done easily using SADP, or via the web GUI.
Actually - I just realised that you are likely using the NVR PoE ports, in Plug&Play mode.It will set the camera into an 'Inactive' state, that requires you to create your own strong password to 'Activate' it.
Perhaps the IP address has been changed.
Use the SADP tool to see if the camera is still responding.
There is no need to change the PC IP address for SADP to work, but if it finds that the IP address is in a different range you'll need to adjust the PC IP address to suit before you can access the camera with the browser.
Common hacked passwords are 1111aaaa asdf1234 and the original default ones are 12345 and 123456789abc
Does SADP find the camera?Use the SADP tool to see if the camera is still responding.
If it really is a Hikvision OEM brand - do you have any idea what series the camera is / what Hikvision model it is based on?I have a rebranded Hikvision (Knight)
SADP does find the camera, as does IVMS. I cannot find a physical reset button and I have not been able to find a similar hikvision model.Does SADP find the camera?
Is this a model with a reset button?
If it really is a Hikvision OEM brand - do you have any idea what series the camera is / what Hikvision model it is based on?
If you can work that out, it may be worth re-flashing the firmware with the Hikvision tftp updater tool.
Some resources here :
TFTPServ
Hikvision IP Camera Emergency Firmware Recovery TFTP. Check this thread for info on how to use this tool to un-brick your Hikvision camera.ipcamtalk.com
This for R0 :
Does it show the HTTP port is 80?SADP does find the camera
Does it show the HTTP port is 80?
Can you post an image - maybe we can help you to identify it.
The tftp updater does do some validation of the firmware that's being offered for installation.
Not as much as the web GUI, but should be worth a try.
Thank you, are there any threads I could use for direction - what I need and what I need to do?The serial console would be easy enough to try.
Do you know the hash algorithm of the encryption key?Yes, you have to do that to connect to each camera.
Suggest 10.0.0.150 for connecting to camera 1
And suggest 192.168.254.100 for camera 2
Camera 2 address is typical of the range used by Hikvision NVR PoE ports.
The Camera 1 address seems anomalous - but we can sort that later once you've got the admin password.
No - the PC IP address isn't assigned by the NVR. Contrary to popular belief the Hikvision NVR doesn't provide DHCP services.
But it does manage the network configuration of any cameras that's it's been given admin access to.
The 169.254.121.85 address on the PC is a 'self-administered address' that the PC provides for itself when there is no DHCP server, and no static address defined.
OK - when you've set the PC IP address to match each target camera as suggested above, use these URLs
Hopefully you will get 2 configuration files, which you can zip up and attach here.
Yes, I generated the above key for command-line OpenSSL as follows :Do you know the hash algorithm of the encryption key?
void make_key() {
unsigned char data[16]="abcdefg", key[64]={0}, iv[16]={0};
int i;
const EVP_CIPHER *cipher = EVP_aes_128_ecb();
EVP_CIPHER_CTX *ctx;
EVP_BytesToKey(cipher, EVP_md5(), NULL, data, 31, 1, key, iv);
for(i =0;i<=63; ++i) fprintf(stderr, " %x", key[i]);
fprintf(stderr," <-- key\n");
for(i =0;i<=15; ++i) fprintf(stderr, " %x", iv[i]);
fprintf(stderr," <-- iv\n");
for(i =0;i<=15; ++i) fprintf(stderr, " %x", data[i]);
fprintf(stderr, " %s", data);
fprintf(stderr," <--data\n");
}
That's correct - the code above is for camera configuration files for firmware versions that don't use SQLlite storage for the data.Recent DVR firmware using the dynamic key inputted by the user when exporting the device parameter. So the above command doesn't work.
Yes, I generated the above key for command-line OpenSSL as follows :
Code:void make_key() { unsigned char data[16]="abcdefg", key[64]={0}, iv[16]={0}; int i; const EVP_CIPHER *cipher = EVP_aes_128_ecb(); EVP_CIPHER_CTX *ctx; EVP_BytesToKey(cipher, EVP_md5(), NULL, data, 31, 1, key, iv); for(i =0;i<=63; ++i) fprintf(stderr, " %x", key[i]); fprintf(stderr," <-- key\n"); for(i =0;i<=15; ++i) fprintf(stderr, " %x", iv[i]); fprintf(stderr," <-- iv\n"); for(i =0;i<=15; ++i) fprintf(stderr, " %x", data[i]); fprintf(stderr, " %s", data); fprintf(stderr," <--data\n"); }
That's correct - the code above is for camera configuration files for firmware versions that don't use SQLlite storage for the data.
NVRs (and presumably DVRs though I've not looked) use quite different methods to encode exported configuration data, and also include individual device-specific data thta's needed to decode it.
See the @montecrypto hikpack tool that can do that, here :Please share the method for decrypting the NVRs configuration file.