Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
SMUX protocol version. Zero means the smux default.
Disable smux keep-alive probes.
Keep-alive interval, int64 values of time.Duration. Zero means the smux default.
Keep-alive timeout, int64 values of time.Duration. Zero means the smux default.
Maximum smux frame size in bytes. Zero means the smux default.
Maximum total smux receive buffer in bytes. Zero means the smux default.
Maximum per-stream smux receive buffer in bytes. Zero means the smux default.
Used in:
Underlying channel transport settings, for example DTLSUDPChannel.
Used in:
Maximum transmission unit of the underlying channel, in bytes.
Relative scheduling weight of this channel. Zero means the default weight.
Maximum packets this channel may send in a single rrpit timestamp window.
Used in:
How long to retain a logical rrpit session after all DTLS channels are gone. Zero closes immediately.
Client reconnect retry interval while the logical session is retained. Zero means use the transport default.
Keep the client rrpit transport session open even when there are no proxied streams.
Idle timeout when keep_transport_session_without_streams is false. Zero means use the transport default.
If positive, discard the local cached rrpit session when no remote control packet is received within this duration.
If positive, consider this DTLS channel dead when no inbound rrpit message bytes arrive for this duration.
Used in:
If non-empty, rrpit debug snapshots and packet logs are written here.
Maximum bytes per rotated debugger packet log file.
Maximum number of rotated debugger packet log files retained.
Used in:
Size of each shard carried inside a transfer lane, in bytes.
Maximum number of source data shards before a lane is finalized.
Maximum number of in-flight / buffered lanes kept by tx and rx state.
Remote sender's maximum number of source data shards per lane. Zero disables the heuristic.
Used in:
Tick interval, int64 values of time.Duration.
Used in:
the fraction of repair share (compare to data shards) to send immediately after finishing sending the data.
when there is still sending capacity in channels, send repair shards for each lane depending on this weight, and number of repair shards still missing(known from control message)
when we received acknowledgement from remote, the fraction of repair shard to send compared to data shards missing
the number of tickets before we send the secondary repair shard again
Number of ticks a finalized oldest lane may stay incomplete before stale-lane boost activates.
Number of ticks the oldest finalized lane may make no progress before stale-lane boost activates.
Minimum number of repair shards in a normal secondary resend burst.
Used in:
Whether locally assigned tx channel ids should use odd parity.
Rewind window for tx-side packet timestamp history.
Rewind window for tx-side remote control history.