Allow circuit terminations on wireless interfaces using wireless links #1348

New Issue

MrUnknownDE · 2026-04-05T23:47:53+02:00

MrUnknownDE commented

2026-04-05 23:47:53 +02:00

Originally created by @kate-james on 9/2/2025

NetBox version

v4.3.2

Feature type

Change to existing functionality

Proposed functionality

Core Change: Extend the existing wireless_links model to support circuit terminations on wireless interfaces, enabling logical connectivity tracking for cellular and other wireless circuits.

Specific Implementation:

Wireless Link Model Enhancement:
- Modify the wireless_links model to accept multiple types of termination (Circuit, and Interface)
- Add support for connecting cellular circuits to wireless interfaces (similar to how cables terminate wired circuits to physical interfaces)
- Maintain existing wireless link functionality for point-to-point interface based wireless connections
Circuit Type Model Enhancement:
- Add a connection_type field to the CircuitType model with choices: Wired and Wireless
- This field determines whether a circuit can terminate to physical ports (via cables) or wireless interfaces (via wireless links)
- Default to Wired for backward compatibility

Use case

Cellular circuits need to be tracked, just as wired circuits. This includes cellular WAN backup connections, IoT device connectivity, and mobile infrastructure circuits that have service provider relationships, billing, and SLA requirements identical to wired circuits.

When using a private APN the logical topology is identical to a wired circuit and modelling capabilities should reflect this.

As discussed in issues #19687 and #20218, the recent model changes removed this capability, and has impacted myself, @ross-cello, @itskeoo, and @denjs enough to step in and raise issues for this.

Workflow Example:

User creates a Circuit with where the CircuitType has connection_type=Wireless
User navigates to a device with a cellular interface
User can terminate the wireless circuit to the cellular interface via the wireless link mechanism

Database changes

CircuitType Model:

Add connection_type field with choices: Wired (default), Wireless
Migration to set all existing circuit types to Wired for backward compatibility

WirelessLink Model:

Modify termination logic to support multiple object types (Circuit and Interface)
Add generic foreign key relationships or extend existing termination fields to handle circuit connections
Maintain existing interface-to-interface wireless link functionality

Validations:

Add restriction to prevent Wired circuits from connecting via wireless links
Add restriction to prevent Wireless circuits from connecting via cables
Ensure circuits can use only one connection method (mutual exclusivity between cable and wireless link terminations)

External dependencies

No response

*Originally created by @kate-james on 9/2/2025* ### NetBox version v4.3.2 ### Feature type Change to existing functionality ### Proposed functionality **Core Change:** Extend the existing `wireless_links` model to support circuit terminations on wireless interfaces, enabling logical connectivity tracking for cellular and other wireless circuits. **Specific Implementation:** 1. **Wireless Link Model Enhancement:** - Modify the `wireless_links` model to accept multiple types of termination (Circuit, and Interface) - Add support for connecting cellular circuits to wireless interfaces (similar to how cables terminate wired circuits to physical interfaces) - Maintain existing wireless link functionality for point-to-point interface based wireless connections 2. **Circuit Type Model Enhancement:** - Add a `connection_type` field to the CircuitType model with choices: `Wired` and `Wireless` - This field determines whether a circuit can terminate to physical ports (via cables) or wireless interfaces (via wireless links) - Default to `Wired` for backward compatibility ### Use case Cellular circuits need to be tracked, just as wired circuits. This includes cellular WAN backup connections, IoT device connectivity, and mobile infrastructure circuits that have service provider relationships, billing, and SLA requirements identical to wired circuits. When using a private APN the logical topology is identical to a wired circuit and modelling capabilities should reflect this. As discussed in issues #19687 and #20218, the recent model changes removed this capability, and has impacted myself, @ross-cello, @itskeoo, and @denjs enough to step in and raise issues for this. **Workflow Example:** 1. User creates a Circuit with where the CircuitType has `connection_type=Wireless` 2. User navigates to a device with a cellular interface 3. User can terminate the wireless circuit to the cellular interface via the wireless link mechanism <img width="768" height="437" alt="Image" src="https://github.com/user-attachments/assets/3004f9b7-df8d-404d-9584-c377e8d64b35" /> ### Database changes **CircuitType Model:** - Add `connection_type` field with choices: `Wired` (default), `Wireless` - Migration to set all existing circuit types to `Wired` for backward compatibility **WirelessLink Model:** - Modify termination logic to support multiple object types (Circuit and Interface) - Add generic foreign key relationships or extend existing termination fields to handle circuit connections - Maintain existing interface-to-interface wireless link functionality **Validations:** - Add restriction to prevent `Wired` circuits from connecting via wireless links - Add restriction to prevent `Wireless` circuits from connecting via cables - Ensure circuits can use only one connection method (mutual exclusivity between cable and wireless link terminations) ### External dependencies _No response_

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high complexity: high netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog status: backlog type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1348