Overview#

Bridge → Overview, the first page after signing in. One ring and one headline say whether anything needs you; under them, the router's WAN traffic, what needs attention, and a drawing of who is connected. A value that could not be read shows as a dash (—), never as zero.

The Overview replaced the Dashboard in 0.9.2. What the Dashboard also showed is on the pages that own it: each interface on Interfaces, rule and forward counts on their own pages, apps on Apps, and the router's details on System.

Status#

The card at the top. The ring's colour and the headline come from the router's attention check, described under Attention:

Ring	Headline	Means
Green	All clear	The check found nothing that needs you.
Amber	What needs looking at, for example "Uplink eth2 is down"	Something to look at, or a warning.
Red	What is wrong	Something is broken.
Grey	Status could not be read	The check could not be read; the reason is under the status line.

The headline reads All clear only when the check said so. A check that could not be read is never shown as a healthy one.

The line under the headline, in monospace:

edge · up 12d 4h · 2 of 2 interfaces · 903 sessions · checked 3s ago

Part	Shows
Host name	The router's host name.
up	How long the router has been running, in its two largest units.
interfaces	How many interfaces have their link up, of how many.
sessions	The connections the router is tracking.
checked	How long ago the attention check ran.

Three meters sit at the right, or under the headline on a phone:

Meter	Shows
Load	The one-minute load average divided by the number of processor cores, as a percentage.
Memory	Memory in use, of the total, for example "1.02 / 7.55 GB".
Storage	Storage in use, and its share of the disk, for example "717M · 3%".

A bar turns amber above 75% and red above 90%. A meter that could not be read shows a dash and an empty bar.

Traffic#

The traffic of one WAN interface over time. The legend names WAN in, drawn as the cyan area, and WAN out, the orange line, each with its current rate. 1h, 6h and 24h choose the range, and peak is the fastest rate in that range, in either direction. The dotted line at the right edge is now. Hover over the chart to read one minute's rates.

Each point is one minute's average, from the traffic history the router keeps (see Interfaces → History). A gap in the line is time nothing was recorded, such as while the agent restarted; the line is not drawn across it.

The interface is named beside the title:

On a router with uplinks, it is the uplink carrying traffic. With more than one uplink, the others are offered beside the title: choose one to chart it instead. Uplinks are set up on High availability → Uplinks.
On a router with no uplink set up, it is the interface the default route leaves through.
With neither, the card reads "No uplink is known: the router has no default route." and links to Uplinks.

The card reads	Means
Uplinks could not be read, so the WAN interface is not known.	The uplinks could not be read, so nothing is charted.
Traffic history could not be read.	The history could not be read; the reason follows.
Traffic history is not being recorded.	The router is not keeping traffic history.
"eth1 is not recorded: every place in the traffic history is taken by another interface."	The history keeps up to 32 interfaces, and all are in use.
Nothing recorded in this period.	No traffic was recorded in the range. When the history started within it, the card says when.

Attention#

A dot and a heading: Nothing needs you when the check found nothing, and Something needs you when it found something. The dot is the ring's colour.

Under the heading, one paragraph in the router's own words: what the check found, the most serious first. A sentence about something that needs you is a link to the page that explains it; a sentence about something that does not is plain text. A link to a page your role cannot open is shown as plain text too.

Under a line, in small type, is what the check could not look at, for example "Firewall drops are not logged." A quiet card never claims more than was checked.

The router runs the check at most every 15 seconds. When it cannot be read, the heading reads Status could not be read, with the reason under it.

Connected now#

A drawing of the router and what is connected to it.

In the drawing	Shows
The router, in the middle	The wheel in a green ring, the host name, and the connections the router is tracking. Grey when nothing could be read from the router.
The WAN, at the left, in orange	Each uplink, with its interface and current rates: `eth1 · 1.4↓ 29.9↑ Mbps`, where ↓ is what arrives and ↑ is what leaves. An uplink not carrying traffic is dimmed and marked standby, when its route is installed but not in use, or no route.
An amber ! above the WAN	A host probing the router from outside, from the attention check: its address, the number of probes, and whether they were dropped.
The LAN, at the right, in cyan	Each LAN interface, with its current DHCP leases: `eth0 · 18 leases`. — leases when the leases could not be read; no count on a router with no DHCP server.
Circles beyond the LAN	The busiest devices on the LAN, sized by their number of connections: `192.0.2.100 · 156 flows`. The last circle counts the rest: `23 · +14 more` is 14 more devices with 23 connections between them.

The moving dashed lines are the links carrying traffic. They stay still when your system asks for reduced motion.

The WAN side is the router's uplinks, or, with none set up, the interface its default route leaves through. The LAN side is every other interface with an address, except tunnels and dummy interfaces. A lease or a device belongs to the LAN whose network holds its address. The router's own addresses are never drawn as devices, and neither is a host outside the LAN, such as one reaching in through a port forward.

Up to four uplinks and four LANs are drawn; past four, the last one counts the rest, for example +3 more. On a phone the drawing is a list: the probe, the uplinks, the router, then each LAN with its devices under it.

The drawing reads	Means
No connections right now.	The router is tracking no connections.
No device on the LAN has a connection open.	The connections are the router's own, or come from outside the LAN.
Connections could not be read.	The connection table could not be read.
Uplinks could not be read.	Which interface is the WAN and which the LAN is not known, so only the router is drawn.
No uplink, No LAN	The router has no interface on that side.

Chart → opens the Sessions page.

What the page does not do#

Change anything. Every card only reads.
Keep history of its own. The traffic chart is the router's traffic history, 24 hours by the minute. Interfaces → History also keeps 31 days by the hour, for every interface.
Show every interface or device. Interfaces lists every interface, and Sessions every connection and device.

For automation#

The reads behind each card, and how often the page repeats them:

Card	Call	Interval
The ring, the headline, Attention, the probe	`GET /api/attention`	15 seconds
Host name, up, Load, Memory, Storage	`GET /api/system`	10 seconds
interfaces	`GET /api/interfaces/detail`	20 seconds
sessions, the devices	`GET /api/sessions`	10 seconds
Leases	`GET /api/dhcp/leases`	15 seconds
Which interface is the WAN and which the LAN	`GET /api/wan`	15 seconds
Current rates	`GET /api/interfaces/history?points=3`	5 seconds
The traffic chart	`GET /api/interfaces/history/archive?window=hour&interface=…`, or `window=day` for 6h and 24h	60 seconds

Every call except the two traffic calls is also repeated when changes are applied.