KSP — Kush Secure Protocol

Networking & Diagnostics

RFC § 10 — Control Frames & Keepalives

Purpose

Measure cryptographic handshake and encrypted frame round-trip time (RTT) to a target KSP server.

Syntax

Command-line specification

bash / powershell

ksp ping <SERVER_URI> [OPTIONS]

Arguments

Argument	Description
<SERVER_URI>	Target server address (e.g., `127.0.0.1:9876`).

Options & Flags

Option Flag	Description
--count, -c <NUM>	Number of ping frames to transmit before stopping (default: `4`).
--interval, -i <MS>	Interval in milliseconds between consecutive ping transmissions (default: `1000`).
--size, -s <BYTES>	Payload size of the encrypted ping frame (default: `64`).

Example Usage

Example command

ksp ping 127.0.0.1:9876 -c 4

Expected Output

PING 127.0.0.1:9876 with 64 bytes of encrypted payload:
  Seq=1  RTT=1.42 ms  Status=OK  Cipher=AES-256-GCM  ReplayWin=Verified
  Seq=2  RTT=0.88 ms  Status=OK  Cipher=AES-256-GCM  ReplayWin=Verified
  Seq=3  RTT=0.91 ms  Status=OK  Cipher=AES-256-GCM  ReplayWin=Verified
  Seq=4  RTT=0.85 ms  Status=OK  Cipher=AES-256-GCM  ReplayWin=Verified

--- 127.0.0.1:9876 ping statistics ---
4 packets transmitted, 4 received, 0.00% packet loss
round-trip min/avg/max/stddev = 0.85/1.01/1.42/0.23 ms

Implementation Notes

Unlike standard ICMP ping, `ksp ping` measures full application-layer encryption and decryption round-trip efficiency.

Related CommandsView All 50 Commands →

ksp diag

ksp benchmark

ksp connect

CLI Installation Guide· Quick Start Workflow· GitHub Source Repository