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

Add interface type DECT #9261

New Issue
Closed
opened 2025-12-29 20:47:35 +01:00 by adam · 6 comments
adam commented 2025-12-29 20:47:35 +01:00
Owner
Copy Link

Originally created by @tschmidtb51 on GitHub (Feb 16, 2024).

NetBox version

v3.7.2

Feature type

Data model extension

Proposed functionality

The interface type definition should be extended to allow for DECT interfaces.

Use case

Currently, it is possible represent common DSL routers (e.g. AVM FRITZ!BOX 7590) in Netbox. However, interfaces that use the DECT standard can't be modeled. However, that would be helpful as DECT can be used:

  • for machine-to-machine communication (see DECT-2020, aka NR+)
  • for smart home solutions, including but not limited to switch power sockets
  • for voice transmissions
  • as covered or unexpected channel by an attacker.

To enable the modeling in all of these scenarios (foremost the machine-to-machine communication), Netbox should include a generic value dect.

Database changes

The new value must be inserted in the netbox/dcim/choices.py.

I'm not aware of any other changes.

External dependencies

None.

Originally created by @tschmidtb51 on GitHub (Feb 16, 2024). ### NetBox version v3.7.2 ### Feature type Data model extension ### Proposed functionality The interface type definition should be extended to allow for `DECT` interfaces. ### Use case Currently, it is possible represent common DSL routers (e.g. AVM FRITZ!BOX 7590) in Netbox. However, interfaces that use the [DECT](https://en.wikipedia.org/wiki/Digital_enhanced_cordless_telecommunications) standard can't be modeled. However, that would be helpful as DECT can be used: - for machine-to-machine communication (see DECT-2020, aka NR+) - for smart home solutions, including but not limited to switch power sockets - for voice transmissions - as covered or unexpected channel by an attacker. To enable the modeling in all of these scenarios (foremost the machine-to-machine communication), Netbox should include a generic value `dect`. ### Database changes The new value must be inserted in the `netbox/dcim/choices.py`. I'm not aware of any other changes. ### External dependencies None.
adam added the type: featurepending closurestatus: under reviewcomplexity: low labels 2025-12-29 20:47:35 +01:00
adam closed this issue 2025-12-29 20:47:35 +01:00
adam commented 2025-12-29 20:47:36 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Mar 4, 2024):

Adding a new type in the choices should be sufficient. I could provide a PR, But I'm unsure whether this is a category on its own or part of the existing Wireless / Cellular.

@alehaa commented on GitHub (Mar 4, 2024): Adding a new type in the choices should be sufficient. I could provide a PR, But I'm unsure whether this is a category on its own or part of the existing Wireless / Cellular.
adam commented 2025-12-29 20:47:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2024):

My (admittedly very limited) understanding of DECT is that it is a communications standard rather than an interface type.

@jeremystretch commented on GitHub (Apr 4, 2024): My (admittedly very limited) understanding of DECT is that it is a communications standard rather than an interface type.
adam commented 2025-12-29 20:47:36 +01:00
Author
Owner
Copy Link

@tschmidtb51 commented on GitHub (Apr 4, 2024):

My (admittedly very limited) understanding of DECT is that it is a communications standard rather than an interface type.

I would argue that it is an interface type and communication standard. It support similar features as Wifi/Cellular networks which are listed as interface types.

@tschmidtb51 commented on GitHub (Apr 4, 2024): > My (admittedly very limited) understanding of DECT is that it is a communications standard rather than an interface type. I would argue that it is an interface type and communication standard. It support similar features as Wifi/Cellular networks which are listed as interface types.
adam commented 2025-12-29 20:47:36 +01:00
Author
Owner
Copy Link

@tschmidtb51 commented on GitHub (Apr 4, 2024):

Adding a new type in the choices should be sufficient. I could provide a PR, But I'm unsure whether this is a category on its own or part of the existing Wireless / Cellular.

I that case, I would probably sort it into cellular:

    TYPE_OTHER_WIRELESS = 'other-wireless'

    # Cellular
    TYPE_DECT = 'dect'
    TYPE_GSM = 'gsm'
@tschmidtb51 commented on GitHub (Apr 4, 2024): > Adding a new type in the choices should be sufficient. I could provide a PR, But I'm unsure whether this is a category on its own or part of the existing Wireless / Cellular. I that case, I would probably sort it into cellular: ```suggestion TYPE_OTHER_WIRELESS = 'other-wireless' # Cellular TYPE_DECT = 'dect' TYPE_GSM = 'gsm'
adam commented 2025-12-29 20:47:37 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 21, 2024):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 21, 2024): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:47:37 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 20, 2024):

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 (Sep 20, 2024): 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 complexity: low pending closure status: under review 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#9261
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?