Menu path: UMS Administration > Global Configuration > Wake On LAN Configuration

Thin clients can be wakened via the network using magic packets. A magic packet contains the MAC addresses of the thin clients that are to be wakened. In order for a thin client to be wakened, it must be in either S3 (suspend to RAM – STR), S4 (suspend-to-disk – STD) or S5 (soft-off) mode. In the UMS administration, you can specify the network addresses to which the magic packets are sent.

For scenarios where the UMS is outside the thin clients' network and broadcast packets from the WAN are not allowed, you can define one or more Linux thin clients as a Wake-On-LAN proxy.

The Wake-On-LAN proxy function is supported by Linux thin clients from Version 5.09.100.
  • Broadcast address

    The magic packet will be sent to the broadcast address of the network.

  • Last known IP address of the Thin Client

    The magic packet will be sent to the last known IP address of the thin client.

  • Automatic Wake On LAN Proxy Detection
    If any other client in the subnet is online, this client is automatically used as WoL proxy.

  • All defined subnets

    The magic packet will be sent to the network addresses of all subnets that are defined for the UMS.


    To add a subnet, proceed as follows:
    1. Click on in the area below All defined subnets.
      The Define subnets dialog will open.
    2. In the Subnet field, enter the network address of the subnet.
    3. Under CIDR (Classless Inter-Domain Routing), select the suitable suffix for the network mask.
    Values between 8 and 28 are appropriate. Example 1: The network address 10.43.8.0 with the suffix 24 corresponds to the CIDR notation 10.43.8.0/24 with the network mask 255.255.255.0. This network corresponds to a Class C network. The addresses that can be used by hosts lie between 10.43.8.1 and 10.43.8.254. Example 2: The network address 10.43.8.64 with the suffix 28 corresponds to the CIDR notation 10.43.8.64/28 with the network mask 255.255.255.240. The addresses that can be used by hosts lie between 10.43.8.65 and 10.43.8.78.
    1. If you wish, add a Comment.
    2. Click on OK.
  • Network address of the last known IP address

    The magic packet is sent to the network address of the network in which the last known IP address of the thin client is located. In order for this network address to be determined, you will need to specify a network mask for each of the possible networks.


    To add a network mask, proceed as follows:
    1. Click on in the area below Network address of the last known IP address.
      The Define network mask dialog will open.
    2. Enter the Network Mask.
    3. If you wish, add a Comment.
    4. Click on OK.
  • Wake On LAN Proxies

    The magic packet will be sent to the thin clients defined as Wake-On-LAN proxies. Each Wake-On-LAN proxy will send the magic packets as a broadcast within the network in which it is located.

    The Broadcast address, Last known IP address of the thin client, All defined subnets and Network address of the last known IP settings have no effect on the Wake-on-LAN proxy.

    The magic packet will not be sent to the thin clients defined as Wake-On-LAN proxies.

    Thin clients configured as a Wake-on-LAN proxy will retain their role, even if Wake-On-LAN proxies is disabled.


    To define one or more thin clients as a Wake-On-LAN proxy, proceed as follows:

    1. Click on in the area below Wake On LAN Proxies.
      The Edit Wake On LAN Proxies dialog will open.
    2. Highlight the desired thin client in the left-hand column.
    3. Click on to select the thin client.
    4. Click on OK.
      The thin client will now function as a Wake-On-LAN proxy.
    A thin client that is configured as a Wake-On-LAN proxy can no longer be put on standby or shut down. This restriction applies as soon as the thin client receives the settings from the UMS.


    To undo the configuration as a Wake-On-LAN proxy, proceed as follows:

    1. Click on in the area below Wake On LAN Proxies.
      The Edit Wake On LAN proxies dialog will open.
    2. Highlight the desired thin client in the right-hand column.
    3. Click on to deselect the thin client.
    4. Click on OK.
      The thin client will no longer be configured as a Wake-On-LAN proxy as soon as the setting is sent to the thin client.