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

Created new IP object is linked to all prefixes in same VRF #11264

New Issue
Closed
opened 2025-12-29 21:42:40 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:42:40 +01:00
Owner
Copy Link

Originally created by @Kompromatas on GitHub (Jun 6, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.2.9

Python Version

3.10

Steps to Reproduce

  1. Click on VRs
  2. Search for VRF1
  3. Choose prefix 192.168.5.0/24 (vlan 101) (there are more prefixes 192.168.5.0/24 on this VRF1 but in different vlans).
  4. Choose to add IP
  5. Enter address, as example 192.168.5.1/24
  6. Create.

New IP is created and it is linked to all prefixes 192.168.5.0/24 on different vlans, which are in the same vlan group (L2 domain) and are assigned to one VRF1.

Expected Behavior

  1. Click on VRs
  2. Search for VRF1
  3. Choose prefix 192.168.5.0/24 (vlan 101)
  4. Choose to add IP
  5. Enter address, as example 192.168.5.1/24
  6. Create.

New IP is created and is linked to only one prefix 192.168.5.0/24 in vlan 101

Observed Behavior

New IP is created and it is linked to all prefixes 192.168.5.0/24 on different vlans, which are in the same vlan group (L2 domain) and are assigned to one VRF1.
If via API I try to search the IP (192.168.5.1/24), the result records do not have information, that identifies the parent prefix.

Originally created by @Kompromatas on GitHub (Jun 6, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.2.9 ### Python Version 3.10 ### Steps to Reproduce 1. Click on VRs 2. Search for VRF1 3. Choose prefix 192.168.5.0/24 (vlan 101) (there are more prefixes 192.168.5.0/24 on this VRF1 but in different vlans). 4. Choose to add IP 5. Enter address, as example 192.168.5.1/24 7. Create. New IP is created and it is linked to all prefixes 192.168.5.0/24 on different vlans, which are in the same vlan group (L2 domain) and are assigned to one VRF1. ### Expected Behavior 1. Click on VRs 2. Search for VRF1 3. Choose prefix 192.168.5.0/24 (vlan 101) 4. Choose to add IP 5. Enter address, as example 192.168.5.1/24 7. Create. New IP is created and is linked to only one prefix 192.168.5.0/24 in vlan 101 ### Observed Behavior New IP is created and it is linked to all prefixes 192.168.5.0/24 on different vlans, which are in the same vlan group (L2 domain) and are assigned to one VRF1. If via API I try to search the IP (192.168.5.1/24), the result records do not have information, that identifies the parent prefix.
adam added the netbox label 2025-12-29 21:42:40 +01:00
adam closed this issue 2025-12-29 21:42:40 +01:00
adam commented 2025-12-29 21:42:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 6, 2025):

What you're describing is intended behavior. You need to create each prefix in a separate VRF if they belong to different L3 domains.

@jeremystretch commented on GitHub (Jun 6, 2025): What you're describing is intended behavior. You need to create each prefix in a separate VRF if they belong to different L3 domains.
adam commented 2025-12-29 21:42:40 +01:00
Author
Owner
Copy Link

@Kompromatas commented on GitHub (Jun 10, 2025):

When creating new VRF, there is an option which allows to create duplicate prefixes for VRF, that's why I thought that I could link IP only to one prefix.

@Kompromatas commented on GitHub (Jun 10, 2025): When creating new VRF, there is an option which allows to create duplicate prefixes for VRF, that's why I thought that I could link IP only to one prefix.
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 netbox
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#11264
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?