Posts made by SunCat_359604577222809

I thought it would be nice to put an update in here for others that might notice the same behavior. It appears that this is intentional (??). The following is the response I received:

---
"The log you see is the Discover package(the simulated DHCP detection package) of the camera, the camera sends them to check whether the wifi network is good. The camera sends the request package about every 5 minutes. And I ask[ed our engineer] if this can be canceled? He told me no. Because when the camera sends a DHCP Discover packet, if the router receives it, it will reply to the camera, and the camera will know if it is still connected to the router."
---

The 802.11 state machine has its own beacon/probe mechanism for maintaining a valid wireless association link (including the ability to switch channels when roaming in multi-channel environment). Testing a link with DHCP probes every 5 minutes seems superfluous and excessive. It begs the follow-up question: What problem are they trying to solve by introducing this new behavior?

I guess it's a good thing that I have my old DHCP config in place so my server is at least handing back the IP I want the camera to use. I would hate to have to trust the FW to do the right thing if my DHCP server passed back a different IP from the static config (which it would normally do for other new devices being added to the network).

I recently updated my RLC-410W with the v3.0.0.136_20121102 firmware to pick up HTML5 support. After the update I have been noticing excessive DHCP queries coming from the camera even though I have it configured with a static IP address. It looks like someone botched the networking support in the latest firmware. There is no reason that the camera should be asking for an IP address every 5 minutes when it already has one.

For those that still have IPC_3816M based cameras, another option for being able to directly view the camera's live output is to use the Real Time Streaming Protocol (RTSP) support. I have a RLC-422W camera that I use this way. My main system runs Linux, and I only need to resort to using the Windows client to modify the motion detection trigger zone or to pull past recordings.

For live viewing, I tend to use VLC with the following URL:

rtsp://doorcam.home.localnet:554

For archival and notice purposes, I find that the email and ftp push mechanisms work just fine for forwarding triggered snapshot and video segments.

While I'm disappointed that Reolink support has decided to abandon these older (but still functional) cameras, all is not lost, and I can continue using them even post-flash.