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 RF connectors #1034

New Issue
Closed
opened 2025-12-29 16:28:09 +01:00 by adam · 6 comments
adam commented 2025-12-29 16:28:09 +01:00
Owner
Copy Link

Originally created by @fogtea on GitHub (Jun 14, 2017).

I work in the 2-way radio industry and would to to see if its possible to add a connection type of RF into netbox. A lot of radios are computers with radios in them, so they have the standard connection types with the addition of a coax connection.

Originally created by @fogtea on GitHub (Jun 14, 2017). I work in the 2-way radio industry and would to to see if its possible to add a connection type of RF into netbox. A lot of radios are computers with radios in them, so they have the standard connection types with the addition of a coax connection.
adam added the type: feature label 2025-12-29 16:28:09 +01:00
adam closed this issue 2025-12-29 16:28:09 +01:00
adam commented 2025-12-29 16:28:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 14, 2017):

What interface types are you proposing be added? Please list the exact names.

@jeremystretch commented on GitHub (Jun 14, 2017): What interface types are you proposing be added? Please list the exact names.
adam commented 2025-12-29 16:28:09 +01:00
Author
Owner
Copy Link

@fogtea commented on GitHub (Jun 14, 2017):

For now, just a separate connector type that says RF, something i can add to a device type instead of interface,console, and power. I dont how important connector types are for netbox, but a few to start with are:
Type-N
BNC
PL-259 (UHF)

Thank you for the immediate follow up!

@fogtea commented on GitHub (Jun 14, 2017): For now, just a separate connector type that says RF, something i can add to a device type instead of interface,console, and power. I dont how important connector types are for netbox, but a few to start with are: Type-N BNC PL-259 (UHF) Thank you for the immediate follow up!
adam commented 2025-12-29 16:28:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 16, 2017):

What are these interfaces used for? NetBox is primarily an IPAM/DCIM application; if they're not used for networking I'm not sure it makes sense to add them.

@jeremystretch commented on GitHub (Jun 16, 2017): What are these interfaces used for? NetBox is primarily an IPAM/DCIM application; if they're not used for networking I'm not sure it makes sense to add them.
adam commented 2025-12-29 16:28:10 +01:00
Author
Owner
Copy Link

@fogtea commented on GitHub (Jun 16, 2017):

Jeremy,

Thank you very much for following up with this!
A radio repeater is basically a server and very much needs to be part of DCIM and IPAM. We have racks of radios all serving different purposes. They can be 1U-4U and have all the connections of a regular server with the addition of a coax. The coax can route directly to an antenna or a multitude of other components like multicouplers, combiners, and duplexors (Rackable radio gear). Think of a device that has 8 coax connections in and 1 coax connection out. Adding coax will give me/users the ability to track/trace where coax lines go given netboxes awesome connecting capability in the web interface. Much like how I can connect server X interface ge/0/0/1 to Switch Y port fe/0/01, Id like the ability to do the same with coax. Radio X, interface coax 1 connects to combiner Y port coax 1. I hope that paints a picture. I know beggars cant be choosers, but so far netbox has been the best solution we have come across. Thank you again!

@fogtea commented on GitHub (Jun 16, 2017): Jeremy, Thank you very much for following up with this! A radio repeater is basically a server and very much needs to be part of DCIM and IPAM. We have racks of radios all serving different purposes. They can be 1U-4U and have all the connections of a regular server with the addition of a coax. The coax can route directly to an antenna or a multitude of other components like multicouplers, combiners, and duplexors (Rackable radio gear). Think of a device that has 8 coax connections in and 1 coax connection out. Adding coax will give me/users the ability to track/trace where coax lines go given netboxes awesome connecting capability in the web interface. Much like how I can connect server X interface ge/0/0/1 to Switch Y port fe/0/01, Id like the ability to do the same with coax. Radio X, interface coax 1 connects to combiner Y port coax 1. I hope that paints a picture. I know beggars cant be choosers, but so far netbox has been the best solution we have come across. Thank you again!
adam commented 2025-12-29 16:28:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 16, 2017):

@fogtea I'm referring specifically to the radio interfaces. It doesn't sound like they could be reasonably classified as data network interfaces, so it wouldn't make sense to add them as options for interface type. Afraid I have to reject this request.

I understand there's value in documenting these connections, but NetBox doesn't currently have a model which would support it. You might be interested in #968, which would potentially introduce a mechanism for adding arbitrary connections such as these. I invite you to document your use case there and give it a 👍

@jeremystretch commented on GitHub (Jun 16, 2017): @fogtea I'm referring specifically to the radio interfaces. It doesn't sound like they could be reasonably classified as data network interfaces, so it wouldn't make sense to add them as options for interface type. Afraid I have to reject this request. I understand there's value in documenting these connections, but NetBox doesn't currently have a model which would support it. You might be interested in #968, which would potentially introduce a mechanism for adding arbitrary connections such as these. I invite you to document your use case there and give it a :+1:
adam commented 2025-12-29 16:28:10 +01:00
Author
Owner
Copy Link

@runeka commented on GitHub (Jan 24, 2019):

I am in the media industry. The entire industry is moving away from SDI-router (BNC connetor) to IP. In the transition period (10 years) before all connected equipment has native ethernet we will be using SFPs that convert the SDI videoflow to a 12Gbps (4K) ip multicast stream. The SFPs have 2xBNC connectors on them. We will build a high bandwidth DC network based on this.
https://www.embrionix.com/product/family/video-sfp-coaxial
The other end of that coax BNC cable will be connected to a device with a BNC interface.
I would like to be able to add BNC interfaces.
I see that this is not relevant for everyone. Custom field for interface types would probably be the best option for users. Personally I would like to ba able to remove Sonet and Serial interfaces.
As it is now we will just use the Other option, and that will work.
Custom fields for cable type would also be great. We use coax, but we never use CAT3.

@runeka commented on GitHub (Jan 24, 2019): I am in the media industry. The entire industry is moving away from SDI-router (BNC connetor) to IP. In the transition period (10 years) before all connected equipment has native ethernet we will be using SFPs that convert the SDI videoflow to a 12Gbps (4K) ip multicast stream. The SFPs have 2xBNC connectors on them. We will build a high bandwidth DC network based on this. https://www.embrionix.com/product/family/video-sfp-coaxial The other end of that coax BNC cable will be connected to a device with a BNC interface. I would like to be able to add BNC interfaces. I see that this is not relevant for everyone. Custom field for interface types would probably be the best option for users. Personally I would like to ba able to remove Sonet and Serial interfaces. As it is now we will just use the Other option, and that will work. Custom fields for cable type would also be great. We use coax, but we never use CAT3.
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 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#1034
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?