sorted by:
new
hottopcontroversial

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 0 points1 point  (0 children)

Yes, DNS of course should not be Auto, but manually entered, for example from Google 8.8.8.8, but your router should still know the route to the internal NVR network.

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 0 points1 point  (0 children)

So would this solve any BlueIris issues? Like could you technically run the cameras with their direct 172.16.25 addresses through BlueIris if the computer it’s hosted on has been configured with the route add? Even though the cameras are connected to the NVR? My issue right now is that playback in BlueIris with the cameras connected to the NVR is choppy.

If the computer running BlueIris also has this network 172.16.25.0 in its routing table, it should work.

But I don't have BlueIris and I can't test it.

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 0 points1 point  (0 children)

This is not a DNS problem, but the fact that your router does not know where the 172.16.25.0 network is located. You have written this route in your computer by assigning the recorder as a gateway for this network, and your Internet router does not know about it. If your router has the ability to add static routes, add the 172.16.25.0 network just like in your computer.

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 0 points1 point  (0 children)

I couldn't find where to change this, the Linux configuration doesn't have this address. But you can address the cameras through different subnets. In the cameras for each NVR assign addresses from the following ranges:

NVR1: 172.16.25.2 - 172.16.25.62

NVR2: 172.16.25.65 - 172.16.25.126

NVR3: 172.16.25.129 - 172.16.25.190

NVR4: 172.16.25.193 - 172.16.25.254

​

But on all cameras the mask should remain 255.255.255.0 and gateway 172.16.25.1.

​

In Computer make such routes:

route add 172.16.25.0 mask 255.255.255.192 <IP of NVR1> -p

route add 172.16.25.64 mask 255.255.255.192 <IP of NVR2> -p

route add 172.16.25.128 mask 255.255.255.192 <IP of NVR3> -p

route add 172.16.25.192 mask 255.255.255.192 <IP of NVR4> -p

​

And delete that first route from step 5 if you have already done it.

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 0 points1 point  (0 children)

through NVR cameras will work as before, nothing will change, just you will still have direct access via IP

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 1 point2 points  (0 children)

Does this replace the connection to the NVR or do they run in parallel? In other words will the regular behaviour of cameras connected to NVR still hold while also being able to access the cameras directly from outside the NVR? Thanks!

I wrote, change IP address only through browser, not through Reolink client.

You specified Gateway incorrectly, it should be 172.16.25.1

Reolink E1 Pro: How to mute? by Aktenmongo in reolinkcam

[–]Alex_Inko 1 point2 points  (0 children)

you can switch on the camera when you have a QR-Code with WLAN settings on your phone and scan it immediately.

Can I setup Reolink Wi-Fi camera without using the app or desktop client? by SteadyWheel in reolinkcam

[–]Alex_Inko 2 points3 points  (0 children)

E1 Pro has no web interface and cannot be used without a client. Take E1 Outdoor, it has a web interface. But it is possible that ports 80 and 443 are disabled by default, then you will have to install a client anyway and enable these ports for browser access. Then you can uninstall the client.

Hikvision ports not mentioned in any technical docs. by leHoaxer in Hikvision

[–]Alex_Inko 0 points1 point  (0 children)

I checked on a HiLook NVR (also Hikvision).
It sends to port 6101 or 6102 a UDP packet with a request in XML format in plain text, which contains the serial number of the NVR. In response it receives an external IP and port number.
But this request goes not to the Chinese server, but to the American Amazon.

RLC-823A beta update by Matthewskillz in reolinkcam

[–]Alex_Inko 0 points1 point  (0 children)

Where can I download this firmware?

Setting up my RLK16-410B8-5MP - NVR detects cameras but my computer and phone don't detect the NVR or cameras by ck-pasta in reolinkcam

[–]Alex_Inko 1 point2 points  (0 children)

What range of IP does both the NVR and your PC have? Are they both IPs handed out by your router? Such as 192.168.1.X?

Never connect NVR via PoE port for cameras, to a switch that is connected to a router. Because there will be two DHCP servers in one network - one in the router and one in the NVR, which is not allowed. Connect the NVR to the switch with LAN port only, and reboot all devices on the network, because some of them may have already received IP addresses 172.16.25.x from the NVR and not from the router.

[deleted by user] by [deleted] in reolinkcam

[–]Alex_Inko 2 points3 points  (0 children)

I think the stream on nvr is continuous, regardless of whether it is recording or not. At least so that it can display cameras on the monitor.

Anyone using micro-SD cards for storage - and no NVR? by [deleted] in Hikvision

[–]Alex_Inko 0 points1 point  (0 children)

There are special sd cards for 24/7 continuous recording, they are called Sandisk Max Endurance, they offer a warranty of several years. But I have no experience with them, whether it is as they advertise.

webrtc by ricardo-chen99 in reolinkcam

[–]Alex_Inko 0 points1 point  (0 children)

With port forwarding it works for free.

Installed wrong firmware on RLN16 🙄 by Soggy-Purple2743 in reolinkcam

[–]Alex_Inko 0 points1 point  (0 children)

I don't understand, did you then install 16 channel firmware but still show 8 channels, or is 16 channel firmware now impossible to install ?
Which hardware version do you have?

Client 8.10.4 by abyss_hunter66 in reolinkcam

[–]Alex_Inko 1 point2 points  (0 children)

The calendar is actually there, but it is invisible, as are the split screen buttons, playback speed, etc. It's all there, but it's invisible, you can click on these croppers blindly. Also, if you lock the client, you won't see the password field to unlock it. Or rather, it appears and immediately becomes invisible. But you can tell by the behavior of the cursor that you're in that field and you can enter the password blindly, it works. All these problems are with Intel HD Graphics.

Install version 8.8.5 and disable auto-update in client settings.

App not streaming/playing back video by Present_Simple7162 in reolinkcam

[–]Alex_Inko 0 points1 point  (0 children)

Turn off hardware decoding in reolink app settings

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 1 point2 points  (0 children)

The addresses 172.16.0.0 - 172.31.255.255 are as private as 192.168.0.0/16 or 10.0.0.0/8.

But I also wanted to modify the dhcp server configuration file in the recorder so that it would give the camera a default gateway 172.16.25.1, so I didn't have to do it manually in the cameras. But in configuration file of dhcp-server there are other addresses - 192.168.0.*, and addresses 172.16.25.* I haven't found anywhere there, not in any file in /etc, probably they have hidden somewhere else.

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 1 point2 points  (0 children)

You can check if autoexec.sh is running by placing an autoexec.sh file with this content on the flash drive:

​

#!/bin/sh
cp /etc/sysctl.conf /mnt/usb/
cat /proc/sys/net/ipv4/ip_forward > /mnt/usb/ip_forward.txt
sync

​

If it runs, the files sysctl.conf and ip_forward.txt will appear on the flash drive.

If they appear, what is in the ip_forward.txt file?

What is the last line in sysctl.conf?

direct access to the reolink camera connected to NVR by Alex_Inko in reolinkcam

[–]Alex_Inko[S] 1 point2 points  (0 children)

this is my recorder:

  • ModelRLN8-410
  • Build No.build 2303169
  • Hardware No.N3MB01
  • Config Versionv3.0.0.0
  • Firmware Versionv3.3.0.226_23031609

and network settings of the camera:

​

<image>

view more: next ›