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

Enforce Uniqueness of IP address in only one interface #6012

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

Originally created by @jk-onnet on GitHub (Jan 28, 2022).

NetBox version

v3.1.6

Feature type

Change to existing functionality

Proposed functionality

Prevent duplication of IP address on same network interface.
I'm not sure is this logically and intended function on same network interface?

Use case

Currently, we can add same prefix number of IP address with identical prefix number of IP address into an interface.
For example,

  1. add 192.168.1.24/24 into same network interface e0/1 of same device A1
  2. add 192.168.1.24/24 into same network interface e0/1 of same device A1
    If the development may takes time or irrelevant to core proposal, it can be ignored.

Database changes

No response

External dependencies

No response

Originally created by @jk-onnet on GitHub (Jan 28, 2022). ### NetBox version v3.1.6 ### Feature type Change to existing functionality ### Proposed functionality Prevent duplication of IP address on same network interface. I'm not sure is this logically and intended function on same network interface? ### Use case Currently, we can add same prefix number of IP address with identical prefix number of IP address into an interface. For example, 1) add 192.168.1.24/24 into same network interface e0/1 of same device A1 2) add 192.168.1.24/24 into same network interface e0/1 of same device A1 If the development may takes time or irrelevant to core proposal, it can be ignored. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:35:41 +01:00
adam closed this issue 2025-12-29 19:35:41 +01:00
adam commented 2025-12-29 19:35:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 28, 2022):

I think it makes sense to enforce the validation as proposed, though I'm not sure how much of an impact doing so would have on performance. AFAICT we would need to retrieve all IPs already assigned to the interface in order to validate the new one; this could be problematic for bulk operations. Still, it's worth looking into.

@jeremystretch commented on GitHub (Jan 28, 2022): I think it makes sense to enforce the validation as proposed, though I'm not sure how much of an impact doing so would have on performance. AFAICT we would need to retrieve all IPs already assigned to the interface in order to validate the new one; this could be problematic for bulk operations. Still, it's worth looking into.
adam commented 2025-12-29 19:35:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 30, 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 30, 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:35:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 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 (Jun 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:35:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 6, 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 (Jul 6, 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: needs owner 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#6012
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?