[Bug]: Traceroutes fail, most of the time, to register on the app with fw 2.3.0... 2.2.24 traceroutes show up on the android app. about firmware HOT 7 CLOSED

Repro steps:
-Need 3 nodes and Android version 2.2.24.
-Install 2.3.0 on two nodes.
-Install 2.2.24 on one node.
-From the 2.3.0 node send a Traceroute to the 2.2.24. You'll see the Traceroute register.
-From the 2.3.0 node send a Traceroute to the 2.3.0 node, Traceroutes won't register at all on the app.

from firmware.

Android app is 2.2.24.

from firmware.

Well, I've managed to get a Traceroute to pop up after trying 18 times... this never happened before.

from firmware.

Maybe this is related to #3452, but I am unable to reproduce. Traceroutes work for me with a node using firmware 2.2.24 and another 2.3.0, and also between two 2.3.0 nodes.

from firmware.

The interesting detail I noticed is that the node that was pinged goes to the top of the node list, like when packet comes from the mesh... but it doesn't acknowledge it as a Traceroute on the app... so, maybe this is an app issue? Packet garbled could be? Maybe we could test the hop count not changed as suggested on the other bug?

from firmware.

Here with android app and fw on 2.3.x , doensn't matter the patch version, traceroutes always show up, but always show 1 hop only: the target node.

from firmware.

Let's continue this in #3452.

from firmware.