Posts made by 3d_46279729295

I'm using a GearHead MP2850BLK and it works just fine.

I did try several I had around here before I found one that worked. It would be nice if Reolink would do this an publish a list of compatible models.

Yes. Thank you very much for sharing. This is a very handy "recipe" that could come in handy in the future.

2017-11-05_18-56-18.jpg

Consider window cling stickers that go inside the window rather than adhesive stickers that go outside of a window. Cling type sticker hold up much better in weather over the long term.

The NVR channel list in the PC application should show the aliases of the channels and not just "channel01," "channel02," etc. It's really difficult to remember what each channel is being used for.

It would be most helpful if there was a configuration setting that would allow the NVR to be configured to disable the internal NVR NAT and DHCP server functions. This would make the switch POE ports simply pass through data to the NVR LAN port. Doing this allows a person to have a single DHCP server on the network for all IP devices and also allows direct IP access to the POE cameras from other locations in the network.

What you are asking to do can be set up and will work just fine. The issue with not using a router is that the router is also usually the provider of your network DHCP services. If you have only a switch and not a router that is also providing DHCP services to your cameras, you will need to go into each camera and configure it with a static IP address on your network. Once the cameras have a static IP address they will connect to the NVR via external switch and the NVR WAN port.

If you plug the cameras into the NVR built in POE switch, the NVR has an internal DHCP server that will assign them IP addresses. Cameras connected to the NVR via the WAN port need to get their IP addresses some other way.

I use the NVR in my system remotely from the cameras and have them all go through a separate POE switch. I do use a router as a DHCP server to provide IP addresses to my cameras.

The LAN ports on the RLN are behind a router and NAT internal to the RLN box. DHCP is provided putting all RLN LAN devices in the 172.16.25.x subnet. DHCP IP addresses will only be provided to devices that have a Reolink MAC vendor ID. There is no IP connectivity from one LAN port to another LAN port on the RLN. You can see it's a very non-standard configuration from what you would normally expect to see. I'm not sure why they did it this way, but it really limits what you can do with the RLN LAN ports other than hooking up Reolink cameras.