-
-
Notifications
You must be signed in to change notification settings - Fork 206
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]: Rearrange traceroute result and add some differentiating colour #1207
Comments
Hey @b8b8, maybe it would be good to consider here how traceroute in 2.5 is going to look like in general. Apart from the SNR per hop, we can also get a two-way traceroute result. There is some validation needed, because it depends on the firmware of the nodes in the route whether the info is accurate or not. I opened a PR for the Python CLI (meshtastic/python#654) to accommodate for this; basically the length of the list of SNRs should be 1 longer than the route list and nodes and SNR can be unknown (represented by Maybe it can look something like this then (excuse me for my Paint skills): Not sure how feasible all of this is, but it would be cool to show it like this :) |
Dude this looks even better. |
Is there any possibility to add timestamps to each hop? And/or how many attempts it took to make each hop? Could be useful for assessing where you need better coverage. |
I've already mentioned it in the discord, but apparently not asked for it as a feature request. Putting the results in the chat history for a node would solve some of the things people have asked for above |
yea, how about the pop-up, but then also the pop-up results end up saved in the appropriate DM with text of all the info people are asking for. Pop just shows info GUVWAF posted. DM has all this plus any other info like timing as text. |
Yep. They're a bit ephemeral at the minute, even if they succeed after you switch tabs they're lost. |
No, those are not sent over LoRa. It would also be hard to get valuable info from them, because each node uses random delays before transmitting and they might have other packets in their queue. Also nodes are not time-synchronized, at least not with second-level accuracy.
Intermediate hops only ever try once. If the signal quality is strong and the traceroute fails, it's likely a packet collision. |
the traceroute dialog message takes a |
Contact Details
No response
Tell us your idea.
My suggestion is to have the traceroutes present vertically and with different colours for hops, transmit, and receive. Also including the hopping SNR would be beneficial.
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: