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 "Wireless role" (rf_role) field to the InterfaceTemplate model #8330

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

Originally created by @sleepinggenius2 on GitHub (Jul 12, 2023).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.5.6

Feature type

Data model extension

Proposed functionality

I would like to request the ability to set a value for the "Wireless role" (rf_role) field within an interface template and for it to be copied over to the corresponding interface when it is instantiated.

Use case

A lot of wireless interfaces always function as either an "Access point" or "Station" and being able to set that within the interface template would be a huge time savings. I have recently been planning to migrate all of our APs into NetBox and was surprised to see that I was unable to designate their wireless radios with an "Access point" role while modeling the device types. It would seem to me that this has a similar use case to the existing ability to set "PoE mode" in the interface template. As we have over a thousand APs in our network, it seems unnecessarily cumbersome to change that setting on all of the radio interfaces after the devices are instantiated.

Database changes

The rf_role field will need to be implemented on the InterfaceTemplate model, just like it is on the Interface model.

External dependencies

None

Originally created by @sleepinggenius2 on GitHub (Jul 12, 2023). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.5.6 ### Feature type Data model extension ### Proposed functionality I would like to request the ability to set a value for the "Wireless role" (rf_role) field within an interface template and for it to be copied over to the corresponding interface when it is instantiated. ### Use case A lot of wireless interfaces always function as either an "Access point" or "Station" and being able to set that within the interface template would be a huge time savings. I have recently been planning to migrate all of our APs into NetBox and was surprised to see that I was unable to designate their wireless radios with an "Access point" role while modeling the device types. It would seem to me that this has a similar use case to the existing ability to set "PoE mode" in the interface template. As we have over a thousand APs in our network, it seems unnecessarily cumbersome to change that setting on all of the radio interfaces after the devices are instantiated. ### Database changes The `rf_role` field will need to be implemented on the `InterfaceTemplate` model, just like it is on the `Interface` model. ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:35:25 +01:00
adam closed this issue 2025-12-29 20:35:25 +01:00
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: 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#8330
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?