Skip to content
LabTether

Advanced Desktop Features

Beyond basic remote desktop, LabTether supports session recordings, Wake-on-LAN, multi-monitor layouts, and in-session file transfer. These features work across protocols where supported.

Session recordings

You can record desktop sessions for training, auditing, or "what did I just do?" moments.

How it works:

  1. Start a desktop session using a protocol that supports recording.
  2. Toggle the record button in the viewer toolbar.
  3. Work normally — the recording captures the session stream.
  4. Stop recording when you are done.
  5. Open the recordings view to find your entry with metadata (timestamp, duration, node).
  6. Play or download the recording.

Recording availability depends on the protocol and session path. WebRTC sessions support browser-local WebM capture via the record button. Other protocol paths depend on backend recording support.

Recordings are subject to the retention settings configured at Settings → Retention. If a recording disappears, check whether retention cleanup removed it.

Tip: If recording seems unavailable for a session, check the protocol. Not all protocol/session combinations support it. Try with default display settings and recording-compatible options enabled.

Wake-on-LAN

Wake-on-LAN lets you power on sleeping or shut-down machines from the LabTether console before connecting to their desktop or terminal.

Requirements:

  • The target machine's BIOS/UEFI has WoL enabled.
  • The NIC supports and is configured for WoL (most modern NICs do).
  • The network permits broadcast or directed relay.
  • LabTether knows the target's MAC address (discovered automatically from node metadata).

How it works:

  1. Open the node's desktop or action panel where the Wake control appears.
  2. Click Wake.
  3. LabTether picks the first valid MAC from node metadata and sends a magic packet.

Relay path: When a connected agent exists on the same local network as the target, LabTether sends the WoL packet through that agent first. This is more reliable than a hub-side broadcast, especially across subnets. If multiple relay agents are eligible, LabTether chooses deterministically — Linux relays first, then stable asset-ID order. Hub-side direct broadcast is the last resort.

  1. Wait for the node to come online and show a connected status.
  2. If the first attempt does not work, retry once after a short delay.

Tip: WoL failures are almost always hardware or network configuration issues. Verify the MAC is correct, WoL is enabled in firmware, and there are no VLAN or subnet broadcast restrictions blocking the magic packet.

Multi-monitor

Multi-monitor support varies by protocol:

WebRTC — When the target agent reports multiple displays, LabTether renders the desktop as a stitched multi-monitor layout using the agent-reported geometry. All monitors appear in a single connected viewport.

VNC — If the target reports multiple displays, use the display picker in the viewer toolbar to select which monitor to view. You switch between monitors rather than seeing them stitched together.

RDP and SPICE — Multi-monitor depends on the upstream protocol capabilities and the target's display configuration.

File transfer

You can move files to and from a remote machine during a desktop session without switching to the file browser.

WebRTC sessions: Drag files from your local machine onto the viewer to upload them over the WebRTC data channel. Progress shows inline in the viewer, and files land in the target directory.

VNC agent-backed sessions: Use the file download control in the viewer toolbar to pull files from the remote machine.

For bulk file operations, the dedicated File Management workflow is a better fit. In-session file transfer is for quick one-off transfers while you are already connected.