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

Allocate quickly /64 prefix on IPv6 parent #684

New Issue
Closed
opened 2025-12-29 16:24:43 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:24:43 +01:00
Owner
Copy Link

Originally created by @fcz83 on GitHub (Feb 1, 2017).

Hi,

First of all, congratulations on making this great product. We are already using it enthusiastically and we look forward to its development.

I have a simple (I believe?) request as we are now going to enable IPv6 on our access network. The intention is to allocate statically delegated prefixes (a /64) to the customer for its LAN out of a /48 pool. We will need to allocate this prefix on the IPAM and then provision it on the user profile on the RADIUS database.

It would be great if we could quickly allocate the next available /64 out of a /48 prefix from Netbox.. right now we can add a child object to a /48 but the information needs to be entered manually. Especially with IPv6, it can get messy as it's a 128 bit address.

We already do this with IPv4 simply by entering into a prefix and allocate a free ip address clicking on the Free IP button. The IP address tab gives the possibility to quickly allocate a free /32... it would be great to do the same with IPv6 as well for /64 subnets. Considering the structure of IPv6, I think allocation of /64 subnets is almost as important as allocation of single IP addresses.

I hope my request makes sense. Thanks again for this great project and keep up the good work!

Originally created by @fcz83 on GitHub (Feb 1, 2017). Hi, First of all, congratulations on making this great product. We are already using it enthusiastically and we look forward to its development. I have a simple (I believe?) request as we are now going to enable IPv6 on our access network. The intention is to allocate statically delegated prefixes (a /64) to the customer for its LAN out of a /48 pool. We will need to allocate this prefix on the IPAM and then provision it on the user profile on the RADIUS database. It would be great if we could quickly allocate the next available /64 out of a /48 prefix from Netbox.. right now we can add a child object to a /48 but the information needs to be entered manually. Especially with IPv6, it can get messy as it's a 128 bit address. We already do this with IPv4 simply by entering into a prefix and allocate a free ip address clicking on the Free IP button. The IP address tab gives the possibility to quickly allocate a free /32... it would be great to do the same with IPv6 as well for /64 subnets. Considering the structure of IPv6, I think allocation of /64 subnets is almost as important as allocation of single IP addresses. I hope my request makes sense. Thanks again for this great project and keep up the good work!
adam closed this issue 2025-12-29 16:24:44 +01:00
adam commented 2025-12-29 16:24:44 +01:00
Author
Owner
Copy Link

@puck commented on GitHub (Feb 7, 2017):

Sounds good. The recommendation for IPv6 is to use sparse allocation rather than the next available /64.

@puck commented on GitHub (Feb 7, 2017): Sounds good. The recommendation for IPv6 is to use sparse allocation rather than the next available /64.
adam commented 2025-12-29 16:24:45 +01:00
Author
Owner
Copy Link

@fcz83 commented on GitHub (Feb 7, 2017):

Allocation can be sparse..we don't have a need to have contiguous /64's allocated in the pool, as long as they are /64's! :-)

@fcz83 commented on GitHub (Feb 7, 2017): Allocation can be sparse..we don't have a need to have contiguous /64's allocated in the pool, as long as they are /64's! :-)
adam commented 2025-12-29 16:24:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 16, 2017):

Seems related to #665. What is the exact workflow you want to implement?

@jeremystretch commented on GitHub (Feb 16, 2017): Seems related to #665. What is the exact workflow you want to implement?
adam commented 2025-12-29 16:24:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 7, 2017):

Closing due to lack of activity.

@jeremystretch commented on GitHub (Mar 7, 2017): Closing due to lack of activity.
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#684
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?