ant-thomas / zsgx1hacks

Hacks for ZS-GX1 IP Camera and various Goke GK7102 based IP Cameras
370 stars 101 forks source link

Works on Digoo DG-W01F Camera #26

Open kaotix opened 6 years ago

kaotix commented 6 years ago

Not an issue, just tested on the Digoo DG-W01F camera and these scripts work. It appears to run damn near identical code to the cameras you've been discussing so I thought I'd test it as I've been doing a bit of hacking of my own.

Scripts run fine. I think even the wifi comes up but I haven't fully tested that yet it's currently wired for testing. I had looked at compiling the snx_rtsp_server for this camera so I'm going to test that today as an alternative to the p2pcam RTSP server.

Link for this camera is https://www.banggood.com/Digoo-DG-WO1F-Cloud-Storage-3_6mm-Lens-720P-Waterproof-Outdoor-WIFI-Security-IP-Camera-Motion-Detect-p-1194795.html

Zinstigator commented 5 years ago

Thanks for writing this code. I have applied to my Digoo DG-W01F and can now telnet into it. :-)

The main reason for applying the hack was so that I can fix the IP address of the camera also to redirect the recording to another location. Network Share or USB drive plugged directly into my router.

Onvif does not allow me to change the IP address - it states that the Underlying connection was closed. I have tried looking into start.sh within the home directory but cannot see anything specific for Ethernet IP address.

Also I have an issue trying to mount a Share.

I created a new mount point of 1 as zero is currently used and tried to mount to it using the command below.

The shares I am connecting to are completely open and set to Everyone R/W.

'mount -o port=2049,nolock,proto=tcp -t nfs 192.168.0.3:\T_Drive /mnt/mmc01/1/' (USB Drive inrouter)

'mount -o port=2049,nolock,proto=tcp -t nfs 192.168.0.23:\open /mnt/mmc01/1/' (FileShare)

I receive mount: 'mounting 192.168.0.23:open on /mnt/mmc01/1/ failed: Connection refused'

any help or assistance would be greatly appreciated.

Thanks.

Zinstigator commented 5 years ago

Thanks for writing this code. I have applied to my Digoo DG-W01F and can now telnet into it. :-)

The main reason for applying the hack was so that I can fix the IP address of the camera also to redirect the recording to another location. Network Share or USB drive plugged directly into my router.

Onvif does not allow me to change the IP address - it states that the Underlying connection was closed. I have tried looking into start.sh within the home directory but cannot see anything specific for Ethernet IP address.

Also I have an issue trying to mount a Share.

I created a new mount point of 1 as zero is currently used and tried to mount to it using the command below.

The shares I am connecting to are completely open and set to Everyone R/W.

'mount -o port=2049,nolock,proto=tcp -t nfs 192.168.0.3:\T_Drive /mnt/mmc01/1/' (USB Drive inrouter)

'mount -o port=2049,nolock,proto=tcp -t nfs 192.168.0.23:\open /mnt/mmc01/1/' (FileShare)

I receive mount: 'mounting 192.168.0.23:open on /mnt/mmc01/1/ failed: Connection refused'

any help or assistance would be greatly appreciated.

Thanks.

I have set the IP address using ifconfig. I am sure you have to save it in an etc location though for it to be permanent. My Unix is very rusty its been years since i have used it.

Zinstigator commented 5 years ago

I have edited the start.sh file within the /home directory setting the ip address. I can see on bootup it starts to use the new address for a few seconds it then seems to revert back to the old DHCP address. A

I have managed to get it to keep the correct TZ now with the echo statement within start.sh

hr1179 commented 5 years ago

After a long time I tried again to get my camera working. The first time it was working, but now I'm not able anymore to connect to the rtsp stream. My first assumption was a network issue but then I recognized that there was an issue with the sdcard. So I used another one and also enable the permanent hack. But still connection was not possible. So I checked if the rtsp ports are listening at all, but it seems they are not:

