Neolink has a pull request that adds MQTT support for Reolink cameras.
https://github.com/thirtythreeforty/neolink/pull/78

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://github.com/jdillenkofer/camera_proxy

Some docs on Baichuan protocol:
https://github.com/thirtythreeforty/neolink/blob/master/dissector/protocol.md
https://github.com/thirtythreeforty/neolink/blob/master/dissector/messages.md

@user_612681119584296_612681119584296

Reolink have a proprietary protocol for NVR auto a*signing IP's that the cameras prefer over DHCP.
Having multiple IP a*signing servers on the same network will always cause issues.
All devices configured for DHCP are prone to IP rea*signment unless a layer 3 switch with effective configured security policy is in use.
Your a*sumptions 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 bypa*sing the NVR:
Static a*sign 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 pa*swords I have always found recent Reolink NVR a*sume username of admin and a pa*sword of blank.
Many years ago I believe Reolink NVR's expected pa*swords like admin/12345 and admin/123456.
It will auto log in to cameras with admin/<blank>.
The NVR does not change the camera pa*swords from that, they remain as admin/<blank>.
If cameras have had their pa*sword changed, local on NVR will simply show invalid pa*sword for the channel.

What pa*sword do you believe the NVR has change the cameras to? The NVR's pa*sword?
I have never seen that behaviour from my Reolink NVR's.

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.

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?

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.

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.

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.

I also agree that Reolink playback is broken on my s20.
Live works ok.

Saving screenshots of live also fails.

Oh wow I also see that memory usage shoot up to nearly 4gb when minimized.

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 a*sign 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

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 pa*sword.