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

Fully Random IPv6 IIDs #5830

New Issue
Closed
opened 2025-12-29 19:33:15 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:33:15 +01:00
Owner
Copy Link

Originally created by @itsgottabered on GitHub (Dec 23, 2021).

NetBox version

v3.1.2

Feature type

New functionality

Proposed functionality

Addition of a toggle when adding ipv6 addresses to create a fully random IID.

  • Toggle at prefix level so any ip address created would be random (GUI tickbox in prefix options)
  • Toggle at address creation to select if address should be random (GUI - when in prefix -> ip addressed, maybe an additional button for create random address, or a sub-button on 'add an IP address' to select random)
  • Toggle for api endpoint for creating random address, /ipam/ip-ranges/{id}/available-ips/,
    ​/ipam​/prefixes​/{id}​/available-ips​/ to allow for programmatic creation of random addresses.

Use case

RFC7721 outlines use of different IID generation techniques to enhance security. Unpredictable IIDs add another layer of opaqueness to the network and having the ability to create random IIDs from Netbox will assist adoption of these techniques.

Database changes

No response

External dependencies

No response

Originally created by @itsgottabered on GitHub (Dec 23, 2021). ### NetBox version v3.1.2 ### Feature type New functionality ### Proposed functionality Addition of a toggle when adding ipv6 addresses to create a fully random IID. * Toggle at prefix level so any ip address created would be random (GUI tickbox in prefix options) * Toggle at address creation to select if address should be random (GUI - when in prefix -> ip addressed, maybe an additional button for create random address, or a sub-button on 'add an IP address' to select random) * Toggle for api endpoint for creating random address, /ipam/ip-ranges/{id}/available-ips/, ​/ipam​/prefixes​/{id}​/available-ips​/ to allow for programmatic creation of random addresses. ### Use case RFC7721 outlines use of different IID generation techniques to enhance security. Unpredictable IIDs add another layer of opaqueness to the network and having the ability to create random IIDs from Netbox will assist adoption of these techniques. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:33:15 +01:00
adam closed this issue 2025-12-29 19:33:15 +01:00
adam commented 2025-12-29 19:33:16 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 23, 2021):

Might make sense to also allow computation based on EUI-64 in addition to this random generation.

@DanSheps commented on GitHub (Dec 23, 2021): Might make sense to also allow computation based on EUI-64 in addition to this random generation.
adam commented 2025-12-29 19:33:16 +01:00
Author
Owner
Copy Link

@itsgottabered commented on GitHub (Dec 23, 2021):

Might make sense to also allow computation based on EUI-64 in addition to this random generation.

I did think about some of the other cases in the RFC but thought it might be too niche of a request. However, I was thinking if you added an address from an interface that had a MAC address configured, EUI-64 could be an option there.

@itsgottabered commented on GitHub (Dec 23, 2021): > Might make sense to also allow computation based on EUI-64 in addition to this random generation. I did think about some of the other cases in the RFC but thought it might be too niche of a request. However, I was thinking if you added an address from an interface that had a MAC address configured, EUI-64 could be an option there.
adam commented 2025-12-29 19:33:17 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 6, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 6, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:33:17 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 5, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Apr 5, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: under review 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#5830
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?