Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make IP range to be selectable when configuring interface IP address with DHCP status. #17514

Open
lopar opened this issue Sep 17, 2024 · 0 comments
Labels
netbox status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application

Comments

@lopar
Copy link

lopar commented Sep 17, 2024

NetBox version

v4.1.0

Feature type

New functionality

Proposed functionality

Make IP range to be selectable when configuring interface IP address. IP range should be selectable only if "DHCP" status is selected. Such DHCP interface ranges should count towards the utilization of the prefix/range. If you have a dynamic range 10.1.1.50 - 10.1.1.99, and you have assigned 25 interfaces to that range, the range should be treated as "50% used".

Of course static IP addresses from such range shoud be countable too. So, if you have a dynamic range 10.1.1.50 - 10.1.1.99, and you have assigned 20 interfaces as DHCP range and have also 5 static adresses from that range, the range should be treated as "50% used".

There should be additional system checks if IP range is already full:

  1. Addind new device to DHCP address pool when there are no place for it.
  2. Adding new static IP address to the range, when range don't have free slots.

Use case

It is common situation when devices in network are using DHCP leases from some IP pool, which adresses are not static, like wifi access points, virtual machines, etc, where static address is not an option, because it can be suddenly changed, making IPAM having wrong data.

I saw multiple discussions and issues about this situation without common answer, but different local situational workarounds. People need such functionality, it's not "one man issue".

Database changes

No response

External dependencies

No response

@lopar lopar added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Sep 17, 2024
@jeremystretch jeremystretch added the netbox label Nov 1, 2024 — with Linear
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
netbox status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants