Skip to main content

Module uplink_calls

Module uplink_calls 

Source
Expand description

Node calls (mail.*, task.*) over the restreamer uplink.

Since A2, C2 no longer forwards signed node calls to core over HTTP: it answers 410. These calls ride a dedicated m4a channel on the node’s existing uplink. That channel is Noise-encrypted end to end to core and opaque to C2. Core takes the node id from the stream, never from the payload. The legacy HTTP path stays as a fallback for nodes without an uplink.

Important: this channel shares the node’s single TCP uplink with g4a. A handshake retry storm (or a wedged Noise session on core’s m4a drain) can fill the TCP send buffer and stall PTY control. Open failures therefore back off hard.

Structs§

NodeCalls
Shared by the door and the node-mail wake; the restream bridge publishes its uplink here.

Enums§

CallError

Constants§

NODE_CALL_CHANNEL
Channel id of the node-call channel; core runs its m4a drain consumer on it.