Hi @daubstep 

Thanks for posting in our business forum.

The system now will report anything related to the DHCP in the log now. If that bothers you, you can disable them in the settings.

About this log, it's a wireless device joining and disconnecting the network several time and it shows this rejection after it has successfully acquired an IP address from the DHCP server.

I assume this is not a problem with either one of them. It seems to be the device switching between the AP's, and it thinks this is a new network and requested the DHCP again.

It should not impact it at all. It should work okay as far as I can see.

Just this device's designed to send the DHCP request whenever it joins a network. And the server already assigned the IP to this MAC address(device). So, it rejects the request and tells it no.

The controller will add more and more logs for transparency, and that may cause unnecessary concerns, of course, and will display the logs that were there before, but we did not display them in the past controller versions.

Hi @daubstep 

Thanks for posting in our business forum.

daubstep wrote

  @Clive_A Thanks for replying - I think you missed the point of my post. I have clients configured to use fixed IPs, but the DHCP server denies them their configured IP, which is logged (but without a reason) and gives them an IP other than is configured in DHCP. This just recently started. The logs aren't the problem, but they document the problem.

 

In this log example, the client is configured (see all the screenshots) to be assigned IP "192.168.4.81", it requests this IP, the DHCP server rejects this request, and instead assigns it 192.168.4.180, which is not configured for this device (see the screenshots). This is causing active problems due to access controls for this device set up for the assigned "192.168.4.81" IP address which the router's DHCP server just started rejecting, until a router reboot, after which it works correctly for <24hrs.

 

In one of the screenshots, you can see the client list showing the device was assigned 4.175 next to the Fixed IP Configuration showing it should be 4.81.

In the screenshot of the logs for two days, you can see it working correctly for 4.81, being rejected and assigned the wrong IP address, then I reboot the router (not shown in the logs here) and things work for the rest of the night on the 30th and into the morning of the 31st, but by the afternoon of the 31st it is rejecting the DHCP request and assigning the wrong IP again - all to the same MAC address, which is the MAC address configured as shown in the other screenshots. Finally, at 4:26, after another router reboot, you can see the device being correctly assgined the 4.81 IP address again.

When you set a new reservation to a device, both the server and the client should be rebooted.

For the server, it should have the previous IP and MAC binding expire. After this expiration, you connect the client. Or you gotta force both of them to reboot.

More specifically, I need Wireshark results and see how they interact. If it is the client keeps requesting or renewing the wrong or the router is giving the previously unreleased IP or sending a completely wrong IP at the first DHCP request.

How Does DHCP Work? Common Questions and Solutions 

Hi @daubstep 

Thanks for posting in our business forum.

daubstep wrote

  @Clive_A I believe it has happened to at least one wired device. The one I've included in the logs here happens to be wireless and has caused the most problems (likely being mobile it renews its lease more often than wired devices). Do you know what the ETA is on the new version (or a beta) with the fix? I have also seen another user posting with the same random wrong-DHCP issue also with a ER707-M2 over in the /r/TPLink_Omada subreddit.

This issue only happens to the ER707-M2. Someone has reported it before.

I learned it is known from the dev. They are aware of it but did not provide the ETA.