Traceroute mismatching route paths and SNR's #22

New issue

Open

opened 2026-03-01 00:51:29 +03:00 by skobkin · 0 comments

skobkin commented

2026-03-01 00:51:29 +03:00

Owner

Number of nodes in the path and number of SNR's mismatches. It's probably caused by MQTT on the path.

But we need to be able to properly map SNR to the node, so we should probably use a map instead of an array for SNR?

{
  "completed_at": "2026-02-28T21:47:48.883366445Z",
  "forward_path": [
    "!698509f8",
    "!db51d31c",
    "!aca94684",
    "!dac8ace3"
  ],
  "forward_snr": [
    0,
    -41,
    -52
  ],
  "from": "!698509f8",
  "inferred_forward_path": true,
  "inferred_return_path": true,
  "request_id": 1042588462,
  "return_path": [
    "!dac8ace3",
    "!9e78e3b4",
    "!698509f8"
  ],
  "return_snr": [
    -17
  ],
  "scope": "lifecycle",
  "source_packets": {
    "reply": 4008125816,
    "request": 1042588462
  },
  "started_at": "2026-02-28T21:47:35.87960927Z",
  "status": "completed",
  "steps": [
    {
      "type": "request",
      "observed_at": "2026-02-28T21:47:35.87960927Z",
      "reported_at": "2026-02-28T21:47:35Z",
      "packet_id": 1042588462
    },
    {
      "type": "reply",
      "observed_at": "2026-02-28T21:47:48.883366445Z",
      "reported_at": "2026-02-28T21:47:48Z",
      "packet_id": 4008125816
    }
  ],
  "to": "!dac8ace3",
  "updated_at": "2026-02-28T21:47:48.883366445Z"
}

Same traceroute from the MeshGo client's PoV:

Route traced toward destination:
■ [mg] MeshGo test (!698509f8)
⇊ SNR: 0.00 dB
■ [nw90] nw-sys-gagarina {INFRA} (!db51d31c)
⇊ SNR: -10.25 dB
■ [rust] rustyarh_4684 (!aca94684)
⇊ SNR: -13.00 dB
■ [g1w0] g1w0 (!dac8ace3)

Route traced back to us:
■ [g1w0] g1w0 (!dac8ace3)
⇊ SNR: -4.25 dB
■ [asrn] arkh-soran (!9e78e3b4)
⇊ SNR: -12.50 dB
■ [scap] skobkin-cap (!a55e5e56)
⇊ SNR: 6.00 dB
■ [mg] MeshGo test (!698509f8)

Number of nodes in the path and number of SNR's mismatches. It's probably caused by MQTT on the path. But we need to be able to properly map SNR to the node, so we should probably use a map instead of an array for SNR? ```json { "completed_at": "2026-02-28T21:47:48.883366445Z", "forward_path": [ "!698509f8", "!db51d31c", "!aca94684", "!dac8ace3" ], "forward_snr": [ 0, -41, -52 ], "from": "!698509f8", "inferred_forward_path": true, "inferred_return_path": true, "request_id": 1042588462, "return_path": [ "!dac8ace3", "!9e78e3b4", "!698509f8" ], "return_snr": [ -17 ], "scope": "lifecycle", "source_packets": { "reply": 4008125816, "request": 1042588462 }, "started_at": "2026-02-28T21:47:35.87960927Z", "status": "completed", "steps": [ { "type": "request", "observed_at": "2026-02-28T21:47:35.87960927Z", "reported_at": "2026-02-28T21:47:35Z", "packet_id": 1042588462 }, { "type": "reply", "observed_at": "2026-02-28T21:47:48.883366445Z", "reported_at": "2026-02-28T21:47:48Z", "packet_id": 4008125816 } ], "to": "!dac8ace3", "updated_at": "2026-02-28T21:47:48.883366445Z" } ``` Same traceroute from the MeshGo client's PoV: ``` Route traced toward destination: ■ [mg] MeshGo test (!698509f8) ⇊ SNR: 0.00 dB ■ [nw90] nw-sys-gagarina {INFRA} (!db51d31c) ⇊ SNR: -10.25 dB ■ [rust] rustyarh_4684 (!aca94684) ⇊ SNR: -13.00 dB ■ [g1w0] g1w0 (!dac8ace3) Route traced back to us: ■ [g1w0] g1w0 (!dac8ace3) ⇊ SNR: -4.25 dB ■ [asrn] arkh-soran (!9e78e3b4) ⇊ SNR: -12.50 dB ■ [scap] skobkin-cap (!a55e5e56) ⇊ SNR: 6.00 dB ■ [mg] MeshGo test (!698509f8) ```

skobkin added the

bug

label

2026-03-01 00:51:29 +03:00

skobkin self-assigned this

2026-03-01 00:51:29 +03:00