reolink cameras?

I am now using Reolink RLC-423. It's my first time to use a security camera. It's a PTZ camera. For now, it works well. I installed it to monitor my yard. If you have problems on using this camera, I can share my experience with you.
 
Found two connections from my ReoLink RLC-410 camera to Amazon Web Services (54.xxx.xxx.xxx) addresses this afternoon, on Port 32100. Shut that off at my router and rebooted the camera to kill those connections. Judging from a lot of other webcams, this appears to be a uPnP 'phone home'. Sorry, that's entirely unnecessary.

A bit more information. Apparently, these three AWS IP addresses have been sending a lot of UDP traffic back to my IP address, which my router is dropping. Since blocking port 32100, the AWS UDP traffic has stopped.
 
Last edited by a moderator:
I noticed that too, but setting IP to static and wiping out the gateway and DNS addresses did the trick in addition to blocking at the router. Not a big deal really as I never expose or allow any of my cameras on the internet as a general practice. Interesting though that it's only calling Amazon.
 
Last night I asked Reolink support why the camera was initiating these UDP connections, and they said it should use only TCP, not UDP. I re-opened the ports this morning long enough to get a screenshot.

Reolink UDP Connections.png

Looking at the router logs some more, those AWS IP addresses are sending UDP packets back on port 32099. Yup, blocked that one, as well.
 
Last edited by a moderator:
  • Like
Reactions: fenderman
No, it seems to be binary.

Code: 
root@2106D:~# tcpdump -XX -vv -i br0 host 192.168.1.71 and port 32100
tcpdump: listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes
10:13:56.238497 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 76)
    192.168.1.71.21523 > ec2-54-86-23-37.compute-1.amazonaws.com.32100: [udp sum ok] UDP, length 48
        0x0000:  14dd a988 b570 d8eb 97a0 8908 0800 4500  .....p........E.
        0x0010:  004c 0000 4000 4011 2b37 c0a8 0147 3656  .L..@.@.+7...G6V
        0x0020:  1725 5413 7d64 0038 b997 f112 002c 2679  .%T.}d.8.....,&y
        0x0030:  34c4 78ae b288 42ef c24b 5a0a 14ac 113a  4.x...B..KZ....:
        0x0040:  8618 244b 5915 4802 351c 7fc7 4e9a dc0f  ..$KY.H.5...N...
        0x0050:  8cae 8264 b2a0 63a7 17c1                 ...d..c...
10:13:56.239276 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 76)
    192.168.1.71.21523 > ec2-54-72-248-104.eu-west-1.compute.amazonaws.com.32100: [udp sum ok] UDP, length 48
        0x0000:  14dd a988 b570 d8eb 97a0 8908 0800 4500  .....p........E.
        0x0010:  004c 0000 4000 4011 4a01 c0a8 0147 3648  .L..@.@.J....G6H
        0x0020:  f868 5413 7d64 0038 d861 f112 002c 2679  .hT.}d.8.a...,&y
        0x0030:  34c4 78ae b288 42ef c24b 5a0a 14ac 113a  4.x...B..KZ....:
        0x0040:  8618 244b 5915 4802 351c 7fc7 4e9a dc0f  ..$KY.H.5...N...
        0x0050:  8cae 8264 b2a0 63a7 17c1                 ...d..c...
10:13:56.239481 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 76)
    192.168.1.71.21523 > ec2-54-179-151-251.ap-southeast-1.compute.amazonaws.com.32100: [udp sum ok] UDP, length 48
        0x0000:  14dd a988 b570 d8eb 97a0 8908 0800 4500  .....p........E.
        0x0010:  004c 0000 4000 4011 aa03 c0a8 0147 36b3  .L..@.@......G6.
        0x0020:  97fb 5413 7d64 0038 3864 f112 002c 2679  ..T.}d.88d...,&y
        0x0030:  34c4 78ae b288 42ef c24b 5a0a 14ac 113a  4.x...B..KZ....:
        0x0040:  8618 244b 5915 4802 351c 7fc7 4e9a dc0f  ..$KY.H.5...N...
        0x0050:  8cae 8264 b2a0 63a7 17c1                 ...d..c...
