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

Add MoCA (coaxial) Interface Type #10952

New Issue
Closed
opened 2025-12-29 21:38:15 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:38:15 +01:00
Owner
Copy Link

Originally created by @ZPrimed on GitHub (Mar 27, 2025).

Originally assigned to: @ZPrimed on GitHub.

NetBox version

v4.2.6

Feature type

Data model extension

Proposed functionality

I am raising this FR to ask for a new coaxial "interface type" for MoCA (Wikipedia link).

I am unsure as to whether the project would prefer to break out the specific MoCA "version" as multiple types? Different versions of MoCA do have different rated interface throughput as well as limitations around simultaneous clients, so that would be an argument for multiple type options. However, the existing "DOCSIS" interface type currently doesn't get split out by version of DOCSIS, even though there are a bunch of those. So, following existing style / KISS would imply a single "MoCA" type.

I'd be willing to make an attempt at the PR to add MoCA (it would be my first PR to NetBox) if I can get clarification on whether each different MoCA revision (1.0, 1.1, 2.0, 2.5, 3.0) belongs in the list separately, or not. AIUI, the only changes would be a few lines added in netbox/dcim/choices.py?

(I would think that if the different MoCA revisions are broken out as different types, then DOCSIS should also have similar types added for consistency, but it's unclear to me what should happen with the old "vanilla" DOCSIS type at that point...)

Use case

Real world example of ISP/telco-type hardware that uses this interface: InCoax in:xtnd Control C25x series, this is one example from one vendor, but I know there are others. These systems exist as a way to re-use existing coax/CATV plant to distribute higher-speed service, typically in an apartment/MDU-type scenario.

Database changes

None required to my knowledge

External dependencies

n/a

Originally created by @ZPrimed on GitHub (Mar 27, 2025). Originally assigned to: @ZPrimed on GitHub. ### NetBox version v4.2.6 ### Feature type Data model extension ### Proposed functionality I am raising this FR to ask for a new coaxial "interface type" for [MoCA](https://en.wikipedia.org/wiki/Multimedia_over_Coax_Alliance) (Wikipedia link). I am unsure as to whether the project would prefer to break out the specific MoCA "version" as multiple types? Different versions of MoCA _do_ have different rated interface throughput as well as limitations around simultaneous clients, so that would be an argument for multiple type options. **However**, the existing "DOCSIS" interface type currently doesn't get split out by version of DOCSIS, even though there are a bunch of those. So, following existing style / KISS would imply a single "MoCA" type. I'd be willing to make an attempt at the PR to add MoCA (it would be my first PR to NetBox) if I can get clarification on whether each different MoCA revision (1.0, 1.1, 2.0, 2.5, 3.0) belongs in the list separately, or not. AIUI, the only changes would be a few lines added in `netbox/dcim/choices.py`? (I would think that _if_ the different MoCA revisions are broken out as different types, then DOCSIS should _also_ have similar types added for consistency, but it's unclear to me what should happen with the old "vanilla" DOCSIS type at that point...) ### Use case Real world example of ISP/telco-type hardware that uses this interface: [InCoax in:xtnd Control C25x series](https://www.incoax.com/products/), this is one example from one vendor, but I know there are others. These systems exist as a way to re-use existing coax/CATV plant to distribute higher-speed service, typically in an apartment/MDU-type scenario. ### Database changes None required to my knowledge ### External dependencies n/a
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:38:15 +01:00
adam closed this issue 2025-12-29 21:38:15 +01:00
adam commented 2025-12-29 21:38:16 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Mar 27, 2025):

An umbrella option for MoCA seems reasonable, like DOCSIS, without breaking it out in to the specific versions.

Assigning to you, @ZPrimed !

@jnovinger commented on GitHub (Mar 27, 2025): An umbrella option for MoCA seems reasonable, like DOCSIS, without breaking it out in to the specific versions. Assigning to you, @ZPrimed !
adam commented 2025-12-29 21:38:16 +01:00
Author
Owner
Copy Link

@ZPrimed commented on GitHub (Mar 27, 2025):

Thanks @jnovinger - PR 19028 created and ready for review!

@ZPrimed commented on GitHub (Mar 27, 2025): Thanks @jnovinger - [PR 19028 created](https://github.com/netbox-community/netbox/pull/19028) and ready for review!
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 status: accepted 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#10952
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?