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

Ability to assign whole prefix to an interface/device #5215

New Issue
Closed
opened 2025-12-29 19:25:31 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:25:31 +01:00
Owner
Copy Link

Originally created by @skrivy on GitHub (Aug 21, 2021).

NetBox version

v2.11.11

Feature type

New functionality

Proposed functionality

Add ability to assign whole IP range to an interface/device.

Use case

This is more related to IPv6. We have /64 range per server (or consumer device) and we don't care about address usage within that range. e.g. there are dynamically created containers on that server and their lifetime can be short.

But, it is important for us to know which range is assigned to each device or interface.

Database changes

To be established.

External dependencies

None as far as I know.

Originally created by @skrivy on GitHub (Aug 21, 2021). ### NetBox version v2.11.11 ### Feature type New functionality ### Proposed functionality Add ability to assign whole IP range to an interface/device. ### Use case This is more related to IPv6. We have /64 range per server (or consumer device) and we don't care about address usage within that range. e.g. there are dynamically created containers on that server and their lifetime can be short. But, it is important for us to know which range is assigned to each device or interface. ### Database changes To be established. ### External dependencies None as far as I know.
adam added the type: feature label 2025-12-29 19:25:31 +01:00
adam closed this issue 2025-12-29 19:25:32 +01:00
adam commented 2025-12-29 19:25:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 23, 2021):

Prefixes are associated to interfaces via the assignment of an IP address within that prefix.

@jeremystretch commented on GitHub (Aug 23, 2021): Prefixes are associated to interfaces via the assignment of an IP address within that prefix.
adam commented 2025-12-29 19:25:32 +01:00
Author
Owner
Copy Link

@skrivy commented on GitHub (Aug 26, 2021):

Yes. It is easy to assign all IP addresses in the prefix to a single machine with IPv4. But I am not able to assign all IPv6 addresses within /64 or even bigger.

After thinking about it for a while. I found some use cases of why we are looking for such a feature.

Search: When a temporary docker container with SLAAC address makes mess in the network, I would like to be able to quickly find on which machine the range resides.

API: With ability to assign whole range to a server, we could easily fetch prefixes for prefix delegation when our dhcpv6 server is asked by dhcp client.

However, feel free to close this feature request if it doesn't make sense or it is out of scope of this project. I understand this feature can be specific for our environment.

@skrivy commented on GitHub (Aug 26, 2021): Yes. It is easy to assign all IP addresses in the prefix to a single machine with IPv4. But I am not able to assign all IPv6 addresses within /64 or even bigger. After thinking about it for a while. I found some use cases of why we are looking for such a feature. Search: When a temporary docker container with SLAAC address makes mess in the network, I would like to be able to quickly find on which machine the range resides. API: With ability to assign whole range to a server, we could easily fetch prefixes for prefix delegation when our dhcpv6 server is asked by dhcp client. However, feel free to close this feature request if it doesn't make sense or it is out of scope of this project. I understand this feature can be specific for our environment.
adam commented 2025-12-29 19:25:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 27, 2021):

Yes. It is easy to assign all IP addresses in the prefix to a single machine with IPv4. But I am not able to assign all IPv6 addresses within /64 or even bigger.

You don't need to assign all IPs, just one. You can then easily infer the attached prefix from the assigned IP address.

@jeremystretch commented on GitHub (Aug 27, 2021): > Yes. It is easy to assign all IP addresses in the prefix to a single machine with IPv4. But I am not able to assign all IPv6 addresses within /64 or even bigger. You don't need to assign _all_ IPs, just one. You can then easily infer the attached prefix from the assigned IP address.
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 type: feature
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#5215
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?