DHCP requests from v3 cameras

My v3 cameras are constantly requesting DHCP addresses. Is anyone else noticing a lot of DHCP requests from their v3 cameras?

My DHCP server is setup with static reservations for everything on this particular vLAN. This includes three v3’s, three v2’s, and two color bulbs. Check out the screen shot below, which is a log from my SonicWALL where my DHCP server for this vLAN lives. Notice the same three MAC addresses are constantly requesting a DHCP address. Those are the v3 MAC addresses. Nothing else on this vLAN is constantly requesting a DHCP address.

All of my v3’s are running the same version of firmware, which is the current official release: 4.36.1.4 (May 5, 2021)

Edit:
I just checked my WiFi access point syslog files. The files were running about 135kb a day in size. Since upgrading the firmware on my v3 cameras, the daily WiFi syslog file is over 1MB in size. Guess what is causing this increase? It’s all related to DHCP requests!

WYZE: Please fix your latest release of v3 firmware.

@WyzeGwendolyn

I don’t think it’s a camera firmware issue. I watch DHCP traffic fairly closely on my routers, and have DHCP reservations for all the cameras as you do. I have seven operational V3 cameras (had eight, I killed one). Six of those are running 4.36.2.5 (the latest beta), but the one in my truck was out of WiFi range when that beta came out, so it is still 4.36.1.4. I am watching the router that is the DHCP server for that LAN and as I type this camera 26 last received a DHCP address 54 minutes, 35 seconds ago (when it got back in WiFi range after my wife and I went out for breakfast). Looking back, the DHCP performance is perfectly normal for all 26 Wyze cameras (18 V2, two Pan, and six V3 (one is not powered up at this time)). Normally the only reason a DHCP client will keep requesting an address is if either the lease time is only a few seconds (unlikely), or the DHCP lease handshake process does not complete.
I am wondering if this is relating to the DHCP Server notice message that your log also shows. Just a guess…

1 Like

Many devices seem to do that on my router, Wyze, Honeywell, Obi, etc…

Typical log off my router, just taken and MAC’s edited out with x’s

2021-05-22 15:06:40 dhcpd: DHCPACK on 192.168.1.28 to xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:06:41 dhcpd: DHCPREQUEST for 192.168.1.31 from xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:06:41 dhcpd: DHCPACK on 192.168.1.31 to xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:06:49 dhcpd: DHCPREQUEST for 192.168.1.117 from xx:xx:xx:xx:xx:xx (OBi202) via br0
2021-05-22 15:06:49 dhcpd: DHCPACK on 192.168.1.117 to xx:xx:xx:xx:xx:xx (OBi202) via br0
2021-05-22 15:06:53 hmpclientd[1457]: Login Successful
2021-05-22 15:07:07 dhcpd: DHCPREQUEST for 192.168.1.26 from xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:07 dhcpd: DHCPACK on 192.168.1.26 to xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:11 dhcpd: DHCPREQUEST for 192.168.1.27 from xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:07:11 dhcpd: DHCPACK on 192.168.1.27 to xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:07:15 dhcpd: DHCPREQUEST for 192.168.1.22 from xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:15 dhcpd: DHCPACK on 192.168.1.22 to xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:15 dhcpd: DHCPREQUEST for 192.168.1.18 from xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:15 dhcpd: DHCPACK on 192.168.1.18 to xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:26 dhcpd: DHCPREQUEST for 192.168.1.16 from xx:xx:xx:xx:xx:xx (AlarmSysxxxxxx) via br0
2021-05-22 15:07:26 dhcpd: DHCPACK on 192.168.1.16 to xx:xx:xx:xx:xx:xx (AlarmSysxxxxxx) via br0
2021-05-22 15:07:27 dhcpd: DHCPREQUEST for 192.168.1.105 from xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:27 dhcpd: DHCPACK on 192.168.1.105 to xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:41 dhcpd: DHCPREQUEST for 192.168.1.115 from xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:41 dhcpd: DHCPACK on 192.168.1.115 to xx:xx:xx:xx:xx:xx via br0
2021-05-22 15:07:57 dhcpd: DHCPREQUEST for 192.168.1.7 from xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:07:57 dhcpd: DHCPACK on 192.168.1.7 to xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:07:59 dhcpd: DHCPREQUEST for 192.168.1.20 from xx:xx:xx:xx:xx:xx (OnePlus-7T-Pro-5G) via br0
2021-05-22 15:07:59 dhcpd: DHCPACK on 192.168.1.20 to xx:xx:xx:xx:xx:xx (OnePlus-7T-Pro-5G) via br0
2021-05-22 15:08:01 dhcpd: DHCPREQUEST for 192.168.1.4 from xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:08:01 dhcpd: DHCPACK on 192.168.1.4 to xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:08:02 dhcpd: DHCPREQUEST for 192.168.1.30 from xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:08:02 dhcpd: DHCPACK on 192.168.1.30 to xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:08:03 dhcpd: DHCPREQUEST for 192.168.1.8 from xx:xx:xx:xx:xx:xx (WyzeCam) via br0
2021-05-22 15:08:03 dhcpd: DHCPACK on 192.168.1.8 to xx:xx:xx:xx:xx:xx (WyzeCam) via br0

I appreciate the replies. With that said, when I unplug my v3’s I no longer have alerts showing up in my SonicWALL. Also, as mentioned, I have plenty of other wise gear that is not creating these alerts. There is something unique to the v3’s…