starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Speed abbreviation improvement #1086

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

Originally created by @InsaneSplash on GitHub (Jul 10, 2017).

Issue type: request

Python version:
NetBox version:2.0.8

Provide the function to summarise both 1000000 and 1024000 values in human readable form as 1Gbs instead of showing it as 1024Mbs. This would apply to 10Mbs, 100Mbs, 10Gbs.

Originally created by @InsaneSplash on GitHub (Jul 10, 2017). ### Issue type: request **Python version:** **NetBox version:2.0.8** Provide the function to summarise both 1000000 and 1024000 values in human readable form as 1Gbs instead of showing it as 1024Mbs. This would apply to 10Mbs, 100Mbs, 10Gbs.
adam added the type: feature label 2025-12-29 16:28:40 +01:00
adam closed this issue 2025-12-29 16:28:40 +01:00
adam commented 2025-12-29 16:28:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 10, 2017):

FYI line rate is always expressed in bits. 1.024 Gbps is not the same as 1 Gbps.

@jeremystretch commented on GitHub (Jul 10, 2017): FYI line rate is always expressed in bits. 1.024 Gbps is not the same as 1 Gbps.
adam commented 2025-12-29 16:28:41 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 26, 2017):

Throwing my .02 in, this would be very handy...

I would argue though for any data imports, values would need to be provided in bits to simplify the process

@bellwood commented on GitHub (Jul 26, 2017): Throwing my .02 in, this would be very handy... I would argue though for any data imports, values would need to be provided in bits to simplify the process
adam commented 2025-12-29 16:28:41 +01:00
Author
Owner
Copy Link

@ktims commented on GitHub (Jul 26, 2017):

Can I morph this to a request for accepting abbreviations in the input fields (e.g. '1g' or '10g')? Counting zeros (and there are a lot of them) and remembering that it is expecting kbps, not bps or mbps as I would consider more intuitive, is a bit annoying.

Hmm, and now that I think of it, maybe pulling in the speed from the interface type when an interface is selected for a circuit would be nice too. A 10GBASE interface is probably connected at 10G, and deleting one zero if not is preferable to typing 6 of them.

@ktims commented on GitHub (Jul 26, 2017): Can I morph this to a request for accepting abbreviations in the input fields (e.g. '1g' or '10g')? Counting zeros (and there are a lot of them) and remembering that it is expecting kbps, not bps or mbps as I would consider more intuitive, is a bit annoying. Hmm, and now that I think of it, maybe pulling in the speed from the interface type when an interface is selected for a circuit would be nice too. A 10GBASE interface is probably connected at 10G, and deleting one zero if not is preferable to typing 6 of them.
adam commented 2025-12-29 16:28:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 26, 2017):

Can I morph this to a request for accepting abbreviations in the input fields (e.g. '1g' or '10g')?

We should be able to create a custom form field that accepts values like "100m" or "1g" and translates the value to an integer during validation.

Hmm, and now that I think of it, maybe pulling in the speed from the interface type when an interface is selected for a circuit would be nice too.

That might be dangerous. It's common practice to set a 1GE interface to 100 Mbps to effect rate limiting, for example.

@jeremystretch commented on GitHub (Jul 26, 2017): > Can I morph this to a request for accepting abbreviations in the input fields (e.g. '1g' or '10g')? We should be able to create a custom form field that accepts values like "100m" or "1g" and translates the value to an integer during validation. > Hmm, and now that I think of it, maybe pulling in the speed from the interface type when an interface is selected for a circuit would be nice too. That might be dangerous. It's common practice to set a 1GE interface to 100 Mbps to effect rate limiting, for example.
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#1086
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?