Project

General

Profile

Actions

Feature #10250

open

DHCP lease view by interface

Added by Ciro Maretto about 4 years ago. Updated about 17 hours ago.

Status:
New
Priority:
Very Low
Assignee:
-
Category:
DHCP (IPv4)
Target version:
Start date:
02/11/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

Improve view: Group customers by interface.

Actions #1

Updated by Jim Pingle about 4 years ago

  • Subject changed from DHCP Leases Status to DHCP lease view by interface
  • Category set to DHCP (IPv4)
  • Priority changed from Low to Very Low
  • Target version set to Future

The leases are not tracked by interface, so this is not easily possible. Others have requested similar things in the past like filtering or grouping clients but there are several problems here:

1. As mentioned above, the lease database only holds address information, not interface information. We could infer some of that from the config, subnets/pools present on interfaces, etc, but it isn't a perfect solution.
2. Grouping by subnet/pool would be too granular since multiple pools could be on the same interface, though some people may want to filter per pool, some would want to filter by anything on an interface, so it would need to support both types of views.
3. As the lease database grows, this would scale poorly. It would consume more and more memory and CPU time to correlate all of the entries, so it would need to be optional and off by default.

So while it is likely possible, there is a lot of work involved.

2.4.5 adds searching to the list, which may eliminate some of the need for this, but it doesn't offer all of the same benefits.

Actions #2

Updated by Don Ireland about 17 hours ago

Jim Pingle wrote in #note-1:

The leases are not tracked by interface, so this is not easily possible. Others have requested similar things in the past like filtering or grouping clients but there are several problems here:

1. As mentioned above, the lease database only holds address information, not interface information. We could infer some of that from the config, subnets/pools present on interfaces, etc, but it isn't a perfect solution.
2. Grouping by subnet/pool would be too granular since multiple pools could be on the same interface, though some people may want to filter per pool, some would want to filter by anything on an interface, so it would need to support both types of views.
3. As the lease database grows, this would scale poorly. It would consume more and more memory and CPU time to correlate all of the entries, so it would need to be optional and off by default.

So while it is likely possible, there is a lot of work involved.

2.4.5 adds searching to the list, which may eliminate some of the need for this, but it doesn't offer all of the same benefits.

I think I have what would be a viable solution to accommodate most if not all the various ways people would want to do it. SAVED FILTERS

Allow the user to create saved filters. The user could filter for specific things. In my use case, I might filter for IP Addresses 10.10.0.<asterisk>. Then I could save that as VLAN100. I'd have another for IP Addresses 10.20.0.<asterisk> and save that as VLAN20.

Someone might make a filter called Shelly Devices and it would search for devices with Shelly in the hostname.

Once I've set up the saved filters, I could just pick one from a drop-down list and the lease list would update based on the filter.

Actions

Also available in: Atom PDF