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

This function does not seem to exist: Show assigned IP address(es) of attached interface when viewing a circuit #661 #9555

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

Originally created by @emallette on GitHub (Apr 29, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.6

Python Version

3.8

Steps to Reproduce

  1. Create a circuit
  2. Attach the circuit on both A Side and Z Side to interfaces.
  3. Add an IPv4 address and an IPv6 address on the interface on Side Z.
  4. Note: The IPv4 and IPv6 address show up in the IPAM address list.
  5. Note: Neither the IPv4 or IPv6 address show up associated with the circuit.

Expected Behavior

Based on Issue #661 this function is supposed to be available.

Observed Behavior

There was no noticeable change to the circuit - there doesn't seem to be a place for the IPv4 or IPv6 address to show up along with the circuit.

Originally created by @emallette on GitHub (Apr 29, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.6 ### Python Version 3.8 ### Steps to Reproduce 1. Create a circuit 2. Attach the circuit on both A Side and Z Side to interfaces. 3. Add an IPv4 address and an IPv6 address on the interface on Side Z. 4. Note: The IPv4 and IPv6 address show up in the IPAM address list. 5. Note: Neither the IPv4 or IPv6 address show up associated with the circuit. ### Expected Behavior Based on Issue #661 this function is supposed to be available. ### Observed Behavior There was no noticeable change to the circuit - there doesn't seem to be a place for the IPv4 or IPv6 address to show up along with the circuit.
adam closed this issue 2025-12-29 20:51:23 +01:00
adam commented 2025-12-29 21:18:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 29, 2024):

Please use the feature request template to propose new functionality.

@jeremystretch commented on GitHub (Apr 29, 2024): Please use the [feature request template](https://github.com/netbox-community/netbox/issues/new?assignees=&labels=type%3A+feature%2Cstatus%3A+needs+triage&projects=&template=feature_request.yaml) to propose new functionality.
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#9555
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?