

- #ADD DEVICE TO REOLINK CLIENT ANDROID#
- #ADD DEVICE TO REOLINK CLIENT SOFTWARE#
- #ADD DEVICE TO REOLINK CLIENT PASSWORD#
- #ADD DEVICE TO REOLINK CLIENT MAC#
So, your Windows machine says, "I want 192.168.2.x, and sends that packet to 192.168.1.1, which knows where to find 192.168.2.x" If your Windows machine had a sub-net mask of 255.255.0.0, it would say, "192.168.2.x is on my sub-net, so I'll do an ARP request to find its MAC address. When the IP is not on the same sub-net, it sends those packets to the MAC address of the gateway device, which then knows which router port knows where to find that IP. Then, it sends packets directly to that MAC address. My naive understanding is that when a device wants to send packets to an IP address that is on the same sub-net, it does an ARP request to get the MAC address of the device. (I enjoy the minutia of networking, but have not reached any significant degree of expertise.)
#ADD DEVICE TO REOLINK CLIENT SOFTWARE#
Clearly it is not necessary for the Windows client software to communicate with the camera.Ĭould you be more specific about how you "configured the routers" to allow traffic from one sub-net to the other? but I haven't been able to find any information that indicates whether this type of outbound connection from the camera to the NVR is necessary.

If I know what ports it needs I can fix the router settings. For example, perhaps the camera needs to establish an outbound connection to the NVR? If so, then that would explain my issue because there may be some firewall rule in my router that is blocking this. However, when I try to add this camera through the NVR console (by IP address, exactly how I added the other two cameras) it just shows up as OFFLINE.īecause I am able to access the camera from a laptop on the same subnet as the NVR without any issues, my guess is that there is some difference between how the Windows client software communicates with the camera vs how the NVR and camera communicate. Using a laptop that is on the 192.168.1.0/24 subnet I am able to connect to the 192.168.2.200 camera via both browser and the ReoLink Windows client app.
#ADD DEVICE TO REOLINK CLIENT ANDROID#
Using a phone that is on the 192.168.1.0/24 subnet I am able to connect to the 192.168.2.200 camera via both browser and the ReoLink android app. I have configured the routers to allow traffic from the first subnet to the camera, and this appears to be working fine. The third camera is in another building with a different subnet for security purposes. The NVR and two of the cameras are on subnet 192.168.1.0/24, and they are playing nicely together. My site has two buildings that each have their own subnets. I have a decent amount of experience with networking and router configuration, and I want to disable UID on the cameras for security purposes. Enter the IP address of the device and click the blue Add button.I'm trying to set up a slightly advanced networking configuration for my Reolink cameras and NVR. Click the “+” at the right end of the Device, and then click IP/Domain. If you know your camera's IP address, you could add the device by IP address.
#ADD DEVICE TO REOLINK CLIENT PASSWORD#
Then the Device Login page will pop out and you need to input the device's login password to live view the device. The cameras in the same local network will automatically show up (if not, click the Refresh button), click the " +" button to add it. Then you need to input the login password of Reolink Duo 2 WiFi, and please note that the default username is "admin". You need to left-click this device or click the edit icon to call the Device Login page.
