starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Extension of available-prefixes api endpoint #1544

New Issue
Closed
opened 2025-12-29 16:32:50 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:32:50 +01:00
Owner
Copy Link

Originally created by @dirtycajunrice on GitHub (Feb 8, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Description

The available prefix endpoint is a wonderful implementation, but only works for pre-existing larger prefixes. When you have an aggregate of Public IPs e.g. /21 and want to pull a new public prefix from that, it is not currently possible.

Thoughts? If wanted, I can try to add this myself this weekend. (Templetizing Jeremy's previous prefix addition)

Originally created by @dirtycajunrice on GitHub (Feb 8, 2018). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. For assistance with installation issues, or for any other issues other than those listed below, please raise your topic for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. Due to an excessive backlog of feature requests, we are not currently accepting any proposals which extend NetBox's feature scope. Do not prepend any sort of tag to your issue's title. An administrator will review your issue and assign labels as appropriate. ---> ### Issue type [x] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) If you are submitting a bug report and have made any changes to the code base, please first validate that your bug can be recreated while running an official release. --> <!-- FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description The available prefix endpoint is a wonderful implementation, but only works for pre-existing larger prefixes. When you have an aggregate of Public IPs e.g. /21 and want to pull a new public prefix from that, it is not currently possible. Thoughts? If wanted, I can try to add this myself this weekend. (Templetizing Jeremy's previous prefix addition)
adam closed this issue 2025-12-29 16:32:50 +01:00
adam commented 2025-12-29 16:32:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 13, 2018):

Aggregates behave a bit differently than prefixes in that they define a swath of IP address space which exists but has not been allocated for anything yet (and may not ever be fully utilized). In most cases, users probably want to select specific top-level allocations from aggregates. But if you do need to provision prefixes automatically, you have the option of defining a container prefix the same size as its aggregate.

@jeremystretch commented on GitHub (Feb 13, 2018): Aggregates behave a bit differently than prefixes in that they define a swath of IP address space which exists but has not been allocated for anything yet (and may not ever be fully utilized). In most cases, users probably want to select specific top-level allocations from aggregates. But if you do need to provision prefixes automatically, you have the option of defining a container prefix the same size as its aggregate.
adam commented 2025-12-29 16:32:51 +01:00
Author
Owner
Copy Link

@diman512 commented on GitHub (May 29, 2019):

Hi Jeremy,
Basically, I am facing the same issue, where we have an aggrigate prefixes of /8 or /16 and we do allocations of /24 from that aggregated prefix.
I need a way to know what aggregate prefix is full utilization so I can move over to the next /16 aggregated prefix.
Can you add an API for that?

@diman512 commented on GitHub (May 29, 2019): Hi Jeremy, Basically, I am facing the same issue, where we have an aggrigate prefixes of /8 or /16 and we do allocations of /24 from that aggregated prefix. I need a way to know what aggregate prefix is full utilization so I can move over to the next /16 aggregated prefix. Can you add an API for that?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1544
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?