fips/src/node/handlers at 974e146bb96945218def87b70b43a448623f60e1 - fips

mirror of https://github.com/jmcorgan/fips.git synced 2026-08-09 08:14:42 +00:00

Files

T

Johnathan Corgan 974e146bb9 node: demote routine per-peer and capacity-cap events from info/warn to debug

On a saturated public-mesh node the connection-lifecycle and capacity-cap
events fire continuously and drown out the genuinely notable INFO/WARN
lines. Demote them to debug and drop a redundant duplicate:

- FMP K-bit cutover promotion (encrypted): info -> debug
- "Connection promoted to active peer" (handshake): info -> debug, and
  remove the duplicate "Inbound peer promoted to active" line that
  shadowed it on the inbound path
- "Peer restart detected" (handshake): info -> debug
- "Peer removed and state cleaned up" (dispatch): info -> debug
- "Rejecting inbound TCP connection (max_inbound_connections reached)"
  (tcp): warn -> debug
- "Congestion detected, CE flag set on forwarded packet" (forwarding):
  warn -> debug
- "Removing peer: link dead timeout" (mmp): warn -> debug

These are expected, high-frequency conditions on a busy public node (new
and reconnecting peers, ECN CE marking, the inbound connection cap, and
link-dead churn), not operator-actionable signals.

2026-06-06 19:11:45 +00:00

discovery.rs

Per-destination TCP MSS clamping at the TUN boundary

2026-05-02 17:37:07 +00:00

dispatch.rs

node: demote routine per-peer and capacity-cap events from info/warn to debug

2026-06-06 19:11:45 +00:00

encrypted.rs

node: demote routine per-peer and capacity-cap events from info/warn to debug

2026-06-06 19:11:45 +00:00

forwarding.rs

node: demote routine per-peer and capacity-cap events from info/warn to debug