Wheelhouse docs

Diagnostics — tools#

The Tools tab has three panels: Traceroute, DNS lookup and Wake-on-LAN. Each runs on the router, so its answer is the network as the router sees it. None of them changes the router's settings.

Traceroute#

  1. Enter a name or an address in Host.
  2. Press Trace, or Enter.

The router's traceroute output is shown under the field. A trace through hops that do not answer takes longer to finish.

The host may contain letters, digits, dots, colons, hyphens and underscores, up to 253 characters. Anything else is refused, and the reason is shown under Traceroute failed. So is any error the router reports.

Trace needs the operator role; for other roles it is disabled with the reason "Running tools needs the operator role". It needs no licence.

DNS lookup#

  1. Enter a name in Name.
  2. Press Look up, or Enter.

The name is looked up by the router, as the devices on the network would look it up. The addresses it resolves to are shown as badges; a name that resolves to nothing shows no address. The router's full answer is shown below them, and says why a name did not resolve.

When the router forwards its lookups to a filtering resolver, such as an AdGuard Home or Pi-hole app, the answer is the filtered one.

Any role can look up a name. The same rules for the name apply as for Host, and a refusal is shown under Lookup failed.

Wake-on-LAN#

Wake-on-LAN sends a wake-up packet from the router to a device on one of its networks. The device must be set to wake when it receives one.

  1. Choose the device in Device. The list holds the DHCP reservations and the devices with a DHCP lease now, each shown as name · address · MAC address. Choosing one fills in MAC address, and fills in Interface with the router's interface on the device's network when its address is on one of them.
  2. For a device that is not in the list, leave Device at Enter a MAC address, type the device's address in MAC address, such as 00:53:00:12:34:56, and choose the Interface it is connected to.
  3. Press Wake device.

When the packet has gone, the message Wake-up packet sent says where: "To 00:53:00:12:34:56 on eth1." It confirms that the router sent the packet, not that the device woke. When the router could not send it, Not sent is shown with the reason.

The MAC address must be six pairs of hexadecimal digits separated by colons. Otherwise the field reads "Enter a MAC address, such as 00:53:00:12:34:56.", and Wake device stays disabled.

Wake device needs the operator role, and no licence. The packet is sent at once; nothing is added to the pending changes. Every attempt is recorded in the audit log as wake-on-lan, including those that were refused.

Wake-on-LAN needs the agent to run on the router. When the agent manages the router over the network instead, Not sent reads "Wake-on-LAN needs the agent to run on the router, and this one does not."

What this tab does not do#

  • No ping.
  • No traceroute options. The trace uses the router's own route and settings; there is no choice of source address, protocol, port or number of hops.
  • No lookup options. There is no choice of record type or of server.
  • Nothing is kept. A result stays on the page until you leave it.

For automation#

CallRoleWhat it does
POST /api/diagnostics/traceroute with {"host": "…"}operatorRuns a traceroute and returns the router's output.
GET /api/diagnostics/lookup?host=…viewerLooks a name up through the router's resolver; returns the addresses and the router's output.
POST /api/diagnostics/wake-on-lan with {"interface": "…", "mac": "…"}operatorSends one wake-up packet out of that interface.

None of them needs a licence. A host the rules above refuse is a 400.

Wake-on-LAN answers:

StatusWhen
200The packet was sent: {"sent": true, "interface": …, "mac": …}.
400"Enter a MAC address, such as 00:53:00:12:34:56." or "Choose one of the router's interfaces." The interface must be one the router's settings declare; VLANs are included.
501The agent is not running on the router.
502"The wake-up packet was not sent:" followed by what the router reported, or the router's interfaces could not be read.

See also#

Updated 2026-09-18 manual diagnostics traceroute dns wake-on-lan