Increase rf_channel_frequency Precision to 3 Decimal Places #157

New Issue

MrUnknownDE · 2026-04-05T16:22:25+02:00

MrUnknownDE commented

2026-04-05 16:22:25 +02:00

Originally created by @AnythingOverIP on 3/12/2026

NetBox version

4.5.4

Feature type

Change to existing functionality

Proposed functionality

Enhance the rf_channel_frequency field on the Interface model to support three (3) decimal places of precision instead of the current two (2), allowing frequencies such as 5900.125 MHz or 928.750 MHz to be represented accurately.

This would change the model definition from: rf_channel_frequency = models.DecimalField(max_digits=7, decimal_places=2, ...) to: rf_channel_frequency = models.DecimalField(max_digits=7, decimal_places=3, ...)

This change would allow more accurate representation of center frequencies for wireless point‑to‑point (P2P) links, particularly in regions where licensing authorities specify sub‑MHz precision requirements.

Use case

In Canada, as in mulitple other countries, ISED (Innovation, Science and Economic Development, the FCC equivalent here) requires three‑digit frequency resolution for licensed wireless P2P links. Operators must configure, document, and maintain frequencies with 0.001 MHz (1 kHz) granularity to meet regulatory and coordination requirements.
Today, NetBox restricts frequency precision to only two decimal places because rf_channel_frequency is implemented as a DecimalField with decimal_places=2 in the core model. This prevents accurate modeling of licensed microwave or sub‑GHz P2P links where center frequencies frequently require kHz‑level precision.

Accurate modeling is essential for:

Documenting licensed P2P links that must be coordinated with ISED
Avoiding regulatory mismatches that could lead to audit issues
Ensuring consistent datasets shared with engineering, NMS exports, or coordination tools
Maintaining clean end‑to‑end design data used for frequency planning

Given that NetBox already supports P2P modeling through wireless interfaces and wireless links, expanding the precision of rf_channel_frequency would make NetBox usable for real‑world licensed microwave deployments.

Proposed Implementation

Update the rf_channel_frequency field on the Interface model to decimal_places=3.
Apply the same change to any related serializers, forms, and API validations.
Run a schema migration for the change.

This should be a low‑impact update, as the field already stores numeric values and increasing precision does not break existing data.

Database changes

n/a

External dependencies

n/a

*Originally created by @AnythingOverIP on 3/12/2026* ### NetBox version 4.5.4 ### Feature type Change to existing functionality ### Proposed functionality Enhance the rf_channel_frequency field on the Interface model to support three (3) decimal places of precision instead of the current two (2), allowing frequencies such as 5900.125 MHz or 928.750 MHz to be represented accurately. This would change the model definition from: `rf_channel_frequency = models.DecimalField(max_digits=7, decimal_places=2, ...)` to: `rf_channel_frequency = models.DecimalField(max_digits=7, decimal_places=3, ...)` This change would allow more accurate representation of center frequencies for wireless point‑to‑point (P2P) links, particularly in regions where licensing authorities specify sub‑MHz precision requirements. ### Use case In Canada, as in mulitple other countries, ISED (Innovation, Science and Economic Development, the FCC equivalent here) requires three‑digit frequency resolution for licensed wireless P2P links. Operators must configure, document, and maintain frequencies with 0.001 MHz (1 kHz) granularity to meet regulatory and coordination requirements. Today, NetBox restricts frequency precision to only two decimal places because rf_channel_frequency is implemented as a DecimalField with decimal_places=2 in the core model. This prevents accurate modeling of licensed microwave or sub‑GHz P2P links where center frequencies frequently require kHz‑level precision. Accurate modeling is essential for: - Documenting licensed P2P links that must be coordinated with ISED - Avoiding regulatory mismatches that could lead to audit issues - Ensuring consistent datasets shared with engineering, NMS exports, or coordination tools - Maintaining clean end‑to‑end design data used for frequency planning Given that NetBox already supports P2P modeling through wireless interfaces and wireless links, expanding the precision of rf_channel_frequency would make NetBox usable for real‑world licensed microwave deployments. **Proposed Implementation** - Update the rf_channel_frequency field on the Interface model to decimal_places=3. - Apply the same change to any related serializers, forms, and API validations. - Run a schema migration for the change. This should be a low‑impact update, as the field already stores numeric values and increasing precision does not break existing data. ### Database changes n/a ### External dependencies n/a

MrUnknownDE closed this issue

2026-04-05 16:22:25 +02:00

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: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low complexity: low netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox 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: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted status: accepted type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature 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#157