UniFi Dream Machine Pro

Ubiquiti · gateway with controller, 1U · UDM-Pro

what it is

A 19-inch rack device, 1U high, combining four roles: an internet gateway with two WAN links, a nine-port gigabit switch with two 10G transceivers, a controller managing access points and switches, and a video recorder with a bay for a 3.5-inch drive. The front panel has a 1.3-inch touchscreen.

It has two independent firmware versions: the system (UniFi OS) and the network application (UniFi Network). The manufacturer releases and documents them separately, so the statement "the gateway is up to date" only makes sense together with which version it refers to.

what we read from it

850 parameters from the controller API — more than one and a half times as many as from a rack switch. This is not one device but four, and each role adds its own measurements.

Things that no switch has:

• Both WAN links separately — each with its own state, address, and counters of traffic, errors and downtime. With two providers, this is the only way to tell "the internet is down" from "one of the two links failed and traffic moved to the other".
• The result of the latest link speed test — download, upload, latency and the server it was run against, together with the date.
• Processor load, memory usage and temperature sensor readings. The gateway processes traffic, so when overloaded it slows down the entire network, while the switch next to it looks healthy.
• Capacity and usage of storage media, including the drive in the bay. Recording stops silently when the drive fills up — without this measurement it becomes visible only when a recording is needed.
• The table of clients seen by the gateway — with the number of the port each of them sits on.
• Events that the controller names itself — a detected loop, loss of a device together with the devices behind it, a forced PoE power cycle.

port layout

The eight LAN ports are arranged in two rows, and the numbering runs downward, then to the right: 1, 3, 5, 7 on top and 2, 4, 6, 8 on the bottom. Adjacent numbers therefore do not sit side by side but one above the other — when looking for a specific cable in a rack, this is the first thing that confuses.

There is a single WAN port, standing apart to the right of those eight, level with the bottom row. The two 10G transceivers are stacked: the upper one is number 10, the lower 11. The reset button is near the right edge of the panel, past the transceivers.

what to watch out for

• Enabling SNMPv3 in the settings disables SNMP v2c on the gateway. Measured in application 10.6: with v3 enabled the gateway's SNMP port is closed; after disabling it, it responds after about 15 seconds. Switches and access points are not affected.
• The gateway ports do not report spanning tree state. The switch ports have this field, the gateway ports do not — even though loop protection operates precisely on them.
• Threat detection in blocking mode cuts off a source selectively. A series of short SSH connections or a port sweep can block an address so that SSH goes silent while ping and web pages work. The block expires on its own after a dozen or so minutes, so it looks like a firewall whim. Exceptions are kept in a separate settings section, not the one visible next to the mode.
• Older event and alarm paths in the API return "not found". In application 10.6 the event log is at a newer address and requires a POST request; a GET request receives error 405, which is easy to mistake for a missing feature.

what we cannot read

• Traffic broken down by individual devices over time — the gateway reports cumulative counters, and the history for each client has to be built separately.
• The content of recordings, or anything about the camera images. The device reports the state of the recorder, not what it recorded.
• The technical condition of the drive — capacity and usage are visible, not the health of the medium.

full parameter list from the controller interface

The list shows WHAT the device exposes — including parameters we do not use ourselves. There are no values here at all: it is a catalog of capabilities, not a reading from anyone's network. It is not a closed list either — explanation below the table.

850 parameters

List source: reading of 1 working unit (as of 2026-09-27). The list is the sum of what we observed — more units reveal more parameters, so numbers for different models are not directly comparable.

full list of parameters read via SNMP

This list comes from a different reading path than the controller list above. These are objects the device itself returns over SNMP (names from MIB files). There are no values here, and no port numbers either.

115 parameters

SNMP list source: reading of 2 units (as of 2026-10-18); sample counted separately from the controller list.