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

IP addresses with overlapping prefixes permitted #3776

New Issue
Closed
opened 2025-12-29 18:31:10 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:31:10 +01:00
Owner
Copy Link

Originally created by @cmacnevin on GitHub (Jun 12, 2020).

Environment

  • Python version: 3.7.4
  • NetBox version: 2.8.5

Steps to Reproduce - all steps are in the UI

  1. Create a prefix, eg 10.0.0.0/8
  2. Create an ip address within that prefix with an arbitrary netmask, eg: 10.0.1.10/24.
  3. Create a second ip address with a netmask which creates an overlapping prefix range, eg: 10.0.1.11/25

Expected Behavior

Expect the second IP address to be rejected. This is not a valid entry in the real world, as it creates overlapping prefixes. Expect logic to anchor ip addresses to prefixes, similar to other IPAMs like Infoblox.

Observed Behavior

Both ip addresses are accepted. Conflict present in the data.

Originally created by @cmacnevin on GitHub (Jun 12, 2020). ### Environment * Python version: 3.7.4 * NetBox version: 2.8.5 ### Steps to Reproduce - all steps are in the UI 1. Create a prefix, eg 10.0.0.0/8 2. Create an ip address within that prefix with an arbitrary netmask, eg: 10.0.1.10/24. 3. Create a second ip address with a netmask which creates an overlapping prefix range, eg: 10.0.1.11/25 ### Expected Behavior Expect the second IP address to be rejected. This is not a valid entry in the real world, as it creates overlapping prefixes. Expect logic to anchor ip addresses to prefixes, similar to other IPAMs like Infoblox. ### Observed Behavior Both ip addresses are accepted. Conflict present in the data.
adam closed this issue 2025-12-29 18:31:10 +01:00
adam commented 2025-12-29 18:31:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 12, 2020):

NetBox does not have the necessary contextual information in this case to validate either address: You cannot assume either mask is correct. Thus, NetBox does not treat either as incorrect. Additionally, support for overlapping IP addresses within a table (VRF) would prevent enforcement of such validation even if the required context was present.

@jeremystretch commented on GitHub (Jun 12, 2020): NetBox does not have the necessary contextual information in this case to validate either address: You cannot assume either mask is correct. Thus, NetBox does not treat either as incorrect. Additionally, support for overlapping IP addresses within a table (VRF) would prevent enforcement of such validation even if the required context was present.
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#3776
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?