search

guino / Merkury1080P

Merkury1080P (CW017) Rooting and Customization
77 stars 16 forks source link

Port 8554 not opened #18

Open vossim opened 2 years ago

vossim commented 2 years ago

I tried patching manually, and I tried a patch available on https://github.com/guino/ppsapp-rtsp for my device (firmware: ppstrong-a3-tuya2_lsc-4.0.6.20210311). When configured correctly I can use the cgi-bin scripts to get mjpeg and snap to work, but for some reason RTSP doesn't get started and I can't connect to port 8554 at all.

I have attached a log of my latest attempt of manually patching the ppsapp, if it would be better to include a log of the patch I found on ppsapp-rtsp, please let me know.

Could you tell me what I'm doing wrong here? ppsapp.log

guino commented 2 years ago

@vossim did you try to just enable onvif in the tuya_config.json file to see if it works ? many people on 4.0.6 have been able to make it work without patching that way (it's what I would try first).

Your log shows rtsp_server module started but doesn't show the debug lines associated with starting onvif so it sounds like the patch didn't work. Most 4.0.6 firmware only have ONVIF (no old style rtsp code) which means you have to use rtsp://IP:8554//Streaming/Channels/101 and rtsp://IP:8554//Streaming/Channels/102 -- I have heard many reports that it doesn't always come up with port 8554 open (either becasue it's UDP or hidden somehow by the device) but still works.

If the json setting and/or the patch doesn't work let me know and I can take another look but usually I only post it to the list if it works, let me know.

vossim commented 2 years ago

I was able to figure out what was going on yesterday. The good news: both RTSP and ONVIF work fine, the not so good news for me: it doesn't work across VLANs. I've got my chinese devices on a separate VLAN in their own subnet, and for some reason I can't connect to the cameras if I'm not connected to the same VLAN.

guino commented 2 years ago

@vossim That's only good news as far as I'm concerned -- you really don't want the feed accessible other than from the same vlan/lan of the device. You can make firewall/network rules to limit/grant access to the feed as you like OR you can create iptables rules to enabled/disabled access on the device based on web requests or as you see fit.