Expand description
§ts_runtime
Tailscale runtime.
Re-exports§
pub use device_state::DeviceState;pub use device_state::RegistrationError;pub use status::Status;pub use status::StatusNode;pub use status::WhoIs;
Modules§
- capture
- Pcap stream framer for debug packet capture (
CapturePcap). Pcap stream framer for debug packet capture (CapturePcap). - control_
runner - Control runner.
- device_
state - Device connection-state tracking (
DeviceState) and typed registration outcome (RegistrationError). Device connection-state tracking: a push-style view of where aRuntimeis in its control-plane lifecycle, plus a typed registration outcome. - fallback_
tcp - Fallback TCP handler registry (
tsnet.Server.RegisterFallbackTCPHandlerparity). Fallback TCP handler registry (tsnet.Server.RegisterFallbackTCPHandlerparity). - funnel
- Client-side Funnel ingress termination (
tsnet’sListenFunneldata path). Client-side Funnel ingress termination (tsnet’sListenFunneldata path). - peer_
tracker - Peer delta update tracking.
- serve
- Stored Serve config + accept-loop runtime (
tsnet’sGet/SetServeConfig+ serving runtime). Stored Serve config + accept-loop runtime (tsnet’sGet/SetServeConfig+ serving runtime). - status
- Netmap status snapshot, WhoIs, and watcher types. Netmap status aggregation, WhoIs lookups, and a netmap-change watcher.
- taildrop
- Taildrop peer-to-peer file transfer store. Taildrop file store — the receiving half of Tailscale’s peer-to-peer file transfer.
- taildrop_
send - Taildrop file sender — the client half of Tailscale’s peer-to-peer file transfer.
Structs§
- Error
- Errors that may occur while executing or interacting with the runtime.
- Runtime
- The runtime for a tailscale device.
Enums§
- Capture
Path - The direction/path of a captured packet, mirroring Go Tailscale’s
capture.Path. The numeric values are the on-wire path codes written into each pcap record’s Tailscale preamble. - Error
Kind - Kinds of errors that may occur while running the runtime.
Type Aliases§
- Capture
Hook - A debug packet-capture hook. When installed on a
DataPlane, it is invoked with the path and the raw IP packet bytes for every plaintext packet crossing the datapath. It must be cheap and non-blocking — it runs inline on the single-threaded dataplane step, so a slow hook backs up the datapath. Wrapped inArcso it is cheap to clone andSend + Syncfor the actor that installs it.