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

Toggle option: IP address: Direct link / Netbox link #3662

New Issue
Closed
opened 2025-12-29 18:30:26 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:30:26 +01:00
Owner
Copy Link

Originally created by @arnoudrut on GitHub (May 9, 2020).

Environment

  • Python version: v3.6.9
  • NetBox version: v2.6.11

Proposed Functionality

When toggled ON, clicking a device's IP address, under interfaces, would open a tab, browsing to the IP address, instead of opening the IP address's Netbox page.

Use Case

Useful to have 'turned on' in practical cases, like in case of a server crash, to easily jump from looking up the internal IP address to actually connecting to the device's browser based Remote Access window.
As it would be proposed to be a toggle, current use wouldn't be affected.

Database Changes

No, there's no need for any database changes to add this functionality.

External Dependencies

Originally created by @arnoudrut on GitHub (May 9, 2020). ### Environment * Python version: v3.6.9 * NetBox version: v2.6.11 ### Proposed Functionality When toggled ON, clicking a device's IP address, under interfaces, would open a tab, browsing to the IP address, instead of opening the IP address's Netbox page. ### Use Case Useful to have 'turned on' in practical cases, like in case of a server crash, to easily jump from looking up the internal IP address to actually connecting to the device's browser based Remote Access window. As it would be proposed to be a toggle, current use wouldn't be affected. ### Database Changes No, there's no need for any database changes to add this functionality. ### External Dependencies
adam closed this issue 2025-12-29 18:30:26 +01:00
adam commented 2025-12-29 18:30:26 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (May 11, 2020):

I think this is a slippery-slope to a whole set of link behaviors that will be specific to one or another use case.
Maybe you want to resort to the Netbox Smart Links? They can lookup any property from the model displayed (like mgmt IP of a device) and build a link to that. We use that to generate SSH and HTTPS links to a device mgmt IP.

In any case, this won't get accepted as a feature request in the current form. A new FR to 'display interface -level smart links within the device GUI' could be attempted (assuming smart links are already available on interface level anyway)

Edit: there are no interface level smart links ATM. To get the functionality you want 2 FRs would need to be created:

  1. Interface level smart links
  2. Render interface smart links in device interface table
@sdktr commented on GitHub (May 11, 2020): I think this is a slippery-slope to a whole set of link behaviors that will be specific to one or another use case. Maybe you want to resort to the Netbox Smart Links? They can lookup any property from the model displayed (like mgmt IP of a device) and build a link to that. We use that to generate SSH and HTTPS links to a device mgmt IP. In any case, this won't get accepted as a feature request in the current form. A new FR to 'display _interface_ -level smart links within the _device_ GUI' could be attempted (assuming smart links are already available on interface level anyway) Edit: there are no interface level smart links ATM. To get the functionality you want 2 FRs would need to be created: 1) Interface level smart links 2) Render interface smart links in device interface table
adam commented 2025-12-29 18:30:26 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (May 11, 2020):

OR: you can create a smart link on the device level that points to the IP-address of a(fixed) interface name for the link destination.

Someone with more intimate knowledge of the model can propably help out with that on the mailinglist, I guess a syntax like the below could work:

{{ obj.interface['IPMI'].ip_address[0] }}

@sdktr commented on GitHub (May 11, 2020): OR: you can create a smart link on the device level that points to the IP-address of a(fixed) interface name for the link destination. Someone with more intimate knowledge of the model can propably help out with that on the mailinglist, I guess a syntax like the below _could_ work: `{{ obj.interface['IPMI'].ip_address[0] }}`
adam commented 2025-12-29 18:30:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 11, 2020):

As @sdktr points out, this is precisely the time of use case custom links were introduced to address.

@jeremystretch commented on GitHub (May 11, 2020): As @sdktr points out, this is precisely the time of use case [custom links](https://netbox.readthedocs.io/en/stable/additional-features/custom-links/) were introduced to address.
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#3662
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?