-
I'm using the Reolink wifi doorbell (with latest frimware) which for the most part works great.
One thing keeps annoying me. The doorbell is assigned a fixed IP address (in the doorbell itself; 192.168.1.65) but for some reason it keeps on sending DHCP requests (192.168.1.207 ??????) to the DHCP server. It does this every 5 minutes for no valid reason. Also, the requested IP address is already in use by an other device.
Why does it do this? This is no normal behavior for a network device. It keeps polluting the routers log and probably interferes with the other devices valid DHCP request.
I experimented with a static IP address in the doorbell, with a static IP address in the DHCP server and an automatic assigned one but it keeps on doing this. Even a complete reset of the doorbell doesn't work.Reply QuoteShare0- Share this Post
-
copy the link
Copied!
-
@user_778275310854286_778275310854286 My assumption is that they are doing DHCP requests to verify communication with the router. Yes, this is not the correct way. I would have opted to ping the gateway of the router. I did complained about this.
-
@joseph_1979 This kind of " misuse" i would characterize as (very) sloppy programming. Also, why is it requesting an IP address (192.168.1.207) it doesn't use itself (in my case 192.168.1.65). As the doorbells IP address is fixed, why not DHCP request this address?
-
@user_778275310854286_778275310854286 This could be the first assigned when DHCP was used. As I stated if this is used to verify the WIFI connectivity with the router then it is a bad design. Perhaps there is another purpose for which we are not aware of.
Doorbell keeps sending DHCP requests
-
I'm using the Reolink wifi doorbell (with latest frimware) which for the most part works great.
One thing keeps annoying me. The doorbell is assigned a fixed IP address (in the doorbell itself; 192.168.1.65) but for some reason it keeps on sending DHCP requests (192.168.1.207 ??????) to the DHCP server. It does this every 5 minutes for no valid reason. Also, the requested IP address is already in use by an other device.
Why does it do this? This is no normal behavior for a network device. It keeps polluting the routers log and probably interferes with the other devices valid DHCP request.
I experimented with a static IP address in the doorbell, with a static IP address in the DHCP server and an automatic assigned one but it keeps on doing this. Even a complete reset of the doorbell doesn't work.