Posts made by user_746479291687074_746479291687074

Just got a doorbell/wifi camera. At present it is my only reolink (having sold the house which had others). I am aware of this discussion:

https://community.reolink.com/topic/6726/unable-to-access-reolink-ip-cams-from-different-vlan

Here's the thing -- some IP goes through to another subnet, I can ping it just fine, and Home Assistant (and whatever protocols it uses) seems OK accessing it. The web gui is flakey, it will paint a login screen but not log in.

This does not SEEM to be a security feature preventing access from other subnets (if so ping would not work, for example). This just seems broken.

Is there a clear statement on what does, and does not work across subnets? On another forum it was said that broadcast traffic must flow and arrive with the same subnet, which makes no sense for a gui (and also might imply nat would not be a solution, as has been suggested).

I just got this -- I can put it back in the box and return it, and plan to if I can't get a clear understanding of this. I don't need the web gui to work across subnets, but I do need whatever integration protocols home assistant uses to work -- and continue to work. At present with this half-working-half-broken approach, it seems likely to expect some firmware update to break it entirely.

I've seen products with subnet isolation as a (bogus) security feature, but all of them (a) actually block all traffic, as any security related approach would, and (b) let the user turn it off if needed. So... what's really up with this?

Linwood

I have, after asking about this on another forum, been told that some users have been provided a later firmware version by Reolink, some kind of beta which was supposed to address this.

I'm surprised no one from Reolink has addressed my post, do they moderate here? Or do I need to contact support directly?

Is no one else having issues like this?

I have a new RLC-823A 16x which i added to a Blue Iris system; it has two other 8mp Hikvision cameras and four Lorex 8mp cameras. All are running at 4fps, and the server and network is barely noticing the workload.

The 6 other cameras all are within a second of each other in their displays, the Reloink starts in sync and over a few hours falls to about 10s behind and stays there.

Disconnect and reconnect and it is back in sync.

I have tried a variety of settings both generic/onvif and BI's Relink specific setting, at the moment running H.265 RTSP. I have not found one that seems to behave differently.

At (only) 4fps there is no good reason it can't keep up.

I have searched and found lots of people with this problem, some say it was fixed with newer firmware, though I am fairly current (v3.1.0.2347_23061923_v1.0.0.93). Is there a newer version?

One suggested using RTMP but at least the flavor of it I tried did not work.

Being 10s behind is quite a lot. Is there a solution?

Linwood

@tchubaba I also use OPNSense and also use a separate vlan for video. I think this NAT stuff is a bad idea. If you want to do it, however, it's done under Firewall, Nat, Outbound. set up manual rules for interface Video (or whatever you called that VLAN) to mirror vlan LAN (except of course don't include Video in the list of courses). This would mean a connection from LAN to VIDEO would use the Video interface address as the source as seen by the camera.

The problem with this is that it does not pass broadcast, and I suspect the issue is the clients are using nDNS or similar garbage configuration tools that rely on broadcasts.

I cannot speak for all cameras, but I just tested my only reolink, a RLC-823A 16x, and it works fine. I initially configured it in the android client (as it didn't seem to want to pull a DHCP address) while the camera was plugged into a LAN (not VIDEO vlan) port. Then I used the web browser to change the IP to a VIDEO subnet address, and switched that switch port to the Vldeo VLAN. Everything then worked, except the client lost sight of it -- delete camera, add back in by explicit IP address (NOT letting it search) and then client worked. To test the windows client I downloaded it, did the same, that worked also. And it works with Blue Iris just fine, and the web browser. I have OPNSense configured to allow connection from LAN to VIDEO, but not from VIDEO to LAN (except for NTP), so the cameras cannot get access outbound, but will respond to connections from inside.

Again, this is one (newer) camera, others may work differently, but I would suggest testing a similar approach and avoiding NAT, as I doubt NAT will fix the issue. It might, and OPNsense can do it, but NAT doesn't carry broadcast (at least not in any normal setup). And normally vendors doing this is not because of security but because they rely on broadcast messages, and both separate VLAN's (by default) and NAT (almost always) will block broadcast.

It is possible to carry broadcasts between VLAN's (not sure about when NAT is involved), but you can look up "broadcasts across vlans" if you want to head down that rathole. However, I would fix see if static IP addresses in client and camera won't solve your problem.

It's pretty clear Reolink is aimed more at "I do not understand computers and do not plan to learn" crowd, and anyone knowing the term "OPNsense" is already out of that class.

Linwood