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

Include endpoint sites in wireless links table #6176

New Issue
Closed
opened 2025-12-29 19:37:43 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:37:43 +01:00
Owner
Copy Link

Originally created by @michael-edobor on GitHub (Mar 6, 2022).

NetBox version

v3.1.8

Feature type

Change to existing functionality

Proposed functionality

This is somewhat similar to #8664 but for wireless links.

I modified the HTML page in my browser to help explain the required functionality. Images below represent proposed functionality detailing what is presently non-existent within netbox

  1. Under the https://{server_ip}/wireless/wireless-links/ page, users should be able to filter wireless links by the sites. See image below.
image
  1. Additionally, the wireless links count should also be viewed from the https://{server_ip}/dcim/sites/{site.id}/ page for each site :
image
  1. Introduction of wireless links count may also affect the UI on 'https://{server_ip}/wireless/wireless-links/{wireless_link.id}/' page . However, an introduction of a 'site' field in the base UI requires calling the site parameter on the device object. Since devices will typically be found in sites so the site field will always reference on the assigned site for the 'device a' or 'device b' with the respective 'interface'.

Use case

This will greatly aid users who document a number of wireless links on netbox. Especially folks in the ISP/Telco Space. This will be helpful to mostly people to easily tell the physical points of wireless 'links' at a particular site from either ends (A or B).

When an operator has a long list of wireless links, it becomes difficult to sort or even export the data due to the interface or device reference. Implementing this will definitely make documentation of wireless links/connections easier.

Database changes

No response

External dependencies

No response

Originally created by @michael-edobor on GitHub (Mar 6, 2022). ### NetBox version v3.1.8 ### Feature type Change to existing functionality ### Proposed functionality This is somewhat similar to [#8664](https://github.com/netbox-community/netbox/issues/8664) but for wireless links. I modified the HTML page in my browser to help explain the required functionality. Images below represent proposed functionality detailing what is presently non-existent within netbox 1. Under the https://{server_ip}/wireless/wireless-links/ page, users should be able to filter wireless links by the sites. See image below. <img width="525" alt="image" src="https://user-images.githubusercontent.com/97886385/156941781-44d150f5-615f-40a9-951c-3de9651923f3.png"> 2. Additionally, the wireless links count should also be viewed from the https://{server_ip}/dcim/sites/{site.id}/ page for each site : <img width="754" alt="image" src="https://user-images.githubusercontent.com/97886385/156942205-b7efbcb7-7f2b-497f-ae13-0ed195c1c4f9.png"> 3. Introduction of wireless links count may also affect the UI on 'https://{server_ip}/wireless/wireless-links/{wireless_link.id}/' page . However, an introduction of a 'site' field in the base UI requires calling the site parameter on the device object. Since devices will typically be found in sites so the site field will always reference on the assigned site for the 'device a' or 'device b' with the respective 'interface'. ### Use case This will greatly aid users who document a number of wireless links on netbox. Especially folks in the ISP/Telco Space. This will be helpful to mostly people to easily tell the physical points of wireless 'links' at a particular site from either ends (A or B). When an operator has a long list of wireless links, it becomes difficult to sort or even export the data due to the interface or device reference. Implementing this will definitely make documentation of wireless links/connections easier. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:37:43 +01:00
adam closed this issue 2025-12-29 19:37:45 +01:00
adam commented 2025-12-29 19:37:45 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 6, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 6, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:37:45 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 6, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jul 6, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#6176
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?