Задать вопрос
Ilya221
@Ilya221
Начинающий админ
network-hardware

Что значит такой флуд в журнал (log) zyxel keenetic start?

что значит такой вот лог? вылетают беспроводные клиенты постоянно
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
  • Вопрос задан
  • 15800 просмотров
Комментировать
Подписаться 2 Оценить Комментировать
Пригласить эксперта
Ответы на вопрос 2
OLS
@OLS
DHCP клиенты обязаны с периодичностью, которая была задана в момент первичного leasing-а адреса, переуточнять у сервера, могут ли они дальше использовать выделенный им IP-адрес. Вот эта активность и составляет большую часть Вашего лога.
Ответ написан
Комментировать
Комментировать
@solalex
Дополню, что каждое устройство, получившее ip адрес от роутера, приходит за продлением адреса на половине срока до его окончания.
Но у вас есть один проблемный клиент с МАК-адресом 64:89:9a:87:db:15 которому роутер выделяет IP 192.168.0.43, но он его не получает по какой то причине, и постоянно долбит роутер запросами на получение адреса.
Ответ написан
Комментировать
Комментировать
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы
Вакансии с Хабр Карьеры
Специалист технической поддержки
DBI • Ростов-на-Дону
от 30 000 ₽
Senior ML Engineer (Computer Vision)
Gradient
от 450 000 ₽
Разработчик Java (Middle/Senior)
ДИКСИ • Москва
от 150 000 до 270 000 ₽
Ещё вакансии
Заказы с Хабр Фриланса
Дизайн интерьера для заведения
27 апр. 2024, в 21:24
150000 руб./за проект
Нужно добавить несколько параллакс эффектов
27 апр. 2024, в 21:12
500 руб./за проект
Доработать функционал загрузки прайсов в БД
27 апр. 2024, в 20:40
5000 руб./за проект
Ещё заказы