adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-10-30 22:41:57 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

RemoteTerm DIRECT_MSG to a local node does not see the ACK reliably (via TCP) #201

New Issue
Closed
opened 2026-10-05 02:03:20 +02:00 by adam · 3 comments
adam commented 2026-10-05 02:03:20 +02:00
Owner
Copy link
Copy source

When sending a direct message via RemoteTerm, the message is transmitted correct, and the receiving node sees it immediately.
An ACK is sent back, but RemoteTerm does not appear to recognize it.

The ACK was confirmed on mesh analyzer and RemoteTerm's own Packet Feed as correct.

It leaves the message with ? state and retries the DIRECT_MSG, receiving a second ACK.
The second ACK is also unrecognized.

Some time (seconds) later, it retries as Flood and receives the ACK and the checkmark.

RemoteTerm is connected to pyMC via TCP/IP
pyMC-Repeater-Companion running 13 Feb 2026/11.0 (max: 510 contacts, 40 channels)
Current learned route: Direct which is correct.

The server is running on the same RPi as RemoteTerm. I don't see any packet loss between pyMC's feed and RemoteTerm's packet feed.

When sending a **direct message** via RemoteTerm, the message is transmitted correct, and the receiving node sees it immediately. An ACK is sent back, but RemoteTerm does not appear to recognize it. The ACK was confirmed on mesh analyzer and RemoteTerm's own Packet Feed as correct. It leaves the message with `?` state and retries the DIRECT_MSG, receiving a second ACK. The second ACK is also unrecognized. Some time (seconds) later, it retries as Flood and receives the ACK and the checkmark. RemoteTerm is connected to pyMC via TCP/IP `pyMC-Repeater-Companion running 13 Feb 2026/11.0 (max: 510 contacts, 40 channels)` `Current learned route: Direct` which is correct. The server is running on the same RPi as RemoteTerm. I don't see any packet loss between pyMC's feed and RemoteTerm's packet feed. <!-- github-sync-id:4591047014 -->
adam closed this issue 2026-10-05 02:03:20 +02:00
adam commented 2026-10-05 02:03:21 +02:00
Author
Owner
Copy link
Copy source

Version: RemoteTerm for MeshCore
v3.14.0·89d7725

Version: RemoteTerm for MeshCore v3.14.0·89d7725 <!-- github-comment-id:4624838041 -->
adam commented 2026-10-05 02:03:21 +02:00
Author
Owner
Copy link
Copy source

Okay that might be the fix. See how that works for you.

Okay that *might* be the fix. See how that works for you. <!-- github-comment-id:4628218620 -->
adam commented 2026-10-05 02:03:22 +02:00
Author
Owner
Copy link
Copy source

Confirmed via Discord.

Confirmed via Discord. <!-- github-comment-id:4637340175 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#201