10:13:56.278193 IP (tos 0x0, ttl 45, id 64776, offset 0, flags [DF], proto UDP (17), length 40)
    ec2-54-86-23-37.compute-1.amazonaws.com.32100 > 192.168.1.71.21523: [udp sum ok] UDP, length 12
        0x0000:  d8eb 97a0 8908 14dd a988 b570 0800 4500  ...........p..E.
        0x0010:  0028 fd08 4000 2d11 4152 3656 1725 c0a8  .(..@.-.AR6V.%..
        0x0020:  0147 7d64 5413 0014 ae1b f113 0008 7e36  .G}dT.........~6
        0x0030:  f246 6369 abc5                           .Fci..
10:13:56.360821 IP (tos 0x0, ttl 42, id 36476, offset 0, flags [DF], proto UDP (17), length 40)
    ec2-54-72-248-104.eu-west-1.compute.amazonaws.com.32100 > 192.168.1.71.21523: [udp sum ok] UDP, length 12
        0x0000:  d8eb 97a0 8908 14dd a988 b570 0800 4500  ...........p..E.
        0x0010:  0028 8e7c 4000 2a11 d1a8 3648 f868 c0a8  .(.|@.*...6H.h..
        0x0020:  0147 7d64 5413 0014 cce5 f113 0008 7e36  .G}dT.........~6
        0x0030:  f246 6369 abc5                           .Fci..
10:13:56.499868 IP (tos 0x0, ttl 46, id 32005, offset 0, flags [DF], proto UDP (17), length 40)
    ec2-54-179-151-251.ap-southeast-1.compute.amazonaws.com.32100 > 192.168.1.71.21523: [udp sum ok] UDP, length 12
        0x0000:  d8eb 97a0 8908 14dd a988 b570 0800 4500  ...........p..E.
        0x0010:  0028 7d05 4000 2e11 3f22 36b3 97fb c0a8  .(}.@...?"6.....
        0x0020:  0147 7d64 5413 0014 2ce8 f113 0008 7e36  .G}dT...,.....~6
        0x0030:  f246 6369 abc5                           .Fci..

And here are the responses back from those AWS nodes:

Code: 
root@2106D:~# tcpdump -XX -vv -i br0 port 23906
tcpdump: listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes
10:24:49.045892 IP (tos 0x0, ttl 45, id 64814, offset 0, flags [DF], proto UDP (17), length 40)
    ec2-54-86-23-37.compute-1.amazonaws.com.32100 > 192.168.1.71.23906: [udp sum ok] UDP, length 12
        0x0000:  d8eb 97a0 8908 14dd a988 b570 0800 4500  ...........p..E.
        0x0010:  0028 fd2e 4000 2d11 412c 3656 1725 c0a8  .(..@.-.A,6V.%..
        0x0020:  0147 7d64 5d62 0014 a4cc f113 0008 7e36  .G}d]b........~6
        0x0030:  f246 6369 abc5                           .Fci..
10:24:49.118974 IP (tos 0x0, ttl 42, id 36514, offset 0, flags [DF], proto UDP (17), length 40)
    ec2-54-72-248-104.eu-west-1.compute.amazonaws.com.32100 > 192.168.1.71.23906: [udp sum ok] UDP, length 12
        0x0000:  d8eb 97a0 8908 14dd a988 b570 0800 4500  ...........p..E.
        0x0010:  0028 8ea2 4000 2a11 d182 3648 f868 c0a8  .(..@.*...6H.h..
        0x0020:  0147 7d64 5d62 0014 c396 f113 0008 7e36  .G}d]b........~6
        0x0030:  f246 6369 abc5                           .Fci..
10:24:49.273486 IP (tos 0x0, ttl 46, id 32043, offset 0, flags [DF], proto UDP (17), length 40)
    ec2-54-179-151-251.ap-southeast-1.compute.amazonaws.com.32100 > 192.168.1.71.23906: [udp sum ok] UDP, length 12
        0x0000:  d8eb 97a0 8908 14dd a988 b570 0800 4500  ...........p..E.
        0x0010:  0028 7d2b 4000 2e11 3efc 36b3 97fb c0a8  .(}+@...>.6.....
        0x0020:  0147 7d64 5d62 0014 2399 f113 0008 7e36  .G}d]b..#.....~6
        0x0030:  f246 6369 abc5                           .Fci..
 
Last edited by a moderator:
I'm guessing it's network configuration info, being sent back to their AWS services, for use with their iPhone/Android apps that allow "easy" configuration.
No, sorry. I don't need that.

What I'm concerned about (and Nayr would be correct) are vulnerabilities as noted in this article about a different camera.

