What's new

ASUS RT-AC87U reconnecting clients on loop ???

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Ricardo Carreira

New Around Here
Hello, why sometimes this appens in my router?

I have the latest Firmware

Code:
Mar 15 20:49:02 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) ec:fa:bc:4f:a4:f1
Mar 15 20:49:02 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.72 ec:fa:bc:4f:a4:f1
Mar 15 20:49:02 dnsmasq-dhcp[2735]: DHCPREQUEST(br0) 192.168.1.72 ec:fa:bc:4f:a4:f1
Mar 15 20:49:02 dnsmasq-dhcp[2735]: DHCPACK(br0) 192.168.1.72 ec:fa:bc:4f:a4:f1 Toilet_Fan
Mar 15 20:49:03 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 2c:f4:32:68:8e:e0
Mar 15 20:49:03 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.101 2c:f4:32:68:8e:e0
Mar 15 20:49:03 dnsmasq-dhcp[2735]: DHCPREQUEST(br0) 192.168.1.101 2c:f4:32:68:8e:e0
Mar 15 20:49:03 dnsmasq-dhcp[2735]: DHCPACK(br0) 192.168.1.101 2c:f4:32:68:8e:e0 Entryway_Light
Mar 15 20:49:03 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 10:52:1c:e8:58:f0
Mar 15 20:49:03 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.61 10:52:1c:e8:58:f0
Mar 15 20:49:03 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f2:77:dd
Mar 15 20:49:03 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.82 98:f4:ab:f2:77:dd
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 8c:aa:b5:05:b2:6c
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.52 8c:aa:b5:05:b2:6c
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f3:01:8d
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.92 98:f4:ab:f3:01:8d
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 10:52:1c:e8:18:e7
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.62 10:52:1c:e8:18:e7
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 68:c6:3a:d5:e7:f0
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.56 68:c6:3a:d5:e7:f0
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPREQUEST(br0) 192.168.1.56 68:c6:3a:d5:e7:f0
Mar 15 20:49:04 dnsmasq-dhcp[2735]: DHCPACK(br0) 192.168.1.56 68:c6:3a:d5:e7:f0 Bathroom_Heater
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 64:90:c1:7c:f0:ca
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.93 64:90:c1:7c:f0:ca
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPREQUEST(br0) 192.168.1.93 64:90:c1:7c:f0:ca
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPACK(br0) 192.168.1.93 64:90:c1:7c:f0:ca Xiaomi_Heater_Br3
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 2c:f4:32:68:c5:a0
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.65 2c:f4:32:68:c5:a0
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f2:77:dd
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.82 98:f4:ab:f2:77:dd
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 10:52:1c:e8:58:29
Mar 15 20:49:05 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.64 10:52:1c:e8:58:29
Mar 15 20:49:06 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 10:52:1c:e8:18:e7
Mar 15 20:49:06 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.62 10:52:1c:e8:18:e7
Mar 15 20:49:06 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f2:71:e8
Mar 15 20:49:06 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.66 98:f4:ab:f2:71:e8
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 2c:f4:32:68:c5:a0
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.65 2c:f4:32:68:c5:a0
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 2c:f4:32:68:92:6e
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.33 2c:f4:32:68:92:6e
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f2:e2:f8
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.46 98:f4:ab:f2:e2:f8
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 10:52:1c:e8:58:29
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.64 10:52:1c:e8:58:29
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 28:6d:97:c6:55:fc
Mar 15 20:49:07 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.47 28:6d:97:c6:55:fc
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f3:0b:3f
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.67 98:f4:ab:f3:0b:3f
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f3:01:8d
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.92 98:f4:ab:f3:01:8d
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 28:6d:97:c6:55:fc
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.47 28:6d:97:c6:55:fc
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 2c:f4:32:68:92:6e
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.33 2c:f4:32:68:92:6e
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f2:71:e8
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.66 98:f4:ab:f2:71:e8
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 10:52:1c:e8:58:f0
Mar 15 20:49:08 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.61 10:52:1c:e8:58:f0
Mar 15 20:49:09 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 98:f4:ab:f2:e2:f8
Mar 15 20:49:09 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.46 98:f4:ab:f2:e2:f8
Mar 15 20:49:09 dnsmasq-dhcp[2735]: DHCPDISCOVER(br0) 28:6d:97:c6:55:fc
Mar 15 20:49:09 dnsmasq-dhcp[2735]: DHCPOFFER(br0) 192.168.1.47 28:6d:97:c6:55:fc

what am i doing wrong?
Regards,
Ricardo
 
It's not necessarily a problem.

Those are DHCP requests (DHCPDISCOVER) being made by numerous devices. All of them are being offered an IP (DHCPOFFER), some are accepting the offer (DHCPREQUEST), and the server is acknowledging it (DHCPACK). In other cases, the process doesn't go beyond the DHCPOFFER, but since we only see a small window of time in the syslog (7 seconds), it could just be those requests and acknowledgments appear later in the syslog, esp. if the DHCP server is being overwhelmed over a short period of time.

So it's difficult to know if this is a problem or normal unless we have a much longer syslog to see the bigger, fuller picture.

Now *why* all these devices are asking to be configured at close to the same time is another question entirely. It appears as if all have been booted at the same time, as if they share an electrical circuit that was just turned ON. Is that possible? Or it might be that some of those devices are particularly sensitive to a router reboot (i.e., loss of connectivity), and are choosing to establish new DHCP leases. I often see this w/ cheap IOT devices.
 
Last edited:

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top