Skip to content

Chore/tunnel handshake logging - #149

Merged
antoncxx merged 2 commits into
mainfrom
chore/tunnel-handshake-logging
Sep 30, 2026
Merged

antoncxx merged 2 commits into
mainfrom
chore/tunnel-handshake-logging

Conversation

@antoncxx

Copy link
Copy Markdown
Collaborator

No description provided.

antoncxx and others added 2 commits September 29, 2026 20:46
The "early eof" / "Failed to read token hash" errors gave no hint about
what was connecting. Handshake failures now log the peer address, why the
read failed (closed, timed out, I/O error), and how many bytes arrived,
with a hex and text preview so HTTP or TLS probes are easy to spot.

Connections that close without sending anything (port scans, TCP health
checks) are logged at info instead of error. read_from_stream now owns
the handshake timeout and no longer logs on its own, which removes the
duplicate tunnel_token.rs:49 error line.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Writing connections and system resources to the datastore puts heavy
load on the machine. Setting STORE_TELEMETRY_IN_DATASTORE=false makes
both RPCs log that the data was accepted and return immediately, skipping
all datastore calls (device authorization check, IP info lookups and the
inserts). Defaults to true, so existing deployments are unaffected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@antoncxx
antoncxx merged commit 2898c48 into main Sep 30, 2026
0 of 3 checks passed
@antoncxx
antoncxx deleted the chore/tunnel-handshake-logging branch September 30, 2026 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant