Module admin_responder 

The device’s answer to Node Management Requests.

This is the seam between the mesh and the ULCP session. The node’s receive path taps arriving Node Management Request payloads, admit decides whether the sender is entitled to be heard at all, and responder_loop runs each admitted exchange: the [DeviceEngine] reads the envelope, the session — reached through the driver’s event loop, since it belongs to that task — serves the frame inside, and the engine wraps the answer and retains it against a retransmission.

Two things are deliberately not here. The session’s property surface is unchanged, because an administrative exchange runs through the same dispatch as the local link (Session::handle_admin_frame). And no part of the exchange holds a borrow across an await: the request crosses to the driver as bytes and the response comes back as bytes.

Structs

AdminCounters

What the binding refused, for a device that has to explain itself without having answered anybody.

Constants

ADMIN_PAYLOAD_MAX

The largest Node Management payload this device produces.

Functions

admit

Decide whether an arriving packet is a Node Management Request this device will act on, and queue it if so.

counters

What the binding has refused since boot.

publish_dev_domain

Republish the administrator list from a device-domain snapshot. Called by the device-domain sync loop on every snapshot, so a key added over either binding takes effect without a reboot.

responder_loop

Serve admitted Node Management exchanges forever.