Services and apps#
Twelve jobs, in two halves: the services the router runs itself, and the containers you add to it.
The router's own services#
| Guide | The job |
|---|---|
| Give a device the same address every time | A static mapping in a DHCP scope |
| Relay DHCP to another segment | When the server is somewhere else |
| Hand out IPv6 with router advertisements | Prefixes, resolvers, and the managed and other flags |
| Point the LAN at the router's resolver | Listen address, allowed sources, cache |
| Authoritative records for local names | Names the router answers for itself |
| Keep a name pointed at a changing address | service dns dynamic, 36 providers |
| Find printers and speakers across VLANs | The mDNS repeater |
Apps#
An app is a container declared in the router's configuration tree. That is the whole idea: an install is a diff you review, a commit you can roll back, and state that survives an image upgrade — not an opaque package with its own lifecycle.
| Guide | The job |
|---|---|
| Install an app | Directories, image, diff, commit |
| Update check and restart | What a pull does and does not do |
| Stop, uninstall, and what stays behind | Lifecycle is configuration too |
| Network-wide filtering with AdGuard Home | A worked example, including the port-53 conflict |
| Wildcard DNS, per-host DHCP options and a PXE architecture matrix | One container that closes three documented platform gaps |
What is not here#
The Companions page reports the configuration state of VyOS' own service upnp,
service dns and service dhcp-server. The agent supervises no external process; dnsmasq
is available as a catalogue app, not as an agent-managed daemon.
Checked against docs/apps.md ·
agent/catalog.json ·
ui/src/pages/Daemons.tsx ·
ui/src/pages/Dns.tsx