#Scw networker pro camera in other subnet update#
Sadly, no firmware update can give the Networker line more processing power. I’m curious if this is an intended limitation due to security concerns about people mis-configuring their network and making their cameras world-accessible, or if it has to do with complexities in the network stack of the firmware. For example, our 2017 line included some cameras with new higher resolution chipsets that the image processor in our 2016 line cannot record. It seems this behavior is expected and documented, though: Use for streaming through any RTSP compatible player on the same local network as the Wyze Cam. However, this isn’t a sustainable long term solution for me, and probably is impractical for a lot of other people. Camera Subnet (assigned by NVR switch/router): 10.1.1.0/24 Ive tried (without success): Accessing cameras with at 10.1.1.x from my laptop on the Plugging my laptop into an empty port on the back of the NVR and accessing cameras. You need to tell router 2 what 192.168.5.x address those packets need to be routed to, because it has no way to figure that out on its own.
My camera server is on a different subnet than this camera, which means I have to do some NAT magic to make it look like my camera server is on the same subnet as the Wyze cams. Home Network Subnet (assigned by primary router): 192.168.5.0/24. Each packet sent by the NAS to the 192.128.5.x subnet will have a destination IP address of 192.168.1.115 (Router 2s WAN address), and SMB traffic will have a destination port of 445. I recently purchased two Wyze cams to investigate the potential of them being a low-cost addition to my existing RTSP camera infrastructure.Įverything seems to be working good, except I ran into one issue: RTSP is only accessible from the same network subnet that the camera is currently on.
0 kommentar(er)