I believe the way to disable this UDP communication is to disable BOTH the uPnP and the UID items, using the Reolink Client program, and selecting the Advanced Network icon. When I set the camera up a few weeks ago, I was very deliberate in disabling the uPnP option, but I figured I'd leave the UID value set. I think that was probably a mistake, in retrospect.

Reolink Client Advanced Network.png

Yup, rebooted the camera after clearing that UID item and saving the settings. No more UDP transmissions to AWS.
 
Last edited by a moderator:
  • Like
Reactions: foreyk
Overnight, Reolink Support e-mailed, advising I disable the UID value. I told them they need to document this functionality, or I wouldn't be able to recommend their cameras. The volume and frequency of these back-and-forth UDP conversations with undocumented AWS IP addresses is simply ridiculous.
 
  • Like
Reactions: foreyk
VorlonFrog said:
Overnight, Reolink Support e-mailed, advising I disable the UID value. I told them they need to document this functionality, or I wouldn't be able to recommend their cameras. The volume and frequency of these back-and-forth UDP conversations with undocumented AWS IP addresses is simply ridiculous.
Click to expand...

Thanks I'll disable the UID... Makes sense, but annoying they don't disclose it upfront. Like the cameras, but they seem to be early in their development.
 
Digging in the last firmware file provided for my RLC-410ws camera, I see it uses the 1/3-inch ov4689 4 megapixel image sensor.

Although there's no telnet/ssh/dropbear daemon running, the root password appears to be 123456..knight
 
Last edited by a moderator:
  • Like
Reactions: Trebacz
New guy here but have been lurking around for a while. I just installed the Reolink RLC-423 and I figured I would post this up for the OP or anyone else wondering about the Reolinks. I haven't tried the others but I am pleased with this camera.

Mounted.jpg

Old view from the Foscam I had Mounted
Old Foscam.PNG

Image from the 423
Daytime.PNG

I have a wider angle with the Reolink than with the Foscam with a seemingly clearer picture.

Nightime view
Night Time.PNG

The IR isn't as bright as the Foscam but still adequate for me. Hope this helps someone out.
 
fenderman said:
If they don't work properly then it's just cheap junk...
Click to expand...

I've been testing two RLC-410 and I find they work fine; better than a lot of what you find on Amazon. Not perfect of course, but neither are Hiks and Dahuas.


Sent from my iPhone using Tapatalk
 
I think you might be judging the cameras based on issues with old firmware. I am using 16 Reolink cameras (mix of RLC-411, 411S, 422 and 1x 423) with Blue Iris as the NVR and some on a Bosch DIVAR system. I agree that in the past they had software issues, but revised firmware seems to have fixed them all for me and now they are performing very well. All are recording at 2560 x 1440 and 30fps and have been for weeks (at some point I will drop frame rates to 15fps, when I shift the BI install to a i7 2600K). The build quality is excellent with my only possible compliant being the nighttime performance, but the additional of an IR illuminator fixes the issue (unfortunately you can not turn off the onboard IR) and now the night performance is really not far off my Bosch IP cameras. Agreed they are cheap certainly compared to the Bosch, but 5 cameras for the cost of one, it was an easy choice for me.
 
Ok, I got my first Reolink 411s camera. I have the registered copy of Blueiris and the latest update to it. I updated the firmware on the 411s to 2.0 something (latest on their web). I have 3 FOS cams and a Starcam. Two of the FOS cams that have the optical zoom work fine. My problem is I can only use the optical zoom with the Reolink software. The zoom buttons in Blueiris do nothing. I can digital zoom but not take advantage of the 4X optical on Reolink. That is one of the reasons I went with that unit. Does anyone have a magic trick I can use to get Blueiris to work with the zoom function? thanks in advance
 
Not sure there's any way to get the zoom working in BI. Contact Reolink; their customer service is pretty responsive.


Sent from my iPhone using Tapatalk
 
  • Like
Reactions: mrgary
I have several Reolink RLC-410 bullet cams, and the day image quality is very good, especially for the price. The PC software and firmware for the cams is a little buggy, but they appear to have very responsive technical support. Of the few issues I've found with the Windows client, support confirmed the issues, and a few weeks later they were fixed in an update. I usually have a reply from their support people within 12 hours or so. The latest firmware for the 410 appears to have a problem with WDR though. The image appears to have WDR enabled, even though it is disabled in the configuration.
 
You must log in or register to reply here.
Top Bottom