@user_746623229407444_746623229407444

lol, it's the typical Cart before the Horse with Reolink.

Same issue as before. Client locks at random times. 8.10 beta wasn't perfect; but I could display 4 feeds without it locking up. I can't display my 12 cameras at once without issues on any of the clients.

Might be time to go back to HikVision.

DX9 released 20 years ago, and 7 years before Reolink was a business.... sometimes I wonder about Reolink and the oddball support they push.

@guero-jose_338291415367917

son, haha
Can I be frank? you are subnetting different networks within the same vlans. That kind of already says everything I need to know. 2nd, your a network admin for an office using reolink cameras... again everything I need to know.

It's extremely hard to follow when you say things like in your first post. " I changed the NVR netmask to 255.0.0.0 to allow the second subnet to connect" think about that a min. You changed it on the device you want "other" devices to connect to. That's not how routing works... you keep saying vlan; a vlan is no different than a physical connection. In reality a physical connect is vlan1 by default. I'm glad other hosts can connect to other hosts on different subnets, did you check ARP cache? what router? L3 switch? gateways? so much info is missing it's crazy.

My shit works, sorry yours doesn't. I'm done, I'm out. enjoy your life.

@joseph-chircop_497308027822318

Support sent me the new APK link, unfortunately it didn't solve my issue. I'm going to install the app on a different phone to make sure my actual doorbell isnt the issue.

https://drive.google.com/file/d/1uf0G_w53SJB3H7187AbidjrO1OMMutcM/view?usp=share_link

This is the "updated" version that will show up on the google play store soon.
https://drive.google.com/file/d/1uf0G_w53SJB3H7187AbidjrO1OMMutcM/view?usp=share_link

8.8.0 is still randomly freezing the live camera views. This is the 3rd update in a row that hasn't fixed the issue.

8.5.2 is the latest version that still works as intended.

This is getting old...

@joseph-chircop_497308027822318

Support sent me the new APK link, unfortunately it didn't solve my issue. I'm going to install the app on a different phone to make sure my actual doorbell isnt the issue.

https://drive.google.com/file/d/1uf0G_w53SJB3H7187AbidjrO1OMMutcM/view?usp=share_link

@joseph_1979 Win 11

@joseph_1979 yea, no idea what it was. The last few versions this would start up with black windows and a play button in the middle; only on those specific models, everything else was fine.

The initial positive I see, is my 4 TrackMix's don't startup with a black screen on the live view now...

@user_803260535316688_803260535316688

assuming package detection will be for the new doorbell? The original can't see that close to the door.

@rblaursen_690488231854236

I'm on unifi AP's and switches and never had an issue with the wifi doorbell. Have you tried connecting directly to the doorbell via IP?

@joseph_1979 yea, looks like 3.0.0.2555_23080700 is still old? not sure.

Either way, none of the "new" features work on it...

Did Reolink just push a new firmware update by chance?
sitting here looking at the client and watched the doorbell go offline. It's been 20mins and nothing....
Can't ping it, but I also don't to reset the power if it's being updated....

Bah..
I was too hasty in my post. It's back up with new firmware.
Firmware Version v3.0.0.2555_23080700

@guero-jose_338291415367917

son, haha
Can I be frank? you are subnetting different networks within the same vlans. That kind of already says everything I need to know. 2nd, your a network admin for an office using reolink cameras... again everything I need to know.

It's extremely hard to follow when you say things like in your first post. " I changed the NVR netmask to 255.0.0.0 to allow the second subnet to connect" think about that a min. You changed it on the device you want "other" devices to connect to. That's not how routing works... you keep saying vlan; a vlan is no different than a physical connection. In reality a physical connect is vlan1 by default. I'm glad other hosts can connect to other hosts on different subnets, did you check ARP cache? what router? L3 switch? gateways? so much info is missing it's crazy.

My shit works, sorry yours doesn't. I'm done, I'm out. enjoy your life.

@guero-jose_338291415367917

Brother I wish you luck. If your networks are not L2 adjacent, they need a gateway and routing table. You can literally have two computers directly connected to each other via ethernet on different subnet networks and they will not communicate to each other without a L3 switch or router correctly configured.

I don't know how else to explain it.

@guero-jose_338291415367917

I'll have to play with my NVR and see if I can replicate it. Shouldnt matter if it's a vlan or not, something has to update the routing table to point to the correct network.

For example:
Network A uses 10.1.1.1 /24 which has a IP range of 10.1.1.1 - 10.1.1.254
Network B uses 10.2.2.1 /24 which has a IP range of 10.2.2.1 - 10.2.2.254

• Those are separate networks, they need a routing table to point to the correct location.

Now you changed Network B to 10.2.2.1 /8 which has a IP range of 10.0.0.1 - 10.255.255.254

• Network A still doesn't know network B exists and it can't connect to 10.2.2.x range without routing info.

On windows you can run the CMD ( route print ) to see your current info.