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

Wireless links: one to many interface support #8972

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

Originally created by @jdreichmann on GitHub (Dec 15, 2023).

NetBox version

v3.6.6

Feature type

Change to existing functionality

Proposed functionality

Currently, wireless interfaces can only be connected using wireless links which are 1:1. The proposal is to change this to 1:n, where a wireless interface with "Access point" status can be connected with many interfaces which have a (new?) type of "Client".

(see https://demo.netbox.dev/static/docs/core-functionality/wireless/#wireless-links "A wireless link represents a connection between exactly two wireless interfaces")

Use case

This allows modelling "those devices are connected to this wifi/access point".

Database changes

No response

External dependencies

No response

Originally created by @jdreichmann on GitHub (Dec 15, 2023). ### NetBox version v3.6.6 ### Feature type Change to existing functionality ### Proposed functionality Currently, wireless interfaces can only be connected using wireless links which are 1:1. The proposal is to change this to 1:n, where a wireless interface with "Access point" status can be connected with many interfaces which have a (new?) type of "Client". (see https://demo.netbox.dev/static/docs/core-functionality/wireless/#wireless-links "A wireless link represents a connection between exactly two wireless interfaces") ### Use case This allows modelling "those devices are connected to this wifi/access point". ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 20:43:31 +01:00
adam closed this issue 2025-12-29 20:43:31 +01:00
adam commented 2025-12-29 20:43:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 15, 2023):

This seems like it would be covered by #9641, so I'm going to close this out as a duplicate. @jdreichmann please feel free to tack on any of your additional requirements or considerations to the other issue.

@jeremystretch commented on GitHub (Dec 15, 2023): This seems like it would be covered by #9641, so I'm going to close this out as a duplicate. @jdreichmann please feel free to tack on any of your additional requirements or considerations to the other issue.
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 status: duplicate 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#8972
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?