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

Extend supported Parent Types for Services to include IPAM > IP Addresses #11346

New Issue
Closed
opened 2025-12-29 21:43:58 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:43:58 +01:00
Owner
Copy Link

Originally created by @rboucher-me on GitHub (Jul 3, 2025).

NetBox version

v4.3.3

Feature type

Change to existing functionality

Proposed functionality

This request is to extend the currently supported Parent Types for Services to support IPAM > IP Addresses. Currently, the following Parent Types are supported:

Image

Use case

This capability would allow results from network port scans (from tools such as Nmap) to be modelled in NetBox by associating the active IP Addresses to the discovered open ports ("Services"). Currently, these associations require a parent Device (or FHRP Group, or VM) and don't allow modelling of services for all active IP Addresses.

Database changes

No identified database changes.

External dependencies

No identified external dependencies

Originally created by @rboucher-me on GitHub (Jul 3, 2025). ### NetBox version v4.3.3 ### Feature type Change to existing functionality ### Proposed functionality This request is to extend the currently supported Parent Types for Services to support IPAM > IP Addresses. Currently, the following Parent Types are supported: ![Image](https://github.com/user-attachments/assets/5253bbc4-da03-4bc2-bb4b-55abaed480b7) ### Use case This capability would allow results from network port scans (from tools such as Nmap) to be modelled in NetBox by associating the active IP Addresses to the discovered open ports ("Services"). Currently, these associations require a parent Device (or FHRP Group, or VM) and don't allow modelling of services for all active IP Addresses. ### Database changes No identified database changes. ### External dependencies No identified external dependencies
adam added the type: feature label 2025-12-29 21:43:58 +01:00
adam closed this issue 2025-12-29 21:43:58 +01:00
adam commented 2025-12-29 21:43:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 10, 2025):

Closing per our discussion earlier; we'll explore alternative approaches for the use case.

@jeremystretch commented on GitHub (Jul 10, 2025): Closing per our discussion earlier; we'll explore alternative approaches for the use case.
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 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#11346
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?