@reolink-fiona Can you supply a link to 8.8.2 please? There was no need for this before, there is no need for this on the Android and iOS now, and there is no need to flood the router logs with 86,000 events every day

IMHO there is an even easier method. Since the client is crashing trying to process a video stream, simply disable WiFi and/or Ethernet, then start the client. It won't crash since there are no streams available to process. You can then leisurely navigate to Settings to disable Hardware Decoding First.

Since installing 8.8.4 any time it is running (anywhere on my LAN) my router reports/logs a never-ending stream of possible DNS re-bind attacks. Here is a small snippet from the log:

Feb 2 18:16:33 dnsmasq[4075]: possible DNS-rebind attack detected: p2p14.reolink.com
Feb 2 18:16:34 dnsmasq[4075]: possible DNS-rebind attack detected: p2pm-abr.reolink.com
Feb 2 18:16:35 dnsmasq[4075]: possible DNS-rebind attack detected: p2p11.reolink.com
Feb 2 18:16:35 dnsmasq[4075]: possible DNS-rebind attack detected: p2p15.reolink.com
Feb 2 18:16:36 dnsmasq[4075]: possible DNS-rebind attack detected: p2p12.reolink.com
Feb 2 18:16:37 dnsmasq[4075]: possible DNS-rebind attack detected: p2p13.reolink.com
Feb 2 18:16:37 dnsmasq[4075]: possible DNS-rebind attack detected: p2p16.reolink.com
Feb 2 18:16:38 dnsmasq[4075]: possible DNS-rebind attack detected: p2p14.reolink.com
Feb 2 18:16:39 dnsmasq[4075]: possible DNS-rebind attack detected: p2pm-abr.reolink.com
Feb 2 18:16:40 dnsmasq[4075]: possible DNS-rebind attack detected: p2p11.reolink.com
Feb 2 18:16:40 dnsmasq[4075]: possible DNS-rebind attack detected: p2p15.reolink.com
Feb 2 18:16:41 dnsmasq[4075]: possible DNS-rebind attack detected: p2p12.reolink.com
Feb 2 18:16:42 dnsmasq[4075]: possible DNS-rebind attack detected: p2p13.reolink.com

I hope you can understand that I do not find disabling the router's re-bind protection and/or whitelisting a slew of reolink web sites that I will never intrinsically trust viable options. Can you provide a link to 8.8.2 so I can get rid of this version ASAP please? My bad for not saving a copy....

If you have performed a reset and it doesn't read the QR, then perhaps try using a different device. Virtually all of my Reolink cameras are unable to "see" the QR code on my Microsoft Surface Duo 2 phone. They have no problems with my other phones

1 If minimized for a while the client will go black, even if hardware decode first is disabled
2 If left open for while it'll sometimes freeze, other times it will go black
3 In either case the client will not restart unless you open task manage and terminate the Reolink processes (I usually need to kill 4)
4 It doesn't remember video quality settings after switching single video to tile and vise versa

I've gone back to 8.8.2. If you click on update it doesn't know 8.8.4 exists, which is an excellent thing since I wouldn't recommend it to anybody, at least not on WIndows

@user_645880601444421_645880601444421 A second related method is to start the client and click on Playback as fast as you can. If you are successful, you'll circumvent initial stream processing and have ample time to disable Hardware Decoding First. Might have to make several attempts before you get good at it

IMHO there is an even easier method. Since the client is crashing trying to process a video stream, simply disable WiFi and/or Ethernet, then start the client. It won't crash since there are no streams available to process. You can then leisurely navigate to Settings to disable Hardware Decoding First.

@reolink-fiona Can you supply a link to 8.8.2 please? There was no need for this before, there is no need for this on the Android and iOS now, and there is no need to flood the router logs with 86,000 events every day

Since installing 8.8.4 any time it is running (anywhere on my LAN) my router reports/logs a never-ending stream of possible DNS re-bind attacks. Here is a small snippet from the log:

Feb 2 18:16:33 dnsmasq[4075]: possible DNS-rebind attack detected: p2p14.reolink.com
Feb 2 18:16:34 dnsmasq[4075]: possible DNS-rebind attack detected: p2pm-abr.reolink.com
Feb 2 18:16:35 dnsmasq[4075]: possible DNS-rebind attack detected: p2p11.reolink.com
Feb 2 18:16:35 dnsmasq[4075]: possible DNS-rebind attack detected: p2p15.reolink.com
Feb 2 18:16:36 dnsmasq[4075]: possible DNS-rebind attack detected: p2p12.reolink.com
Feb 2 18:16:37 dnsmasq[4075]: possible DNS-rebind attack detected: p2p13.reolink.com
Feb 2 18:16:37 dnsmasq[4075]: possible DNS-rebind attack detected: p2p16.reolink.com
Feb 2 18:16:38 dnsmasq[4075]: possible DNS-rebind attack detected: p2p14.reolink.com
Feb 2 18:16:39 dnsmasq[4075]: possible DNS-rebind attack detected: p2pm-abr.reolink.com
Feb 2 18:16:40 dnsmasq[4075]: possible DNS-rebind attack detected: p2p11.reolink.com
Feb 2 18:16:40 dnsmasq[4075]: possible DNS-rebind attack detected: p2p15.reolink.com
Feb 2 18:16:41 dnsmasq[4075]: possible DNS-rebind attack detected: p2p12.reolink.com
Feb 2 18:16:42 dnsmasq[4075]: possible DNS-rebind attack detected: p2p13.reolink.com

I hope you can understand that I do not find disabling the router's re-bind protection and/or whitelisting a slew of reolink web sites that I will never intrinsically trust viable options. Can you provide a link to 8.8.2 so I can get rid of this version ASAP please? My bad for not saving a copy....

@joseph-chircop_497308027822318 I'm not sure I understand. I installed over 8.8.2 and every camera remained populated, i.e. there was no need to add cameras from scratch. Also, all of my preset thumbnails are present and working fine. What am I missing?

@joseph-chircop_497308027822318 Does Reolink offer any IR illuminator recommendations? Brands? Lumens? Optimal wavelength? I have 3x RLC-532WAs that I would consider augmenting with IR illumination - so ideally the illuminator would be very wide angle if possible, say 180 degrees

A related issue - the Windows desktop app does not respond well if at all to arrow finger touches on a tablet (in my case Surface Pros). It would be nice if the app better supported tablet use including point & click

Interestingly enough if the camera supports patrol/scout mode the order of those patrol presets can be rearranged. It should be easy to extend this functionality to the presets