Missing heartbeat/keep-alive messages in protocol #100

Closed
opened 2026-07-21 16:20:03 +02:00 by TapTap · 1 comment
Owner

Description

Long transfers with no activity may get dropped by firewalls/NATs. There is no keep-alive message in the protocol.

Location

src/shared/protocol.h (NEED STATUS enum)

Suggested Fix

Add STATUS_KEEPALIVE to the NET_STATUS enum. Sender sends it periodically during long chunk transfers; receiver resets its timeout on receipt. Frequency should be configurable (default: every 30s of inactivity).

Severity

medium

Category

feature

Sub-Agent

feature-scout (FS-6)


This issue was automatically generated by the issue-creator agent.

## Description Long transfers with no activity may get dropped by firewalls/NATs. There is no keep-alive message in the protocol. ## Location src/shared/protocol.h (NEED STATUS enum) ## Suggested Fix Add `STATUS_KEEPALIVE` to the `NET_STATUS` enum. Sender sends it periodically during long chunk transfers; receiver resets its timeout on receipt. Frequency should be configurable (default: every 30s of inactivity). ## Severity medium ## Category feature ## Sub-Agent feature-scout (FS-6) --- _This issue was automatically generated by the issue-creator agent._
Author
Owner

Fixed in PR #148 — merged into main on 2026-07-29.

Fixed in PR #148 — merged into main on 2026-07-29.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: TapTap/FastSync#100