Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Show two-way traceroute with SNR per hop if available #283

Open
GUVWAF opened this issue Aug 29, 2024 · 0 comments
Open
Labels
enhancement New feature or request minor change This is a minor change

Comments

@GUVWAF
Copy link
Member

GUVWAF commented Aug 29, 2024

Description

Since 2.5, when performing a traceroute, nodes will record the SNR per hop, as well as the route back. It would be nice to show this if available. For example, it could show:

1 Hop towards, 2 Hops back
Route towards: You --> Node 1 (-10.75dB) --> Node 2 (-5.25dB)
Route back:    Node 2  --> Node 3 (-2dB) --> Node 1 (-1.5dB) --> You (-8dB)

Since old firmware won’t add the SNR and the route back, there is some validation needed. For the SNR to be valid, the SNR list should be one longer than the route list (because the destination adds SNR as well). For the route back to be valid, also hopStart needs to be populated, because only then nodes can add unknown nodes and SNR. Unknown SNR is represented by the value -128 and unknown nodes by 0xFFFFFFFF (4294967295). The SNR values are in dB, but they are scaled by 4, so it has to be divided by 4 before showing it. A reference implementation in Python can be found here.

@GUVWAF GUVWAF added the enhancement New feature or request label Aug 29, 2024
@Hunter275 Hunter275 added the minor change This is a minor change label Aug 29, 2024
@Hunter275 Hunter275 added bug Something isn't working and removed bug Something isn't working labels Sep 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request minor change This is a minor change
Projects
None yet
Development

No branches or pull requests

2 participants