WarpKVM

Virtual media and accounts

Disk images as a USB drive, users and roles, two-factor sign-in, API tokens, and Wake-on-LAN on the DIY Kit.

The console's settings are grouped the same way as this page: Media and Power under Device, Access under Connectivity.

Carrier board on the Luckfox Aura from above; the Aura's USB-C OTG port is the one that carries the virtual drive to the target

Virtual media

The kit can present a disk image to the target as a USB drive, so you can boot an installer or a rescue image without touching the machine.

  1. Under Media, Upload a disk image from your computer into the kit's library. The upload is checked end to end before it is stored.
  2. In the Library, choose the image and how to mount it: as a CD-ROM or as a flash drive, and read-only or writable.
  3. The target sees a new USB drive. Boot from it as you would from a stick.
  4. Eject when you are done. A forced eject is there for a target that holds the drive open.

The library lives on the microSD card, which has about 4.7 GiB free on the 8 GB card that ships. The kit refuses an upload that would leave the card nearly full, so the system itself always has room.

Accounts and roles

The first account, created with the setup key, is an admin. Under Access, an admin adds more accounts, each with one role:

RoleCan do
AdminEverything, including accounts, network, and deleting images
OperatorKeyboard and mouse, stream settings, and uploading, mounting, and ejecting media
ViewerWatches the screen and sees the media library; keyboard and mouse are ignored

The kit always keeps at least one admin. Every account can change its own password; changing it signs out that account's other sessions.

Sessions are listed under Access and can be revoked one by one. They last 7 days by default, and an admin can set anything from 1 hour to 30 days.

Two-factor sign-in

Any account can turn on two-factor sign-in with an authenticator app (six-digit codes). Turning it on needs your password and a first code, and hands you ten one-time recovery codes: keep them somewhere safe. An admin can reset another account's second factor.

API tokens

For scripts, create a token under Access. Each token has a scope, read, control, or admin, never above its owner's role, and an optional expiry of 30 days, 90 days, a year, or a date you pick. The token is shown once; the kit keeps only a hash of it. Deleting an account revokes its tokens.

The board has no battery-backed clock, so until it has synced its time after a cold boot, tokens with an expiry are refused. Tokens with no expiry are not affected.

Wake-on-LAN

Under Power, save a machine's name and MAC address and wake it with one button. The kit sends the magic packet on its own network, so the target must be on the same network segment and have Wake-on-LAN enabled in its firmware.

For a machine that does not support Wake-on-LAN, or one that has hung, the ATX Inline card presses the power and reset buttons directly.

On this page