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

IPAM nesting bug - showing false positive #11465

New Issue
Closed
opened 2025-12-29 21:45:37 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:45:37 +01:00
Owner
Copy Link

Originally created by @Jeffrey-FB on GitHub (Aug 11, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.0

Python Version

3.11

Steps to Reproduce

create a IPAM prefix container for 10.100.0.0/15
Then a container 10.100.0.0/16
Then a container 10.100.241.0/24
Then create a vrf for 10.100.241.0/29
and 10.100.241.8/29

Expected Behavior

10.100.241.0/29 and 10.100.241.8/29 show show as stepped on the prefix page as a child of 10.100.241.0/24
e.g.
--10.100.241.0/24
---10.100.241.0/29
---10.100.241.8/29

The /29 should show as child prefixes in the /24 'Child Prefix' tab

Observed Behavior

the /29 do not step on the IPAM -> Prefix menu
But they do show in the 'Child Prefixes' in the tab of 10.100.241.0/24
the 10.100.241.0/24 container Utilization also shows 0.0% even though it say it has Child Prefixes
As per images attached.

I have tried changing the container /24 to active all this seems to do is remove all the child /29 from it.
And the same applies if i try change the status of the /29's they just remove themselves as a child prefix from the /24

Is there a way to fix this, can I gather some extra info to help resolve this for us?
Thanks

Image Image
Originally created by @Jeffrey-FB on GitHub (Aug 11, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.0 ### Python Version 3.11 ### Steps to Reproduce create a IPAM prefix container for 10.100.0.0/15 Then a container 10.100.0.0/16 Then a container 10.100.241.0/24 Then create a vrf for 10.100.241.0/29 and 10.100.241.8/29 ### Expected Behavior 10.100.241.0/29 and 10.100.241.8/29 show show as stepped on the prefix page as a child of 10.100.241.0/24 e.g. --10.100.241.0/24 ---10.100.241.0/29 ---10.100.241.8/29 The /29 should show as child prefixes in the /24 'Child Prefix' tab ### Observed Behavior the /29 do not step on the IPAM -> Prefix menu But they do show in the 'Child Prefixes' in the tab of 10.100.241.0/24 the 10.100.241.0/24 container Utilization also shows 0.0% even though it say it has Child Prefixes As per images attached. I have tried changing the container /24 to active all this seems to do is remove all the child /29 from it. And the same applies if i try change the status of the /29's they just remove themselves as a child prefix from the /24 Is there a way to fix this, can I gather some extra info to help resolve this for us? Thanks <img width="736" height="631" alt="Image" src="https://github.com/user-attachments/assets/8c637d54-bf56-4418-9991-fe8d0b5fe6a0" /> <img width="1107" height="637" alt="Image" src="https://github.com/user-attachments/assets/36c1063f-3877-47cf-83e3-95db3e3543cd" />
adam added the netbox label 2025-12-29 21:45:37 +01:00
adam closed this issue 2025-12-29 21:45:37 +01:00
adam commented 2025-12-29 21:45:37 +01:00
Author
Owner
Copy Link

@kyerlasswell commented on GitHub (Aug 12, 2025):

Your container prefixes aren't in the same VRF as your /29s.

The whole hierarchy you created needs to be in the VRF you made; they default to the Global VRF otherwise.

IPAM > Prefixes list:
Image

Child prefixes of 10.100.241.0/24 in the custom VRF:

Image
@kyerlasswell commented on GitHub (Aug 12, 2025): Your container prefixes aren't in the same VRF as your /29s. The whole hierarchy you created needs to be in the VRF you made; they default to the `Global` VRF otherwise. IPAM > Prefixes list: <img width="484" height="215" alt="Image" src="https://github.com/user-attachments/assets/3addbb44-7724-4f14-ab80-da926bd7928d" /> Child prefixes of 10.100.241.0/24 in the custom VRF: <img width="618" height="477" alt="Image" src="https://github.com/user-attachments/assets/cf3a6b46-880b-4ac4-8f4e-1dba7b7aefe7" />
adam commented 2025-12-29 21:45:38 +01:00
Author
Owner
Copy Link

@Jeffrey-FB commented on GitHub (Aug 14, 2025):

Aah, I see.
The /29 's are the isc's for each vrf, which is why 10.100.241.0/24 is in global.
So I'm using 10.100.0.0/15 for our region (Also Global) and then we break it down to /18, /20, /22, /24 from there.
And assign those to the vrf's

Guess there is no way around that?
e.g. Instead of using Global for the /15 is there a way to place it for a region so that all the 10.100.0.0/15 will fall in there.
Everything seems to show up in the Child Prefixes for the /15.
It was just more an aesthetic thing so everything nests nicely.

@Jeffrey-FB commented on GitHub (Aug 14, 2025): Aah, I see. The /29 's are the isc's for each vrf, which is why 10.100.241.0/24 is in global. So I'm using 10.100.0.0/15 for our region (Also Global) and then we break it down to /18, /20, /22, /24 from there. And assign those to the vrf's Guess there is no way around that? e.g. Instead of using Global for the /15 is there a way to place it for a region so that all the 10.100.0.0/15 will fall in there. Everything seems to show up in the Child Prefixes for the /15. It was just more an aesthetic thing so everything nests nicely.
adam commented 2025-12-29 21:45:38 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Aug 18, 2025):

@Jeffrey-FB It sounds like this isn't a bug if I'm reading this correctly as per Kyler's comment. Converting this to a discussion.

@arthanson commented on GitHub (Aug 18, 2025): @Jeffrey-FB It sounds like this isn't a bug if I'm reading this correctly as per Kyler's comment. Converting this to a discussion.
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#11465
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?