# netstat -anp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN      137/tcpsvd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      135/dropbearmulti
tcp        0      0 0.0.0.0:7101            0.0.0.0:*               LISTEN      179/p2pcam
tcp        0      0 0.0.0.0:7103            0.0.0.0:*               LISTEN      179/p2pcam
tcp        0      0 0.0.0.0:3201            0.0.0.0:*               LISTEN      157/tees
tcp        0      0 192.168.1.22:22         192.168.1.21:49277      ESTABLISHED 225/dropbearmulti
tcp        0      0 :::8080                 :::*                    LISTEN      130/busybox
tcp        0      0 :::22                   :::*                    LISTEN      135/dropbearmulti
tcp        0      0 :::23                   :::*                    LISTEN      185/telnetd
udp        0      0 0.0.0.0:8001            0.0.0.0:*                           179/p2pcam
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node PID/Program name    Path
unix  2      [ ACC ]     STREAM     LISTENING       1033 179/p2pcam          /tmp/aaa
unix  3      [ ]         DGRAM                       837 157/tees            /var/run/tees.sock
unix  2      [ ]         DGRAM                      1045 179/p2pcam

Shouldn't it listen on port 554 and 5000? Any idea?

hr1179 commented 5 years ago

I've connected a UART interface now and there is this error message: ERROR: can not get mac from net interface, please check hardware...

But ifconfig shows that hwaddr for eth0 (wlan not used up to now) is set correctly. Could this be the reason for the issue in my post above?

tonbor commented 5 years ago

tcp 0 0 192.168.1.155:554 192.168.1.249:50264 ESTABLISHED 210/p2pcam tcp 0 0 192.168.1.155:554 192.168.1.249:50243 ESTABLISHED 210/p2pcam No only 554

tonbor commented 5 years ago

settings in cls.conf [cls_server] fixip = eth0 ip = 192.168.X.XXX gw = 192.168.X.X

hr1179 commented 4 years ago

I've created the cls.conf in /home directory and it is used, but the camera is still not listining on port 554 and I'm therefore not able to connect. Any other ideas. Is there a way to restore the image or at least the /home directory?

hr1179 commented 4 years ago

Still no success. Does anyone have a firmware.bin for Digoo DG-W01F?

tonbor commented 4 years ago

Wrong directory for cls.conf

hr1179 commented 4 years ago

Ok, put onto sdcard, correct? But still does not work. Even if I restore hack, camera is not connecting to any external cloud service.

tonbor commented 4 years ago

In the process, I found out that it is possible in / home or on a USB flash drive (checked / mnt / mmc01, vfat and exfat are supported) to put the cls.conf file with something like this [cls_server] fixip = eth0 ip = 192.168.1.123 gw = 192.168.1.1 netmask = 255.255.255.0 dns = 192.168.1.1 ssid = wifiname passwd = 129345678

to set the network configuration. The same parameters are copied to devParam.dat. If you remove fixip = eth0, then wifi will be activated.

hr1179 commented 4 years ago

Yes, I saw it also via UART interface that cls.conf was found on /home. But network is setup correctly. The issue is, that the camera is not listing on port 554.

tonbor commented 4 years ago

rtsp://192.168.1.XXX:554/ch0_0.h264

hr1179 commented 4 years ago

what does netstat -an show in your case? For me it does not show listening on port 554 (see post above), so trying another stream may not help.

tonbor commented 4 years ago

tcp 0 0 192.168.1.XXX:554 192.168.1.XXX:44185 ESTABLISHED

hr1179 commented 4 years ago

and also listening if it's not yet established?

tonbor commented 4 years ago

It is established, two nvr's and android app

hr1179 commented 4 years ago

What does it show in netstat if it's not yet connected. Something like this? tcp 0 0 0.0.0.0:554 0.0.0.0:* LISTEN

Nobi83 commented 4 years ago

