@MelbourneMaker 

I have somewhat simpler home network configuration, with just ISP Router, and Deco M5/M9 mesh running in Access Point mode. When I deployed my Deco mesh, I wanted to assign static IP address to Main Deco, to have easier access to its web interface through Web browser.

I have found that while I can successfully add Main Deco to DHCP Reservation table of my ISP router, Main Deco does not get IP address I want assign to it. Main Deco gets proper IP address from DHCP range set on my router, but not the one I configured in DHCP Reservation table.

After relatively quick investigation I have found it is a bug with my ISP Router, HITRON CODA-4582.

Your issue seem to be different, because your Main Deco does get proper IP address after reboot. Yet, using same tools I did, it could be possible to narrow down location of the problem. 

If you want my assistance with that, please give me the following information:

What is DHCP Lease time in your DHCP server on the Router?

When the "Main Deco" unit is given a completely different IP address - is that IP address still from correct IP range?

Do you have access to DHCP Reservation table on DHCP server, which for each device listed there shows Client Name, MAC Address and IP address you want to assign to that client.

What is the client name for Main Deco you put in DHCP Reservation table? 

Do you have access to list of Connected Devices on your Router, which for each device listed there shows Host Name, MAC Address and IP address? If that list has other fields, such as Interface, Status and perhaps even field telling how device got its IP address (example: DHCP, DHCP-Reservation, Self-Assigned) - please let me know.

Alexandre. wrote

  @MelbourneMaker 

 

I have somewhat simpler home network configuration, with just ISP Router, and Deco M5/M9 mesh running in Access Point mode. When I deployed my Deco mesh, I wanted to assign static IP address to Main Deco, to have easier access to its web interface through Web browser.

I have found that while I can successfully add Main Deco to DHCP Reservation table of my ISP router, Main Deco does not get IP address I want assign to it. Main Deco gets proper IP address from DHCP range set on my router, but not the one I configured in DHCP Reservation table.

 

After relatively quick investigation I have found it is a bug with my ISP Router, HITRON CODA-4582.

 

Your issue seem to be different, because your Main Deco does get proper IP address after reboot. Yet, using same tools I did, it could be possible to narrow down location of the problem. 

If you want my assistance with that, please give me the following information:

 

What is DHCP Lease time in your DHCP server on the Router?

 

When the "Main Deco" unit is given a completely different IP address - is that IP address still from correct IP range?

 

Do you have access to DHCP Reservation table on DHCP server, which for each device listed there shows Client Name, MAC Address and IP address you want to assign to that client.

 

What is the client name for Main Deco you put in DHCP Reservation table? 

 

Do you have access to list of Connected Devices on your Router, which for each device listed there shows Host Name, MAC Address and IP address? If that list has other fields, such as Interface, Status and perhaps even field telling how device got its IP address (example: DHCP, DHCP-Reservation, Self-Assigned) - please let me know.

  @Alexandre. 

Thanks for your reply. In response to the questions you have raised:

1. The DHCP Lease time has been set at 2880, 1440, 60 and 30 minutes, and the same issue occurs. Currently the lease time is set to 2880 minutes (or 48 hours), which is the maximum lease time.

2. The DHCP assigned IP address, after a power cycle, is xxx.xxx.2.5. The completely different IP address that sometimes is used is always xxx.xxx.2.252. This IP address is from the same DHCP range, however no DHCP reservation exists for it, and it is not assigned to any MAC address.  

3. The DHCP reservations are all handled by the TP Link Omada Gigabit VPN router (ER605 v1.0), and configured through the Omada Controller instance. The list of reservations shows the MAC Address, Assigned IP Address, Network, Description, & whether the reservations is enabled or not. The DHCP reservations are assigned using the connecting devices' MAC Address. The entry for the "Main Deco" has the correct MAC address, an assigned IP Address which is used when the device is power cycled, and the entry is enabled.

4. The client name for the "Main Deco" is "office" which was defined in the iOS App when the location of the device was selected.

5. The complete list of network devices is available via the Omada Controller software, and shows the "Main Deco"'s MAC address and IP address. All devices on my network are configured to obtain their IP Addresses from the DHCP server, and every device has a reserved IP address in the DHCP configuration. Unfortunately the logs within Omada Controller do not provide details regarding the provision of IP addresses to clients on the network.

It's strange how this happens regularly... and can only be rectified by power cycling the "Main Dec" unit.

  @MelbourneMaker 

I am going to leave troubleshooting to TP-Link senior engineers, now that they are involved. When they find where the problem is, I'll appreciate you posting their findings here.

------------------------

There are two things I was going to suggest. 

1. Double check MAC address of Main Deco as reported in Router and in Deco app. For Deco running in AP mode, it should be the same as on the label at the bottom of the unit. When Deco gets "different IP address," check if MAC address reported for Main Deco in Deco app and in router is now is off by one (the last character of label MAC(hexadecimal)+1). For example: xxxxxxxxxx87------>xxxxxxxxxx88

2. When Main Deco is with its xxx.xxx.2.5 IP address, create an entry in DHCP Reservation table with made up MAC address and IP address xxx.xxx.2.252. After DHCP renewal by Main Deco, if it still reports xxx.xxx.2.252 - that would mean Deco unit decided to assign that IP to itself. DHCP server would never do that when there is an entry in DHCP Reservation table for different device.

If, on the other side, Main Deco now reports IP address different from xxx.xxx.2.252 and  xxx.xxx.2.5 - I would look more carefully at what's up with DHCP server.

-------------------------

Finally, if everyone is out of ideas, I would suggest creating an entry in DHCP Reservation table for Main Deco with its MAC address, and IP address xxx.xxx.2.252. If that makes Main Deco always run with IP address xxx.xxx.2.252, I would leave it at that.