Posts made by KS

@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.

@guero-jose_338291415367917

Because changing the devices subnet does not change the routing table to the different network. That routing table is either made manually or when a device gets the information from DHCP.

@user_746623229407444_746623229407444 what firmware did you use?

@user_746623229407444_746623229407444

Something changed in the last firmware that messed that ability up, and a couple other things like camera naming...
Now you have to right click the camera ( in the desktop client) and select the view you want to see.

The other way to get both views up at the same time is to add that specific camera to the desktop client, then you can drag both views over to your layout.

I have 4 trackmix's all named differently and displayed correctly on the camera view, but the client likes to display the same numbers for some reason. If you change it on the client, then the camera view naming convention gets all screwed up and doubles the name for each view normal/zoomed.

@user_746623229407444_746623229407444

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

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

@joseph_1979



it happens so frequently, that I set a batch file to run every 3 hours....

TASKKILL /IM Reolink.exe /F
TIMEOUT /T 5
START C:\"Program Files"\Reolink\Reolink.exe

also the same issue as posted here a few weeks back. (https://community.reolink.com/topic/5671/8-10-2-memory-leak-or-something?post_id=21871&_=1686518759084)

Is it possible to set the screen location via some user setting to force the Reolink Client application to start in a specific location? For whatever reason, the reolink client does not "remember" the last position when it's closed in Windows 11.

I always put the client on my left monitor in the lower 3rd ( vertical ultra wide). Every time you close the program or restart, the client starts on the main screen right in the middle.


If the client wouldn't crash all the time, it wouldn't be a problem. But since it does..... I've created a batch script that forces the close and reopens it, just hate that it always starts in the middle of the screen and doesn't remember the size or location..

@joseph_1979 yes, but that's a mentality not a standard practice. If you can't fix something so evident 5 versions ago; why would you keep "adding" features on top of other issues... New people coming to Reolink, downloads the client they show available, which is not the one from a year ago.