@user_612681119584296_612681119584296
Reolink have a proprietary protocol for NVR auto assigning IP's that the cameras prefer over DHCP.
Having multiple IP assigning servers on the same network will always cause issues.
All devices configured for DHCP are prone to IP reassignment unless a layer 3 switch with effective configured security policy is in use.
Your assumptions that any client is safe from another DHCP server getting connected to a network are mislead.
The non Reolink devices were unimpacted this time because the Reolink NVR does not run a DHCP server, it is proprietary.
For mixed network connection allowing for direct network access to individual cameras aka allow bypassing the NVR:
Static assign the cameras to prevent your issue. And only connect the NVR's WAN port to your network..
For isolated camera only network where individual cameras are unreachable from data network aka only connect via NVR:
Plug 1 (or more) of the 4 NVR LAN ports towards your camera only VLAN and let the NVR manage the cameras as Reolink suggest in the FAQ for the device.
PS it appears Reolink have misleading WAN/LAN names in some docs I found. Although I do not have the 36 channel device myself the WAN will be the single port. The LAN will be the 4 ports.
Regarding the passwords I have always found recent Reolink NVR assume username of admin and a password of blank.
Many years ago I believe Reolink NVR's expected passwords like admin/12345 and admin/123456.
It will auto log in to cameras with admin/<blank>.
The NVR does not change the camera passwords from that, they remain as admin/<blank>.
If cameras have had their password changed, local on NVR will simply show invalid password for the channel.
What password do you believe the NVR has change the cameras to? The NVR's password?
I have never seen that behaviour from my Reolink NVR's.

Posts made by bits_67665092824
-
RE: Major security flaw in ALL new model Reolink cameras.
-
RE: relink android software
For RTSP:
https://support.reolink.com/hc/en-us/articles/360007010473-How-to-Live-View-Reolink-Cameras-via-VLC-Media-Player
For IP change I think you need to use Windows or Mac client.
It appears many settings are not exposed in the Android app.
PS Reolink has web UI available for some models, rlc-4xx, rlc-8xx and rln-xxx. -
RE: reolink client 8.1.28 – UID connection
P2P UID method via AWS is very different to UID discovery method.
UID discovery in a LAN context only uses the UID as a unique code in the broadcast messages.
P2P UID in an internet context uses the unique code in a request to the Reolink server to setup a punch throw connection to the camera.
What method of UID do you believe applies for you? -
RE: reolink client 8.1.28 – UID connection
Describe the network environments more.
UID requires internet access for both cameras and client or UID can use broadcasts on the LAN between camera and client to learn the cameras IP.
It is also possible your NAT router could cause issues or a firewall could block the connection.
If you have 2 separate LAN networks with private IP routing between but if the device or client lack internet, connecting via UID would be impossible. Both internet and broadcast UID methods would be blocked.
Maybe you believe the 7.x client is using UID but it is not.
Or there is differences in its ability to use tcp or udp. -
RE: Playback speed option is missing?
I do think variable playback speed in windows client did also require updated device firmware for support. Although the firmware mention I think should be new enough.
-
RE: FTP w/ RLN16-410
I wrote a free open source Windows app that can convert the .264 files you likely have if you are interested.
For me the first step would be to update firmware as the problem may have been fixed. -
RE: Playback on Adroid APP isnt working
I also agree that Reolink playback is broken on my s20.
Live works ok.
Saving screenshots of live also fails. -
RE: reolink client 8.1.28 - RAM usage
Oh wow I also see that memory usage shoot up to nearly 4gb when minimized.
-
RE: NVR Firmware Wishlist
When I update cameras I tend to do this:
-Connect laptop to the NVR POE ports, disconnecting one of the 8 cameras to do so.
-Statically assign laptop to 172.16.25.101
-Open Reolink client and add cameras I want to update
-Update camera firmware from client direct connected to camera -
RE: Sharing Camera - ability to limit permissions to change settings
I don't have a Reolink Go but on all the other Reolink devices I have seen you can create administrator or user accounts.
Admins can change all settings but users can only view or change their own password. -
RE: E1 Pro link problem
The linked file definitely appears to identify itself as 116_20110204
e1.png -
RE: RLC 423 (5MP) Firmware
I can't find firmware for RLC-423 in download center. That's why I'm asking. I guess im not the only one with this model. Must all customers ask per email to get the update?
It appears the link may have gone up just after you posted?
https://support.reolink.com/hc/en-us/articles/900004031146-12-23-2020-Firmware-for-RLC-423-IPC-51516M- -
RE: RLN8-410: Four-Camera View Only?
Local on the NVR HDMI or via Reolink clients (Windows, Mac, Android, iOS) can all show 8 live feeds at the same time.
Playback of recorded files on the NVR is limited to 4 cameras at a time. -
RE: Connect non reolink POE devices to NVR
Probably has its own DHCP server and private subnet.
Not that it is very important but Reolink NVR does not use DHCP to allocate the IP addresses for cameras connected to the NVR and instead uses its own protocol.
In that protocol only the IP address is given to the camera. No subnet, gateway or dns is exchanged with the camera.
172.16.25.0/24 is used.
The NVR does not function as a router between its LAN and WAN interfaces. -
RE: Cameras are trying to connect to unknown IP addresses
What do these resolve to in your region?:
apis.reolink.com
p2p.reolink.com
Do you have the UID feature enabled? -
RE: API and 3rd party access for Argus 2
The network protocol, encryption, media format and basically all aspects of Reolink products has been fully reverse engineered already.
This includes NVR and IP cameras such as RLC/B/E/Argus.
Anything the official Reolink client, NVR or IP Cams send between each other is already documented.
Eg here is a tool that can log in and get a video stream from Argus cameras:
https://[censored]/jdillenkofer/camera_proxy
Some docs on Baichuan protocol:
https://[censored]/thirtythreeforty/neolink/blob/master/dissector/protocol.md
https://[censored]/thirtythreeforty/neolink/blob/master/dissector/messages.md -
RE: MQTT and or Webhook Support for Home Automation
Neolink has a pull request that adds MQTT support for Reolink cameras.
https://[censored]/thirtythreeforty/neolink/pull/78 -
RE: Flash is Dead? Where is HTML5 Support?
You can continue to use flash if you must in a browser that you use purely to connect to the cameras.
Eg
You could install Pale Moon for use with the camera.
https://www.palemoon.org/
I am not saying replace your current browser with Pale Moon but use it solely for connecting to the cameras. -
RE: Reolink Client Beta For Windows
How do you playback more than 1 channel at a time?
-
RE: please add rtsp support to e1 and lumus cameras
Neolink can create a rtsp stream for E1 cameras.
https://[censored]/thirtythreeforty/neolink