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

Prefixes appearing out of order #627

New Issue
Closed
opened 2025-12-29 16:24:02 +01:00 by adam · 5 comments
adam commented 2025-12-29 16:24:02 +01:00
Owner
Copy Link

Originally created by @CFRR on GitHub (Jan 16, 2017).

Hi,

We have for example a 10.172.0.0/16 and child prefixes 10.172.0.0/18, 10.172.64.0/18 and 10.172.128.0/17 and in Prefixes main page appears like this:

prefix_1

When I add a new prefix for example 10.220.0.0/16 appears like this:

prefix_2

This is a normal situation?

Originally created by @CFRR on GitHub (Jan 16, 2017). Hi, We have for example a 10.172.0.0/16 and child prefixes 10.172.0.0/18, 10.172.64.0/18 and 10.172.128.0/17 and in Prefixes main page appears like this: ![prefix_1](https://cloud.githubusercontent.com/assets/17024363/21982852/32a6cf02-dbe6-11e6-8957-475f2e772257.PNG) When I add a new prefix for example 10.220.0.0/16 appears like this: ![prefix_2](https://cloud.githubusercontent.com/assets/17024363/21982881/48e7f660-dbe6-11e6-9b93-210f7dbda90c.PNG) This is a normal situation?
adam closed this issue 2025-12-29 16:24:02 +01:00
adam commented 2025-12-29 16:24:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 17, 2017):

What version of NetBox are you using? I'm not able to replicate this on v1.8.1.

@jeremystretch commented on GitHub (Jan 17, 2017): What version of NetBox are you using? I'm not able to replicate this on v1.8.1.
adam commented 2025-12-29 16:24:03 +01:00
Author
Owner
Copy Link

@CFRR commented on GitHub (Jan 17, 2017):

Hi Jeremy,
I'm using the last version v1.8.1.

@CFRR commented on GitHub (Jan 17, 2017): Hi Jeremy, I'm using the last version v1.8.1.
adam commented 2025-12-29 16:24:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 17, 2017):

Are you filtering or sorting the prefixes somehow? Can you explain the steps needed to recreate this please?

@jeremystretch commented on GitHub (Jan 17, 2017): Are you filtering or sorting the prefixes somehow? Can you explain the steps needed to recreate this please?
adam commented 2025-12-29 16:24:03 +01:00
Author
Owner
Copy Link

@CFRR commented on GitHub (Jan 17, 2017):

Jeremy,

Are you filtering or sorting the prefixes somehow?

No.

Can you explain the steps needed to recreate this please?

  1. Add a prefix: 10.172.0.0/16 VRF Global
  2. Add a child prefixes 10.172.0.0/18, 10.172.64.0/18 and 10.172.128.0/17 VRF A
  3. Add a prefix: 10.220.0.0/16 VRF Global

But the "issue" is that, the VRF are different, when I change to the same VRF the prefix are in order.
We have the concept of define a major prefix and divide in minor prefix by several VRF.

Is it possible to achieve this?
Thx.

@CFRR commented on GitHub (Jan 17, 2017): Jeremy, > Are you filtering or sorting the prefixes somehow? No. > Can you explain the steps needed to recreate this please? 1. Add a prefix: 10.172.0.0/16 VRF Global 2. Add a child prefixes 10.172.0.0/18, 10.172.64.0/18 and 10.172.128.0/17 VRF A 1. Add a prefix: 10.220.0.0/16 VRF Global But the "issue" is that, the VRF are different, when I change to the same VRF the prefix are in order. We have the concept of define a major prefix and divide in minor prefix by several VRF. Is it possible to achieve this? Thx.
adam commented 2025-12-29 16:24:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 17, 2017):

Oh, I see. Yes, this is expected behavior. The global table and the VRF table are treated as entirely separate IP spaces. NetBox lists all the prefixes from the global table first, followed by all the prefixes from VRF A.

Clicking the "Prefix" header of the table will sort all prefixes by their IP, without regard to VRF assignment.

@jeremystretch commented on GitHub (Jan 17, 2017): Oh, I see. Yes, this is expected behavior. The global table and the VRF table are treated as entirely separate IP spaces. NetBox lists all the prefixes from the global table first, followed by all the prefixes from VRF A. Clicking the "Prefix" header of the table will sort all prefixes by their IP, without regard to VRF assignment.
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#627
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?