1
Votes

Routers can't release DHCP leases when managed by a controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
 
1
Votes

Routers can't release DHCP leases when managed by a controller

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Routers can't release DHCP leases when managed by a controller
Routers can't release DHCP leases when managed by a controller
2024-12-10 21:26:42 - last edited 2024-12-11 15:21:48
Model: ER605 (TL-R605)   ER7212PC  
Hardware Version: V2
Firmware Version: N/A

Currently, there is no function to release DHCP leases on routers when accessing them through hardware controllers. That is problematic when attempting to troubleshoot devices, setup networks, and create static IPs via MAC address binding.The current solution from TP-Link support is to block the device, and unblock the device through the client list. Every router should have this functionality, no matter how it is managed. Let's work together TP-Link, maybe we can figure something out.

#1
Options
3 Reply
Re:Routers can't release DHCP leases when managed by a controller
2024-12-11 01:20:46

Hi @Medcor_Matt 

Thanks for posting in our business forum.

Can you provide any links to this feature on a different brand?

What I learned from Huawei is that it resets the whole VLAN interface to release the IP.

From the official docs of Huawei UG, it asks you to release the IP on the client instead of on the router.

Curious if there is any vendor that can do this. Appreciate it if you can list anyone with docs so I can fill a request.

#2
Options
Re:Routers can't release DHCP leases when managed by a controller
2024-12-11 15:17:07

  @Clive_A I understand that a true release of a DHCP lease is done on the client level. Most of the time I don't have the capability to access all of the computers or devices that are taking up the current IP address leases. I would like a way to release the entry from the router, so I can bind IPs to mac addresses, or just free them up in general. This also comes into play when you have a limited scope DHCP pool.

Say you have hundreds of routers with VPN and you only assign them a /28 range. The remote office has enough equipment to fill most of that range with just enough to spare. However, a surge in staff one day means some cell phones were connecting to the network, and now there's not enough IP addresses to go around. I would like to release those phones from the DHCP pool on the router, not block them. 

Fortinet has Fortimanager cloud management for their Fortigates. There is a feature called DHCP Query. From there I can see the connected clients and release their lease. 

Ubiqity cloud management has a feature to "reconnect" clients (it's also on the phone app). 

I'm sure there's more out there, but this is what I can dig up on a moments notice. We can argue semantics about how this process really works, but I would like a smoother, more intuitive way to accomplish this goal, instead of the current "Block" feature. 

#3
Options
Re:Routers can't release DHCP leases when managed by a controller
2024-12-12 02:13:17

Hi @Medcor_Matt 

Thanks for posting in our business forum.

Medcor_Matt wrote

  @Clive_A I understand that a true release of a DHCP lease is done on the client level. Most of the time I don't have the capability to access all of the computers or devices that are taking up the current IP address leases. I would like a way to release the entry from the router, so I can bind IPs to mac addresses, or just free them up in general. This also comes into play when you have a limited scope DHCP pool.

Say you have hundreds of routers with VPN and you only assign them a /28 range. The remote office has enough equipment to fill most of that range with just enough to spare. However, a surge in staff one day means some cell phones were connecting to the network, and now there's not enough IP addresses to go around. I would like to release those phones from the DHCP pool on the router, not block them. 

Fortinet has Fortimanager cloud management for their Fortigates. There is a feature called DHCP Query. From there I can see the connected clients and release their lease. 

Ubiqity cloud management has a feature to "reconnect" clients (it's also on the phone app). 

I'm sure there's more out there, but this is what I can dig up on a moments notice. We can argue semantics about how this process really works, but I would like a smoother, more intuitive way to accomplish this goal, instead of the current "Block" feature. 


If you are asking for a reconnection option:

 

Try that out?

#5
Options