starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Bring back GraphQL reverse search for IP-Addresses based on device #11672

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

Originally created by @dxks on GitHub (Oct 2, 2025).

NetBox version

v4.4.2

Feature type

Data model extension

Proposed functionality

With NetBox 4.2 it was possible to perform a graphql query to retrieve all IP-Addresses that belongs in any kind to a device:

query { ip_address_list(filters:{device_id:"4711"}) { id address }}

Unfortunately with the new Filtering this option has gone and now only a forward search over interfaces and services and manually combining it is possible as there cannot be build a relationship in the filters between an ip address and a device. The REST API still works but with no chance to add additional data in the query, i.e. services or nat bound to that ip.

Use case

Retrieve all ip addresses for a device and define the retrieved data and further relationships.

Database changes

No response

External dependencies

No response

Originally created by @dxks on GitHub (Oct 2, 2025). ### NetBox version v4.4.2 ### Feature type Data model extension ### Proposed functionality With NetBox 4.2 it was possible to perform a graphql query to retrieve all IP-Addresses that belongs in any kind to a device: `query { ip_address_list(filters:{device_id:"4711"}) { id address }}` Unfortunately with the new Filtering this option has gone and now only a forward search over interfaces and services and manually combining it is possible as there cannot be build a relationship in the filters between an ip address and a device. The REST API still works but with no chance to add additional data in the query, i.e. services or nat bound to that ip. ### Use case Retrieve all ip addresses for a device and define the retrieved data and further relationships. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurenetboxtopic: GraphQL labels 2025-12-29 21:48:20 +01:00
adam closed this issue 2025-12-29 21:48:20 +01:00
adam commented 2025-12-29 21:48:21 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 2, 2025):

For the moment, you can query through the device relationship to get all IP addresses:

query {
  device(id: 4711) {
    interfaces {
      ip_addresses {
        id
        address
        # Additional fields as needed
      }
    }
    services {
      ipaddresses {
        id
        address
      }
    }
  }
}

This requires client-side flattening but should get you all IPs for a device.

@jnovinger commented on GitHub (Oct 2, 2025): For the moment, you can query through the device relationship to get all IP addresses: ```graphql query { device(id: 4711) { interfaces { ip_addresses { id address # Additional fields as needed } } services { ipaddresses { id address } } } } ``` This requires client-side flattening but should get you all IPs for a device.
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 topic: GraphQL 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#11672
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?