How to use Wake-on Gaming

1. Overview

Wake-on Gaming is a web control panel for Condor Gaming Server. It lets authorized Steam users:

• Send Wake-on-LAN packets to power on the game server
• Check whether the server is online (LAN and VPN addresses)
• Download a WireGuard VPN profile to reach your home LAN from away
• Upload WireGuard client configs to join other networks and switch between them
• Scan the LAN and hub VPN for hosts, then wake machines that expose a MAC address

Open the panel at https://wakeup.tracedroute.net.

2. Sign in with Steam

1. Go to https://wakeup.tracedroute.net.
2. Click Sign in with Steam.
3. Complete Steam OpenID login in your browser.
4. If your account is authorized, you land on the Control center dashboard.

If you see “Access denied”, your Steam ID is not on the allow list. Ask the server owner to add your Steam ID to WOG_ALLOWED_STEAM_IDS in the server .env file.

Use Sign out in the top bar when you are done on a shared computer.

3. Default game server

The first card on the dashboard is your primary machine: Condor Gaming Server.

Buttons

• Wake server — Sends a Wake-on-LAN packet to 192.168.1.222 using the configured MAC. Use this when the machine is off or asleep and you need it back online. There is a short cooldown between wake/shutdown actions.
• Shut down — Currently disabled on this server (WOG_SHUTDOWN_MODE=none).
• Refresh — Re-checks online status (pings both LAN and VPN addresses).

The Online / Offline badge updates automatically every 15 seconds and after a successful wake.

4. Secure VPN (connect to this host)

This section is for your remote device (Windows laptop, Linux PC, phone with WireGuard) to tunnel into the home network where Condor Gaming Server lives.

Built-in VPN is disabled on this server.

5. WireGuard client networks

Use this when this game server must join another network (for example a Condor hub or a friend’s WireGuard) using interface wogcli.

Both this application and the game server must be clients on the same VPN. Upload the hub (or shared) client .conf here so this host joins the same WireGuard network as Condor Gaming Server (192.168.1.222). Your remote laptop/PC must use a client profile for that same VPN as well.

Upload a new network

1. Optionally enter a Network label (e.g. “Virginia hub”).
2. Click Choose .conf and select a standard WireGuard client .conf file (must include [Interface] with PrivateKey and [Peer] with PublicKey).
3. Click Upload & connect. The profile is saved, the previous client tunnel is brought down, and the new one is activated.

Switch between saved networks

1. Open the saved networks dropdown — entries are sorted by most recently used (date/time shown in each option).
2. Select a network → Switch network.
3. The active profile shows under Active network with client address and endpoint.

Other actions

• Disconnect — Stops the client tunnel without deleting saved profiles.
• Delete — Removes the selected profile from disk (disconnects first if it was active).

Re-uploading a .conf with the same peer Endpoint updates that existing profile instead of creating a duplicate. Profiles persist across container restarts in wake-on-gaming-data/wg-client-profiles/.

6. Network discovery

Discover devices on your subnets and wake any host that reports a MAC address.

Scan scope

Use the dropdown next to Scan network:

• All networks — Scans LAN (192.168.1.0/24) and VPN subnets (10.13.13.0/24).
• LAN — ARP-based scan of the local subnet (best for finding MAC addresses).
• VPN (…) — ICMP ping scan of the hub VPN; finds peers but usually no MAC.

Scans may take up to a minute. A cooldown applies between scans.

Results table

• Host — Name from nmap, reverse DNS, or MAC vendor.
• Network — Subnet the host was found on.
• Address — IPv4 address.
• MAC / Vendor — Required for per-row Wake buttons.
• Status — Up/Down from a quick ping.

Use the filter box to search by hostname, IP, MAC, or vendor. Rows marked Default match your game server. LAN wake sends a broadcast + unicast; VPN wake sends a directed packet only.

7. Common remote workflows

A. Wake the game server from away

Requires you, this Wake-on Gaming app, and Condor Gaming Server all to be on the same VPN (see overview).

1. On the game-server host: WireGuard client networks → upload the shared hub/client .conf → Upload & connect (if not already active).
2. On your remote device: connect WireGuard using a client profile for that same VPN (section 4 or your hub’s config).
3. Open https://wakeup.tracedroute.net → sign in with Steam.
4. Click Wake server (targets VPN IP 192.168.1.222).
5. Wait ~30–60 seconds → status should change to Online.

B. Reach home LAN devices while traveling

1. Activate the Secure VPN tunnel on your laptop.
2. Run Scan network → All networks or LAN.
3. Wake other Ethernet devices (Basement PC, etc.) from the table if they have a MAC.

C. Move the server to a new location / hub

1. Obtain the new WireGuard client .conf from the remote network admin.
2. WireGuard client networks → upload the file → Upload & connect.
3. Later, use the dropdown to switch back to any saved network.

8. Prerequisites & tips

• Same VPN for everyone. This Wake-on Gaming app, the game server (192.168.1.222), and your remote browser device must all be WireGuard clients on the same VPN network. Use WireGuard client networks on the server host and matching client configs on your PC.
• Wake-on-LAN requires WOL enabled in BIOS/UEFI and, for best results, Ethernet (not Wi‑Fi sleep).
• The game server must have a static or DHCP-reserved MAC (10:ff:e0:2d:7a:5e).
• If the server is fully powered off, this web UI is not running — something else on the network (or hub) must deliver the magic packet, or you wake it while connected via VPN to a machine that can reach the LAN broadcast.
• Do not share downloaded .conf files — they contain private keys.
• This app does not modify Condor’s separate hub VPN (wg0 / port 51820).

9. Troubleshooting