Traceroute returns swap source and destination nodes #33

New Issue

2026-10-05T06:02:54+02:00

adam commented

2026-10-05 06:02:54 +02:00

Meshview v3.0.0, when running traceroutes I am seeing that the return path has the source and destination nodes reversed, and the incorrect paths are reflected on the node graph as well.

All the nodes in between appear to be correctly linked it's just swapping source and destination in its logic.

Ex: Hi8 is direct to FB and woof is direct to PGlf but they're swapped in this graph.

https://map.wpamesh.net/graph/traceroute/825294159

Meshview v3.0.0, when running traceroutes I am seeing that the return path has the source and destination nodes reversed, and the incorrect paths are reflected on the node graph as well. All the nodes in between appear to be correctly linked it's just swapping source and destination in its logic. Ex: Hi8 is direct to FB and woof is direct to PGlf but they're swapped in this graph. https://map.wpamesh.net/graph/traceroute/825294159

adam commented

2026-10-05 06:02:55 +02:00

Thank you for the report. I will look into it.

Thank you for the report. I will look into it.

adam commented

2026-10-05 06:02:56 +02:00

I validated I see the same behavior. Thank you. Will keep you posted

I validated I see the same behavior. Thank you. Will keep you posted

adam commented

2026-10-05 06:02:56 +02:00

Same here, I guess it's also a cause why there are no destination boxes in traceroute graphs

Same here, I guess it's also a cause why there are no destination boxes in traceroute graphs

adam commented

2026-10-05 06:02:57 +02:00

Is it possible to get destination boxes back? I mean those we have seen before traceroute graphs were changed.
They were extremely useful, much more than return traceroute graphs.

Is it possible to get destination boxes back? I mean those we have seen before traceroute graphs were changed. They were extremely useful, much more than return traceroute graphs.

adam commented

2026-10-05 06:02:58 +02:00

so any chances to fix backward traceroutes?

so any chances to fix backward traceroutes? <img width="622" height="591" alt="Image" src="https://github.com/user-attachments/assets/5b13276a-552b-4664-b7b7-de6ab97214a9" />

adam commented

2026-10-05 06:02:58 +02:00

so i made my own graph... well... nope! it's not as easy as swap source and destination, even not as if middle array in backward order... nope it's FUBAR!

(black arrows is forward part from backward traceroute which is in red arrows and not reached its destination)

so i made my own graph... well... nope! it's not as easy as swap source and destination, even not as if middle array in backward order... nope it's FUBAR! <img width="854" height="1024" alt="Image" src="https://github.com/user-attachments/assets/f71342a5-0dd6-4957-8c73-65693cf809d5" /> (black arrows is forward part from backward traceroute which is in red arrows and not reached its destination)

adam commented

2026-10-05 06:02:59 +02:00

web.py

here is my attempt to fix this. at least now it matches with traceroutes in client. key point is this:

        if hasattr(route, 'route_back') and route.route_back:
            is_route_back = True
       ...
        if is_route_back:
            path.extend(route.route_back)
        else:
            path.extend(route.route)

[web.py](https://github.com/user-attachments/files/29210060/web.py) here is my attempt to fix this. at least now it matches with traceroutes in client. key point is this: ``` if hasattr(route, 'route_back') and route.route_back: is_route_back = True ... if is_route_back: path.extend(route.route_back) else: path.extend(route.route) ```

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/meshview#33