One device is spamming dhcp requests to server -> filling logs

General questions
1

Hi all,

I have this one smart plug on my home network (it’s one of three plugs from the same manufacturer) that keeps spamming requests like below to the server. It’s filled the logs. The other two plugs nor any other device on the network do not behave like this. Functionally, this plug is working but am at a loss as to why it keeps generating these requests. Anybody see something like this in the past?

Running VyOS 1.3-RC3 and extract of /var/log/messages is below. These lines repeat in all the messages.x log files…

Feb 22 08:44:42 hostname dhcpd[15101]: DHCPREQUEST for 10.0.40.70 from xx:xx:xx:xx:xx:xx (Switch-00018529) via eth1
Feb 22 08:44:42 hostname dhcpd[15101]: DHCPACK on 10.0.40.70 to xx:xx:xx:xx:xx:xx (Switch-00018529) via eth1
Feb 22 08:44:42 hostname dhcpd[15101]: data: host_decl_name: not available
Feb 22 08:44:42 hostname vyos-hostsd[825]: Request data: {"type": "hosts", "op": "add", "data": {"dhcp-server-10.0.40.70": {"Switch-00018529.home.arpa": {"address": ["10.0.40.70"], "aliases": []}}}}
Feb 22 08:44:42 hostname vyos-hostsd[825]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Feb 22 08:44:42 hostname vyos-hostsd[825]: Sent response: {'data': None}
Feb 22 08:44:42 hostname vyos-hostsd[825]: Request data: {"op": "apply"}
Feb 22 08:44:42 hostname vyos-hostsd[825]: Applying 1 changes
Feb 22 08:44:42 hostname vyos-hostsd[825]: Writing /etc/resolv.conf
Feb 22 08:44:42 hostname vyos-hostsd[825]: Writing /etc/hosts
Feb 22 08:44:42 hostname vyos-hostsd[825]: Writing /run/powerdns/recursor.vyos-hostsd.conf.lua
Feb 22 08:44:42 hostname vyos-hostsd[825]: Writing /run/powerdns/recursor.forward-zones.conf
Feb 22 08:44:42 hostname vyos-hostsd[825]: pdns_recursor not running, not sending "reload-lua-config"
Feb 22 08:44:42 hostname vyos-hostsd[825]: pdns_recursor not running, not sending "reload-zones"
Feb 22 08:44:42 hostname vyos-hostsd[825]: Success
Feb 22 08:44:42 hostname vyos-hostsd[825]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Feb 22 08:44:42 hostname vyos-hostsd[825]: Sent response: {'data': {'message': 'Applied 1 changes'}}
Feb 22 08:44:42 hostname dhcpd[15101]: DHCPREQUEST for 10.0.40.70 from xx:xx:xx:xx:xx:xx (Switch-00018529) via eth1
Feb 22 08:44:42 hostname dhcpd[15101]: DHCPACK on 10.0.40.70 to xx:xx:xx:xx:xx:xx (Switch-00018529) via eth1
Feb 22 08:44:42 hostname dhcpd[15101]: data: host_decl_name: not available
Feb 22 08:44:42 hostname vyos-hostsd[825]: Request data: {"type": "hosts", "op": "add", "data": {"dhcp-server-10.0.40.70": {"Switch-00018529.home.arpa": {"address": ["10.0.40.70"], "aliases": []}}}}
Feb 22 08:44:42 hostname vyos-hostsd[825]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Feb 22 08:44:42 hostname vyos-hostsd[825]: Sent response: {'data': None}
Feb 22 08:44:42 hostname vyos-hostsd[825]: Request data: {"op": "apply"}
Feb 22 08:44:42 hostname vyos-hostsd[825]: Applying 1 changes
Feb 22 08:44:42 hostname vyos-hostsd[825]: Writing /etc/resolv.conf
Feb 22 08:44:42 hostname vyos-hostsd[825]: Writing /etc/hosts
Feb 22 08:44:42 hostname vyos-hostsd[825]: Writing /run/powerdns/recursor.vyos-hostsd.conf.lua
Feb 22 08:44:42 hostname vyos-hostsd[825]: Writing /run/powerdns/recursor.forward-zones.conf
Feb 22 08:44:42 hostname vyos-hostsd[825]: pdns_recursor not running, not sending "reload-lua-config"
Feb 22 08:44:42 hostname vyos-hostsd[825]: pdns_recursor not running, not sending "reload-zones"
Feb 22 08:44:42 hostname vyos-hostsd[825]: Success
Feb 22 08:44:42 hostname vyos-hostsd[825]: Saving state to /run/vyos-hostsd/vyos-hostsd.state
Feb 22 08:44:42 hostname vyos-hostsd[825]: Sent response: {'data': {'message': 'Applied 1 changes'}}
Feb 22 08:44:42 hostname dhcpd[15101]: DHCPREQUEST for 10.0.40.70 from xx:xx:xx:xx:xx:xx (Switch-00018529) via eth1
Feb 22 08:44:42 hostname dhcpd[15101]: DHCPACK on 10.0.40.70 to xx:xx:xx:xx:xx:xx (Switch-00018529) via eth1
Feb 22 08:44:42 hostname dhcpd[15101]: data: host_decl_name: not available```
2

Shutdown the interface to this device until the user have resolved the issue.

If unknown why the device behaves like this try to reflash it with latest firmware and see if that fixes the issue?

You can also try to connect it to a different interface or replace the network cable.

1 Like
3

Thanks @Apachez, I unplugged, powered down and reset the device entirely and after re-pairing it, it no longer is spamming DHCP messages. Strange but it’s solved now :slight_smile:

2 Likes
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.