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

Allow IP addresses or IP Ranges to be assigned to a site like Prefixes ? #8477

New Issue
Closed
opened 2025-12-29 20:37:14 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:37:14 +01:00
Owner
Copy Link

Originally created by @LeDistordu on GitHub (Aug 16, 2023).

NetBox version

v3.5.8

Feature type

New functionality

Proposed functionality

Allow IP Addresses and IP Ranges to be assigned to a Site/VLAN like Prefixes

Use case

Hi, Many of my sites use the same IP ranges and inevitably the same IPs. The philosophy on the Prefixes side is good, but it would be necessary to push the allocation of sites / vlan to IP addresses and ranges.

Database changes

none

External dependencies

none

Originally created by @LeDistordu on GitHub (Aug 16, 2023). ### NetBox version v3.5.8 ### Feature type New functionality ### Proposed functionality Allow IP Addresses and IP Ranges to be assigned to a Site/VLAN like Prefixes ### Use case Hi, Many of my sites use the same IP ranges and inevitably the same IPs. The philosophy on the Prefixes side is good, but it would be necessary to push the allocation of sites / vlan to IP addresses and ranges. ### Database changes none ### External dependencies none
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:37:14 +01:00
adam closed this issue 2025-12-29 20:37:14 +01:00
adam commented 2025-12-29 20:37:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 16, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Aug 16, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:37:15 +01:00
Author
Owner
Copy Link

@LeDistordu commented on GitHub (Aug 16, 2023):

sorry, it should be more understandable now

@LeDistordu commented on GitHub (Aug 16, 2023): sorry, it should be more understandable now
adam commented 2025-12-29 20:37:15 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Aug 17, 2023):

Unfortunately @LeDistordu this Feature Request is not really actionnable right as it is right now, even more so with your recent edits.

Please make sure your feature request conveys the intent and purpose of such feature and how others could benefit for it and again, perhaps an issue is not the right place to discuss this if you don't have a fully fleshed out idea as explained in our contributing guide

@jsenecal commented on GitHub (Aug 17, 2023): Unfortunately @LeDistordu this Feature Request is not really actionnable right as it is right now, even more so with your recent edits. Please make sure your feature request conveys the intent and purpose of such feature and how others could benefit for it and again, perhaps an issue is not the right place to discuss this if you don't have a fully fleshed out idea as explained in our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md#bulb-feature-requests)
adam commented 2025-12-29 20:37:15 +01:00
Author
Owner
Copy Link

@LeDistordu commented on GitHub (Aug 17, 2023):

Hi, ok you can close, i open discussion on forum : https://github.com/netbox-community/netbox/discussions/13492

@LeDistordu commented on GitHub (Aug 17, 2023): Hi, ok you can close, i open discussion on forum : https://github.com/netbox-community/netbox/discussions/13492
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 status: revisions needed 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#8477
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?