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

Connect wireless interfaces in backhaul (PtP) networks #2249

New Issue
Closed
opened 2025-12-29 17:24:06 +01:00 by adam · 2 comments
adam commented 2025-12-29 17:24:06 +01:00
Owner
Copy Link

Originally created by @x-drum on GitHub (Dec 24, 2018).

As stated in #2067 by @jeremystretch:

Interface connections are necessarily limited to one-to-one relationships. Modeling wireless "connections" was never a goal given their typically one-to-many and dynamic nature.

This is a feature request for a new connection type (different from the interface one) in order to document and maintain relations between wireless devices in a backhaul (or PtP) link.

Environment

  • Python version: 3.6.7
  • NetBox version: 2.5.0

Steps to Reproduce

  • Create two wireless devices (every device has at least one IEEE 802.11ac interface, eg: wlan0)
  • Try to connect device A wlan0 to device B wlan0 using the interface connect form,

Expected Behavior

Establish a connection between the two interfaces

Observed Behavior

You are not allowed to connect the two wireless interfaces

Originally created by @x-drum on GitHub (Dec 24, 2018). As stated in #2067 by @jeremystretch: > Interface connections are necessarily limited to one-to-one relationships. Modeling wireless "connections" was never a goal given their typically one-to-many and dynamic nature. This is a feature request for a new connection type (different from the interface one) in order to document and maintain relations between wireless devices in a backhaul (or PtP) link. ### Environment * Python version: 3.6.7 * NetBox version: 2.5.0 ### Steps to Reproduce - Create two wireless devices (every device has at least one IEEE 802.11ac interface, eg: wlan0) - Try to connect device A wlan0 to device B wlan0 using the interface connect form, ### Expected Behavior Establish a connection between the two interfaces ### Observed Behavior You are not allowed to connect the two wireless interfaces
adam added the status: duplicate label 2025-12-29 17:24:06 +01:00
adam closed this issue 2025-12-29 17:24:06 +01:00
adam commented 2025-12-29 17:24:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 28, 2018):

This was already proposed and rejected in #2067.

@jeremystretch commented on GitHub (Dec 28, 2018): This was already proposed and rejected in #2067.
adam commented 2025-12-29 17:24:07 +01:00
Author
Owner
Copy Link

@x-drum commented on GitHub (Jan 3, 2019):

@jeremystretch there will ever be an alternative way to handle this kind of devices/relationship in Netbox?

Take Backhaul/PtP wireless networks as an example, should we give up with this kind of usage scenario or there is a way?.

Thanks and sorry for necrobumping this one.
Regars.

@x-drum commented on GitHub (Jan 3, 2019): @jeremystretch there will ever be an **alternative way** to handle this kind of devices/relationship in Netbox? Take Backhaul/PtP wireless networks as an example, should we give up with this kind of usage scenario or there is a way?. Thanks and sorry for necrobumping this one. Regars.
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
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#2249
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?