Hi guys! After a lot of searching and trying, I managed to set up the DG-W01F IP Camera into Synology Surveillance Station. Data capture works on NAS. Hope I can help someone with this. "rtsp://admin:passw0rd@192.168.1.xx:554/onvif1" --> It didn't work for me. Activation failed. "rtsp://admin@192.168.1.xx:554/onvif1" --> Works without a password.

Cam_1

vinnywebmaster commented 4 years ago

Hi guys! For you, who have much more experience, which may be a silly question, but I am doing what I have tried everything. I believe my DG-W01F camera has crashed because I can't connect it in any way. The first time I put it into operation and the camera emitted the "reset success" sound, after that the camera did not emit any more sound, just a small popping sound. I tried to connect and only succeeded this time. After that, I can't do it, not even through the cable, it doesn't appear on the network even though the green light on her RJ45 connector is flashing. I tried to install "zsgx1hacks-v0.4.zip" and "readonlyhack-v0.1.zip" and neither worked because it still does not appear on the network. I try to give the manual reset and also nothing, the camera does not respond to the command. What could I do to format and install any firmware that works? (It can be the original too). The camera is bricked. Thanks so much!

hr1179 commented 4 years ago

After a long time I tried again to get my camera working. The first time it was working, but now I'm not able anymore to connect to the rtsp stream. My first assumption was a network issue but then I recognized that there was an issue with the sdcard. So I used another one and also enable the permanent hack. But still connection was not possible. So I checked if the rtsp ports are listening at all, but it seems they are not:

# netstat -anp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:21              0.0.0.0:*               LISTEN      137/tcpsvd
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      135/dropbearmulti
tcp        0      0 0.0.0.0:7101            0.0.0.0:*               LISTEN      179/p2pcam
tcp        0      0 0.0.0.0:7103            0.0.0.0:*               LISTEN      179/p2pcam
tcp        0      0 0.0.0.0:3201            0.0.0.0:*               LISTEN      157/tees
tcp        0      0 192.168.1.22:22         192.168.1.21:49277      ESTABLISHED 225/dropbearmulti
tcp        0      0 :::8080                 :::*                    LISTEN      130/busybox
tcp        0      0 :::22                   :::*                    LISTEN      135/dropbearmulti
tcp        0      0 :::23                   :::*                    LISTEN      185/telnetd
udp        0      0 0.0.0.0:8001            0.0.0.0:*                           179/p2pcam
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node PID/Program name    Path
unix  2      [ ACC ]     STREAM     LISTENING       1033 179/p2pcam          /tmp/aaa
unix  3      [ ]         DGRAM                       837 157/tees            /var/run/tees.sock
unix  2      [ ]         DGRAM                      1045 179/p2pcam

Shouldn't it listen on port 554 and 5000? Any idea?

It is quite unpleasant. I've found now the reason for the issue. I use a power supply with adjustable voltage, and for any reason I've changed to 5V. With 12V it works again ;-)

Sorry for the confusion.

ikemomota commented 2 years ago

anybody still have this camera working? mine would not save to sdcard anymore. firmware: 3.4.0.1031 i need p2pcam.tar.gz from this camera, if somebody have it, pls share. thanks

Zinstigator commented 2 years ago

Mine no longer records to the SD card either. Firmware 3.2.8.0208

hondcxrider commented 10 months ago

Im new to all this, so take it easy. I have a digoo w02f. I've installed hack v04. All working ok, I'm using putty to telnet to it and winSCP ( ftp) to look at the file system, edit files. I'd like to connect the wifi, I've modified the wpa_supplicant.conf and put in the cls.conf file. but no joy. I don't want to use the DHCP server on my router but a fixed address in the long run, which with some success I achieved in eth0. I'm confused mainly by file locations. files are present but not where I expected them i.e. my debug_cmd.sh file is found in media, (also on \mmt\mmc01\ 0) not in \root, where the only file is init. Any ideas? thanks in advance