Skip to content

Machines on your network (Wake-on-LAN)

A GPU machine at home or in an office has no cloud API. Prism can still power it on when a request needs its model and off after idle time:

  • On: Prism asks the service agent of another, always-on machine in the same network (a NAS, a mini PC, or the machine Prism runs on) to send a Wake-on-LAN packet to the GPU machine’s network card.
  • Off: Prism stops the machine’s model servers as usual, then asks the machine’s own agent to shut the machine down.

Prism never creates or deletes machines; it only powers a paired machine on and off.

  1. Wake-on-LAN turned on in the machine’s firmware. Open the BIOS or UEFI settings of the GPU machine and turn on Wake-on-LAN (it may be called “Wake on PCI-E”, “Power on by LAN” or “Resume by LAN”). If the network card has its own Wake-on-LAN setting in the operating system, turn it on too. Prism cannot see the firmware setting; without it the machine does not wake.
  2. A wired connection. Most Wi-Fi cards cannot wake a machine.
  3. A second machine with the agent in the same subnet, confirmed in Prism and switched on when the GPU machine should wake. The machine Prism runs on counts when it is in that subnet and added as This server.
  4. For power-off: a one-time permission on the GPU machine, see below.
  1. Pair the GPU machine (Add a machine) and confirm it.
  2. Pair and confirm the always-on machine the same way.
  3. Open the GPU machine in Compute providers and press Power on over the network (Wake-on-LAN).

The agents report their network cards to Prism (name, MAC address, IPv4 and IPv6 addresses). Prism picks the GPU machine’s wired card in the shared subnet and shows which machine will send the packet. The button is disabled, with the reason, while no other confirmed machine shares a subnet with it or its agent has not reported its network yet (an agent reports it once it runs Prism’s version; agents update themselves).

The machine card then shows, for example:

gpu-box-1 On [Power off]
Power: Wake-on-LAN via office-nas · MAC 3c:7c:3f:aa:bb:cc (from the agent)
Power off after idle [30 min]

An account without root may not shut a machine down unless it sits at the machine’s own screen: on Debian 13, logind’s polkit policy answers org.freedesktop.login1.power-off with “yes” only for an active local session and asks for an administrator password otherwise. The agent runs as a user service and is never in such a session, so it needs a one-time grant:

Terminal window
sudo prism-service-agent grant-system-units --user ACCOUNT

ACCOUNT is the account the agent runs as; the console shows the exact command. This is the same command that lets the agent manage model servers running as system services (System services); it now also lets the account power the machine off (org.freedesktop.login1.power-off and power-off-multiple-sessions). It does not let the account override shutdown inhibitors. The pairing script asks for this grant on every machine that cannot power itself off yet; answer y and type your sudo password once. Without the grant Prism still powers the machine on, and the console says that power-off needs it.

  • Which machine sends the packet: every confirmed machine whose network contains the GPU machine’s address can. Prism asks the machine it runs on first, then the others in name order, and moves to the next when one does not answer. The packet goes only to the broadcast address of a subnet the sending machine is in; the agent refuses any other destination.
  • On or off: the GPU machine counts as on while its agent answers, and as off when it does not. After a wake-up request it counts as starting until its agent answers, within the power-on timeout (10 minutes by default).
  • Power off after idle works as for cloud machines (Compute providers): after that long without requests, and with no GPU process outside Prism’s model servers, Prism stops the servers and asks the agent to shut the machine down.
  • Prism never shuts down the machine it runs on.
  • Check Wake-on-LAN in the BIOS or UEFI settings, and that the machine is connected by cable.
  • The card shows “The network card reports wake-up as off” when the operating system has wake-up disabled for the card. Turn it on in the firmware settings, or with ethtool -s <card> wol g as root.
  • The sending machine must be on and in the same subnet: routers do not forward the broadcast packet to other networks.