What does such a flood mean in the log (log) zyxel keenetic start?

I

Ilya Kuznetsov2016-09-29 15:52:02

network hardware

Ilya Kuznetsov, 2016-09-29 15:52:02

what does this log mean? wireless clients keep
crashing I] Sep 29 13:32:45 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.10 from 40:c6:2a:41:7e:f4.
[I] Sep 29 13:32:45 ndhcps: _WEBADMIN: sending ACK of 192.168.0.10 to 40:c6:2a:41:7e:f4.
[I] Sep 29 14:04:21 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_RENEWING) for 192.168.0.107 from 04:18:d6:e0:f4:57.
[I] Sep 29 14:04:21 ndhcps: _WEBADMIN: sending ACK of 192.168.0.107 to 04:18:d6:e0:f4:57.
[I] Sep 29 14:04:22 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_RENEWING) for 192.168.0.33 from 04:18:d6:e0:ff:b1.
[I] Sep 29 14:04:22 ndhcps: _WEBADMIN: sending ACK of 192.168.0.33 to 04:18:d6:e0:ff:b1.
[I] Sep 29 14:04:57 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_RENEWING) for 192.168.0.101 from 04:18:d6:86:d5:cc.
[I] Sep 29 14:04:57 ndhcps: _WEBADMIN: sending ACK of 192.168.0.101 to 04:18:d6:86:d5:cc.
[I] Sep 29 14:55:41 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 14:55:41 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 14:58:53 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 14:58:53 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 14:59:36 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 14:59:36 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 15:03:40 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_RENEWING) for 192.168.0.47 from 04:18:d6:e0:f0:2e.
[I] Sep 29 15:03:40 ndhcps: _WEBADMIN: sending ACK of 192.168.0.47 to 04:18:d6:e0:f0:2e.
[I] Sep 29 15:06:20 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 15:06:20 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 15:07:53 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 15:07:53 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 15:11:27 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_RENEWING) for 192.168.0.13 from 50:c8:e5:7e:c4:9e.
[I] Sep 29 15:11:27 ndhcps: _WEBADMIN: sending ACK of 192.168.0.13 to 50:c8:e5:7e:c4:9e.
[I] Sep 29 15:16:33 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 15:16:33 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 15:16:36 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 15:16:36 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 15:17:53 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 15:17:53 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 15:53:36 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_RENEWING) for 192.168.0.36 from 00:24:1d:9a:24:d7.
[I] Sep 29 15:53:36 ndhcps: _WEBADMIN: sending ACK of 192.168.0.36 to 00:24:1d:9a:24:d7.
[I] Sep 29 15:57:45 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_RENEWING) for 192.168.0.48 from 8c:fa:ba:f4:1e:a9.
[I] Sep 29 15:57:45 ndhcps: _WEBADMIN: sending ACK of 192.168.0.48 to 8c:fa:ba:f4:1e:a9.
[I] Sep 29 15:59:46 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_RENEWING) for 192.168.0.11 from 38:01:95:db:50:f4.
[I] Sep 29 15:59:46 ndhcps: _WEBADMIN: sending ACK of 192.168.0.11 to 38:01:95:db:50:f4.
[I] Sep 29 16:08:01 ndhcps: _WEBADMIN: DHCPDISCOVER received from 64:89:9a:87:db:15.
[I] Sep 29 16:08:01 ndhcps: _WEBADMIN: making OFFER of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:08:01 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_SELECTING) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:08:01 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:09:32 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:09:32 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:09:35 ndhcps: _WEBADMIN: DHCPDISCOVER received from 64:89:9a:87:db:15.
[I] Sep 29 16:09:36 ndhcps: _WEBADMIN: making OFFER of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:09:36 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_SELECTING) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:09:36 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:11:52 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:11:52 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:13:27 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:13:27 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:14:25 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:14:25 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:14:50 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:14:50 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:14:54 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:14:54 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:19:23 ndhcps: _WEBADMIN: DHCPDISCOVER received from 64:89:9a:87:db:15.
[I] Sep 29 16:19:23 ndhcps: _WEBADMIN: making OFFER of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:19:23 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_SELECTING) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:19:23 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:19:25 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:19:25 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:19:42 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:19:42 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:20:30 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:20:30 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:20:34 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from 64:89:9a:87:db:15.
[I] Sep 29 16:20:34 ndhcps: _WEBADMIN: sending ACK of 192.168.0.43 to 64:89:9a:87:db:15.
[I] Sep 29 16:21:58 ndhcps: _WEBADMIN: DHCPREQUEST received (STATE_INIT) for 192.168.0.43 from

Reply

Answer the question

In order to leave comments, you need to log in

2 answer(s)

A

Andrew, 2016-09-29
@OLS

DHCP clients are required to check with the server at the frequency specified at the time of the primary leasing address whether they can continue to use the IP address allocated to them. It is this activity that makes up the bulk of your log.

S

solalex, 2016-09-29
@solalex

I will add that each device that has received an ip address from the router comes for an extension of the address for half the term before it ends.
But you have one problematic client with MAC address 64:89:9a:87:db:15 to which the router allocates IP 192.168.