feat: rebranded from vpn-router to linux-manager.

This commit is contained in:
slawek committed 2026-11-22 09:51:07 +01:00
1 parent 8efe21bfa6
commit 85a1ffa21f
238 files changed
+5010 -3761

No files matched your search

+4 -4
View File
@@ -13,18 +13,18 @@ code not already used to sign in.
change signs you out.
- **Enrol** or **replace** an authenticator app: scan the QR code, then enter a code of the app.
Removing the enrolment is left to an administrator.
- **Add a passkey:** the browser or your password manager creates a passkey for the router's name;
- **Add a passkey:** the browser or your password manager creates a passkey for the server's name;
each passkey has a label and the time it was added, and a remove icon.
- **VPN profiles** (VPN users), each after your current password and, when enrolled, a code:
- **Download the OpenVPN profile:** a `.ovpn` file for an OpenVPN client, which signs in with
your name and password.
- **Download the Apple VPN profile (IKEv2):** a `.mobileconfig` that sets up the router's IKEv2
- **Download the Apple VPN profile (IKEv2):** a `.mobileconfig` that sets up the server's IKEv2
VPN on a Mac, iPhone or iPad. It also asks for a profile password, which the device asks for
when you install the profile in System Settings (Mac) or Settings (iPhone, iPad).
## Passkeys
**Sign in with a passkey** on the sign-in page uses a passkey the browser offers, without the
name, the password or the code. Passkeys work on the Manager's HTTPS address on the router's name
only. They sign in to the Manager and to the router's OpenID Provider, and open a shell on the
name, the password or the code. Passkeys work on the Manager's HTTPS address on the server's name
only. They sign in to the Manager and to the server's OpenID Provider, and open a shell on the
[Shell](shell.md) page in place of the password and code.
+4 -4
View File
@@ -1,6 +1,6 @@
# Backup
The router's backups: to a local folder, copied to the cloud with rclone, or to a Proxmox Backup
The server's backups: to a local folder, copied to the cloud with rclone, or to a Proxmox Backup
Server.
## Sections
@@ -13,13 +13,13 @@ Server.
run.
- **Local archives:** with their times and sizes, searched by name and time, 10, 25, 50 or 100 at
a time.
- **Warnings:** the PBS client or rclone the settings need is not installed on the router.
- **Warnings:** the PBS client or rclone the settings need is not installed on the server.
## Actions
- **Edit:** changes the settings in one dialog. Only the retention settings that apply to the
schedule are offered. The rclone remote is one of the router's `/etc/vpn-router/rclone.conf`,
schedule are offered. The rclone remote is one of the server's `/etc/linux-manager/rclone.conf`,
with a path and the mode, sync or copy. The token secret is kept when left empty.
- **Run now:** starts a backup; the tab reads every 3 seconds until it ends.
Restoring is done on the router as root with `vpn-router-backup restore`.
Restoring is done on the server as root with `linux-manager-backup restore`.
+7 -7
View File
@@ -1,21 +1,21 @@
# Certificates
The router's two-level CA: a root CA and issuing CAs that sign the certificates.
The server's two-level CA: a root CA and issuing CAs that sign the certificates.
## Above the tabs
- **Issue:** a certificate from a CSR, saved with its chain, or with a key the router makes, saved
as a PFX file protected by a password; the router keeps no copy of the key.
- **Issue:** a certificate from a CSR, saved with its chain, or with a key the server makes, saved
as a PFX file protected by a password; the server keeps no copy of the key.
- **Settings:** the names, lifetimes, key type, CRL validity and publishing endpoints.
- **Warnings:** what needs attention, such as a CRL about to expire.
## Tabs
- **Root:** the root CA's subject and expiry, whether its key is on the router (marked with a
- **Root:** the root CA's subject and expiry, whether its key is on the server (marked with a
warning sign) or offline, and its CRL. **Download root CA** gives its certificate; **Upload CRL**
takes a root CRL signed offline. Below, the certificates of the issuing CAs.
- **Templates:** key, lifetime, subject, usages, alternative names, certificate policies and the
CAs that issue each template. **Add template**, **Edit**, **Remove** for the router's own and
CAs that issue each template. **Add template**, **Edit**, **Remove** for the server's own and
**Reset** for a changed built-in one.
- **Extended key usages:** the usages templates may give, with their OIDs; custom ones are added
with a name and an OID.
@@ -25,6 +25,6 @@ The router's two-level CA: a root CA and issuing CAs that sign the certificates.
- **Issuing CAs:** general-purpose CAs, each with its templates and an optional ACME server.
**Add issuing CA**, **Edit** and **Remove**; a removed CA is retired and its certificate revoked.
- **Certificates:** each with its kind, template, names, expiry and state; one of another system
or of the router is revoked after a confirmation with a reason.
or of the server is revoked after a confirmation with a reason.
The root key is exported, removed and imported on the router with `vpn-router-ca`, never here.
The root key is exported, removed and imported on the server with `linux-manager-ca`, never here.
+12 -12
View File
@@ -1,21 +1,21 @@
# DNS
The router's name server (PowerDNS), the primary of the router's domains. Every domain has the
same two name servers: the router's FQDN and a secondary name server. The [web sites](sites.md)
The server's name server (PowerDNS), the primary of the server's domains. Every domain has the
same two name servers: the server's FQDN and a secondary name server. The [web sites](sites.md)
whose DNS is Router managed get their records in the domain they are in.
## Settings
- **State:** disabled, running, or not running yet; the router installs PowerDNS when it is
- **State:** disabled, running, or not running yet; the server installs PowerDNS when it is
enabled.
- **Primary name server:** the router's FQDN, the SOA and the first NS of every domain. It is the
router's name and is not edited here; its own A record is kept by the DNS of its domain,
wherever that is, not by the router's domains.
- **Primary name server:** the server's FQDN, the SOA and the first NS of every domain. It is the
server's name and is not edited here; its own A record is kept by the DNS of its domain,
wherever that is, not by the server's domains.
- **Secondary name server:** the second NS of every domain, required while the name server is
enabled. The router notifies the addresses it resolves to of every change and allows them to
enabled. The server notifies the addresses it resolves to of every change and allows them to
transfer the domains.
- **Public IP address:** the router's public IP, which the records of the sites with Public IP
take; empty when the router has none or no site uses it.
- **Public IP address:** the server's public IP, which the records of the sites with Public IP
take; empty when the server has none or no site uses it.
- **Listen:** the interfaces port 53 is open on. While IKEv2 or OpenVPN remote access is enabled,
it must not share an interface with the clients' resolver, by default on the internal one.
- **TTL:** how long resolvers keep the answers of a domain without its own TTL.
@@ -28,7 +28,7 @@ whose DNS is Router managed get their records in the domain they are in.
remove button removes a domain with its manual records. A domain inside another domain of the
router is delegated from it.
A domain the router hosts, for example `example.com`, with the router's FQDN `router.other.net`,
A domain the server hosts, for example `example.com`, with the server's FQDN `router.other.net`,
the secondary `ns2.provider.net`, and a Router managed site of `www.example.com` and
`example.com` with Public IP `203.0.113.10`:
@@ -47,10 +47,10 @@ Selecting a domain shows:
A name is relative to the domain, `@` for the domain itself. A record of a name and type the
domain already has from its name servers or its sites is not served.
Changes are served after the router applies them, a few seconds later; **Refresh** shows them.
Changes are served after the server applies them, a few seconds later; **Refresh** shows them.
## Delegation
The parent of each domain must delegate it: NS records naming the router's FQDN and the secondary
The parent of each domain must delegate it: NS records naming the server's FQDN and the secondary
name server, and, for a name server inside the domain, its A record (a glue record), at the
registrar or DNS provider of the parent.
+4 -4
View File
@@ -1,11 +1,11 @@
# Docker
Whether Docker is installed on the router, the state of `docker.service` and of the router's
Whether Docker is installed on the server, the state of `docker.service` and of the server's
Docker rules, the ports exposed on the external interface, and the rules of the
`VPN-ROUTER-DOCKER` chain.
`LINUX-MANAGER-DOCKER` chain.
Exposed ports are set on the router as root, for example:
Exposed ports are set on the server as root, for example:
```sh
vpn-config-edit set --restart docker.exposed_ports 443,8000:8100
linux-manager-config-edit set --restart docker.exposed_ports 443,8000:8100
```
+4 -4
View File
@@ -1,6 +1,6 @@
# Groups
The groups of the router's directory, with their descriptions and members.
The groups of the server's directory, with their descriptions and members.
- **Add** and **Edit:** the name, the description and the members in one dialog. A group has at
least one member: a user or a service account, but not an internal one.
@@ -8,10 +8,10 @@ The groups of the router's directory, with their descriptions and members.
to it. A group that a client of the [OpenID Provider](service-accounts.md#openid-provider) allows
cannot be removed.
## Groups the router reads
## Groups the server reads
- **admins:** its members use all pages of the Manager. Only root on the router changes it, with
`vpn-router-group` or a token of `vpn-router-token`.
- **admins:** its members use all pages of the Manager. Only root on the server changes it, with
`linux-manager-group` or a token of `linux-manager-token`.
- **Allowed groups** of an OpenID Connect client: only their members may sign in to that client.
Renaming a group renames it in those clients.
- **Roles** of a resource of the OpenID Provider assigned to a group are roles of its members, in
+9 -5
View File
@@ -1,9 +1,13 @@
# VPN Router Manager Documentation
# Ubuntu Linux Manager Documentation
The VPN Router Manager shows the state of a router running the `vpn-router` package and manages
its users, connections, certificates and services. Members of the router's group `admins` see all
The Ubuntu Linux Manager shows the state of a server running the `linux-manager` package and manages
its users, connections, certificates and services. Members of the server's group `admins` see all
pages; any other user sees only their own account.
The router and the VPN are components switched on in the server's configuration (`router.enabled`
and `vpn.enabled`). While the VPN is off the page menu has no Remote Access page; while the router
is off the Connectivity page shows only its Network tab.
The help opens at the topic of the page you are on. Links between topics open in this panel;
Back returns to the previous topic and the house icon to this one.
@@ -25,12 +29,12 @@ Back returns to the previous topic and the house icon to this one.
- **Page menu** (right end): switches between the pages; its button names the page shown.
- **Help** (question mark, left of the page menu): opens and closes this panel; the page moves left
while it is open.
- **Shell** (terminal icon, administrators): a shell on the router; pressed on the Shell page, it
- **Shell** (terminal icon, administrators): a shell on the server; pressed on the Shell page, it
returns to the page it was opened from.
- **Your name**: opens your account; pressed there, it returns to the page it was opened from.
- **Sign out**, **Settings** (gear, but not on the account page) and **Theme** (light, dark or the system's).
## Settings
The gear, hidden on the sign-in and the account page, sets how often the Overview and the Metrics tab read the router on their own: manually, or
The gear, hidden on the sign-in and the account page, sets how often the Overview and the Metrics tab read the server on their own: manually, or
every 5, 10 or 30 seconds, 1, 5 or 15 minutes. The browser keeps the choice; Defaults sets it back.
+6 -6
View File
@@ -1,26 +1,26 @@
# Logs
The last lines of the router's logs.
The last lines of the server's logs.
## Sub-tabs
- **Journal:** the systemd journal of one of the router's units, or of all units.
- **Files:** a log file the router lists in its setting `web.log_files`. Files are added on the
- **Journal:** the systemd journal of one of the server's units, or of all units.
- **Files:** a log file the server lists in its setting `web.log_files`. Files are added on the
router as root:
```sh
vpn-config-edit set web.log_files /var/log/syslog,/var/log/auth.log
linux-manager-config-edit set web.log_files /var/log/syslog,/var/log/auth.log
```
## Controls
- **Unit** or **File:** the log shown.
- **Lines:** 100, 200, 500 or 1000 of the last lines; the router answers at most 1000 at a time,
- **Lines:** 100, 200, 500 or 1000 of the last lines; the server answers at most 1000 at a time,
and reads at most the last MiB of a file.
- **Follow:** reads the log every 2 seconds and keeps the view at its last line, as `tail -f`
does. Refresh is off meanwhile.
- **Refresh:** reads the log again. A log is also read when the unit, the file or the number of
lines changes.
Older lines stay on the router: `journalctl` and the files themselves, over SSH or the
Older lines stay on the server: `journalctl` and the files themselves, over SSH or the
[Shell](shell.md).
+1 -1
View File
@@ -1,6 +1,6 @@
# Metrics
Charts of the router over the last hour, day, month or year, read every minute by default (see
Charts of the server over the last hour, day, month or year, read every minute by default (see
[Settings](index.md#settings)).
## Charts
+12 -8
View File
@@ -1,15 +1,19 @@
# Remote Access
A tab each for IKEv2, OpenVPN and WireGuard access: the settings, whether the router
A tab each for IKEv2, OpenVPN and WireGuard access: the settings, whether the server
runs the system, why an enabled one does not run yet, and the connected clients.
The page is there while the VPN component is on (`vpn.enabled`). While the router component is
off, the clients reach the networks of `local.cidrs` through NAT from the server's address, on
its one interface; while it is on, they are routed with their own addresses.
## Edit
Enables or disables the system and sets its address pool (for WireGuard the address of `wg0`) and
its port, with OpenVPN's protocol. The router applies a change in the background.
its port, with OpenVPN's protocol. The server applies a change in the background.
IKEv2 and OpenVPN also need the router's `wan.local_fqdn` and its VPN server certificate. A cloud
firewall in front of the router, such as an Azure network security group, must allow the OpenVPN
IKEv2 and OpenVPN also need the server's `wan.local_fqdn` and its VPN server certificate. A cloud
firewall in front of the server, such as an Azure network security group, must allow the OpenVPN
and WireGuard ports itself.
## IKEv2
@@ -17,7 +21,7 @@ and WireGuard ports itself.
The IPsec security associations, child SAs, connections and connection children of IKEv2 access.
**DNS domains** (Edit, one per line): the domains, with their subdomains, the clients resolve with
the router's DNS, such as `internal.cloudapp.net`; other names stay with the clients' own DNS. The
the server's DNS, such as `internal.cloudapp.net`; other names stay with the clients' own DNS. The
router pushes them over IKEv2, and the Apple VPN profile names them, so a Mac, iPhone or iPad needs
a newly downloaded profile after a change.
@@ -31,11 +35,11 @@ their password and, when enrolled, the code.
- **Connections:** each peer with its user, IPs, endpoint, handshake and traffic.
- **Peers:** the devices of the VPN users, each with its user, public key and IPs.
- **Add peer:** the user, the device's public key and the IPs, which start as the next free
address of the `wg0` network. The router checks that keys are unique and IPs do not overlap.
address of the `wg0` network. The server checks that keys are unique and IPs do not overlap.
- The eye opens the device's configuration; the download gives `<user>-<n>.conf`, with a
placeholder for the device's private key, which the router never has.
placeholder for the device's private key, which the server never has.
- The remove button removes a peer after a confirmation.
- **Server:** the router's public key with a copy icon, the endpoint and the allowed IPs a device
- **Server:** the server's public key with a copy icon, the endpoint and the allowed IPs a device
needs; **Show config** opens a device configuration with placeholders.
- In the configuration dialogs a switch leaves out the `[Interface]` and `PrivateKey` lines, which
WireGuard for Windows fills in for a new empty tunnel.
+12 -12
View File
@@ -1,30 +1,30 @@
# Overview
The Overview tab shows the state of the router, read every 10 seconds by default (see
The Overview tab shows the state of the server, read every 10 seconds by default (see
[Settings](index.md#settings)). The updates of the other packages of the system are on the
[System](system.md) tab.
## Panels
- **Status:** the overall status, ok or degraded, on its title bar; the installed version of
`vpn-router` and, when the repository has a newer one, that version;
`linux-manager` and, when the repository has a newer one, that version;
IKEv2, OpenVPN and WireGuard; the status web service and its port; HTTPS and the name it is for,
with a chip while the certificates come from Let's Encrypt's staging CA and a settings button
(see HTTPS settings below); and Caddy, its HTTPS proxy, with its version, where it comes from (Ubuntu or upstream) and the
state of `caddy.service`.
- **Services:** the state of each of the router's systemd services and of Caddy; the chip on the
title bar tells whether the router's services are active.
- **Addresses:** links to the status page over HTTPS and over plain HTTP, and to the Router
- **Services:** the state of each of the server's systemd services and of Caddy; the chip on the
title bar tells whether the server's services are active.
- **Addresses:** links to the status page over HTTPS and over plain HTTP, and to the
Manager over HTTPS, each opening in a new tab; and the issuer and the discovery URL of the
router's OpenID Provider, each with a copy icon, or off while the provider is disabled (see
server's OpenID Provider, each with a copy icon, or off while the provider is disabled (see
[Service accounts](service-accounts.md#openid-provider)).
- **Backup:** the result of the last run, the next run and Run now (see [Backup](backup.md)).
- **PostgreSQL:** each cluster with its main settings and its databases with their sizes.
- **Configuration:** the sections of the router's configuration the other pages do not show,
- **Configuration:** the sections of the server's configuration the other pages do not show,
among them the status web service (`web`) and HTTPS (`https`).
Caddy is switched to upstream's packages on the router as root with
`vpn-router-caddy use-upstream`.
Caddy is switched to upstream's packages on the server as root with
`linux-manager-caddy use-upstream`.
## HTTPS settings
@@ -33,12 +33,12 @@ takes every certificate, the web sites' included, from Let's Encrypt's staging e
rate limits are far higher but whose certificates no browser trusts: it is for routers that are
rebuilt often, for tests only. While it is off, Caddy takes its certificates from Let's Encrypt,
and from ZeroSSL when Let's Encrypt refuses, such as for its limit of 5 certificates a week for the
same name. Saving runs the router's setup again, which applies the change. The other HTTPS
settings are changed on the router with `vpn-config-edit`.
same name. Saving runs the server's setup again, which applies the change. The other HTTPS
settings are changed on the server with `linux-manager-config-edit`.
## Updates
- **Check update** asks the router's package repository for newer versions.
- **Check update** asks the server's package repository for newer versions.
- **Upgrade** appears when one is found; it installs the new packages after a confirmation and
shows the upgrade's output. A reboot is offered when a package asks for one.
- Nothing is read while a check, an upgrade or a reboot runs.
+9 -9
View File
@@ -1,12 +1,12 @@
# Service accounts
Accounts that other systems sign in with to use the router's services, such as an OpenTelemetry
Collector reading the router's metrics. They cannot sign in to the Manager.
Accounts that other systems sign in with to use the server's services, such as an OpenTelemetry
Collector reading the server's metrics. They cannot sign in to the Manager.
## Columns
- **Name:** a GUID, which Add proposes, or a user name.
- **Kind:** a service account, or **Internal**: the router creates and manages an internal one for
- **Kind:** a service account, or **Internal**: the server creates and manages an internal one for
its own services, so it has no actions here.
- **OpenID Provider:**
- as a client: the number of redirect URIs and the allowed groups, the grants, `public`, and the
@@ -22,13 +22,13 @@ Collector reading the router's metrics. They cannot sign in to the Manager.
## OpenID Provider
The router can sign its users in to other systems with OpenID Connect. Its issuer and discovery
The server can sign its users in to other systems with OpenID Connect. Its issuer and discovery
URL are on the Addresses panel of the [Overview](router.md), each with a copy icon, and while it is
enabled the title of the list has the number of its clients. It is turned on on the router as
enabled the title of the list has the number of its clients. It is turned on on the server as
root:
```sh
vpn-config-edit set --restart oidc.enabled true
linux-manager-config-edit set --restart oidc.enabled true
```
### As a client
@@ -44,17 +44,17 @@ A service account with a redirect URI or a grant is a client:
- **Allowed groups:** only their members may sign in to the client; without any, every user may.
- **Client credentials:** the client gets a token as its own service account, with its secret and
without a user, for jobs and scripts.
- **Device authorization:** a program without a browser shows a code. The user opens the router's
- **Device authorization:** a program without a browser shows a code. The user opens the server's
device page, enters the code, signs in, and allows or denies the program.
- **Public client (no secret):** for programs that cannot keep a secret, such as a CLI; it cannot
use client credentials.
- **Client scopes:** the scopes of resources the client may ask for, as `<resource>:<scope>`.
Users sign in on the router's page with their password and code, or with a passkey.
Users sign in on the server's page with their password and code, or with a passkey.
### As a resource
Every service account is also a resource: an application that checks the router's tokens, such
Every service account is also a resource: an application that checks the server's tokens, such
as an S3 gateway. A client asks for a token for it by its name, or by asking for its scopes.
- **Scopes:** what clients may ask to do there, such as `read`, asked for as `<name>:read`. A
+13 -13
View File
@@ -1,22 +1,22 @@
# Shell
A login shell on the router, as your console account: your own POSIX account of the directory, or
A login shell on the server, as your console account: your own POSIX account of the directory, or
a local account root chose.
- **Opening** asks for your password and code again, unless you used a shell within the router's
- **Opening** asks for your password and code again, unless you used a shell within the server's
`web.shell_auth_timeout` minutes. **Open with a passkey** takes one of your passkeys instead,
unlocked with your device's PIN or biometrics; it shows when you have a passkey (see
[Account](account.md)).
- **Closing:** the router ends the shell after `web.shell_idle_minutes` without a keystroke; the
- **Closing:** the server ends the shell after `web.shell_idle_minutes` without a keystroke; the
page shows the reason and keeps the terminal readable.
## Editor
`vre FILE...` (or `vpn-router-editor FILE...`) in the shell opens the files in the editor of this
`lme FILE...` (or `linux-manager-editor FILE...`) in the shell opens the files in the editor of this
page and returns at once:
```sh
vre /etc/hosts ~/notes.txt
lme /etc/hosts ~/notes.txt
```
- **Tabs:** each file has a tab with its name, and its path as the tooltip. A dot marks unsaved
@@ -25,27 +25,27 @@ vre /etc/hosts ~/notes.txt
terminal and the editor; the shell keeps running.
- **Minimap button** (left of Save): shows or hides the minimap at the right edge of the editor.
This browser remembers the choice.
- **Save** (or Ctrl+S): writes the file on the router, as your console account. When the file
changed on the router after it was read, **Reload** takes the router's version and **Overwrite**
- **Save** (or Ctrl+S): writes the file on the server, as your console account. When the file
changed on the server after it was read, **Reload** takes the server's version and **Overwrite**
writes yours.
- **Limits:** text files of up to 1 MiB, at most 20 at a time. A file that does not exist is
created when saved. A file your console account may not write cannot be saved; edit it in the
terminal.
- **When files close:** when the shell ends, every file closes and the icon goes away. `vre`
- **When files close:** when the shell ends, every file closes and the icon goes away. `lme`
works only in this shell.
## Requirements
- Membership of `admins`, enrolment for one-time passwords (see [Account](account.md)), also when
you open the shell with a passkey, as the router's login session and `sudo` need it, and console
login, which root switches on the router:
you open the shell with a passkey, as the server's login session and `sudo` need it, and console
login, which root switches on the server:
```sh
vpn-router-user console <name> --posix
linux-manager-user console <name> --posix
```
- The router offers the shell only while its `web.shell` is `true`:
- The server offers the shell only while its `web.shell` is `true`:
```sh
vpn-config-edit set web.shell true
linux-manager-config-edit set web.shell true
```
+6 -4
View File
@@ -1,10 +1,12 @@
# Site-to-site connections
The Connectivity page: the router's IPsec site-to-site connections and its network.
The Connectivity page: the server's IPsec site-to-site connections and its network.
Site-to-site connections need the router component (`router.enabled`); while it is off, the
page shows only the Network tab.
## Status tab
Each connection the router set up, with the local and the remote identity, the subnets it
Each connection the server set up, with the local and the remote identity, the subnets it
resolved and how long it has been up, and their IPsec security associations, child SAs,
connections and connection children. IKEv2 access connections are on the IKEv2 tab of
[Remote Access](remote-access.md).
@@ -24,7 +26,7 @@ authentication and whether the tunnel is established.
- **Pre-shared key:** typed as a password; required while the connection has none and kept when
left empty; never shown.
- **Certificates:** the PEM certificate of a remote CA is optional; without it the peer's
certificate must come from the router's site-to-site CA.
certificate must come from the server's site-to-site CA.
The router applies a change in the background by running its setup again. The connection the
The server applies a change in the background by running its setup again. The connection the
router was installed with is `remote-site`.
+11 -11
View File
@@ -1,13 +1,13 @@
# Web sites
Static web sites that Caddy serves on the router, each from its own folder,
`/var/lib/vpn-router/sites/<name>`. The files of a site are on the [Files](site-files.md) tab, and
Static web sites that Caddy serves on the server, each from its own folder,
`/var/lib/linux-manager/sites/<name>`. The files of a site are on the [Files](site-files.md) tab, and
the name server of their domain on the [DNS](dns.md) tab.
## Settings
- **State:** whether the sites are served.
- **Largest upload:** the largest file or zip archive the Files tab and the router's API take.
- **Largest upload:** the largest file or zip archive the Files tab and the server's API take.
- **WebDAV:** whether the folders are served over WebDAV, and its URL with a copy icon.
**Settings** edits them.
@@ -22,13 +22,13 @@ the name server of their domain on the [DNS](dns.md) tab.
certificate and key given with the site.
- **Editors:** the group whose members may change the files besides the admins.
- **DNS:** who serves the records of the host names. **User managed:** a DNS provider outside the
router. **Router managed:** the router's name server gives each host name an A or AAAA record in
its domain on the [DNS](dns.md) tab, with the router's **Public IP** (the Public IP address of
router. **Router managed:** the server's name server gives each host name an A or AAAA record in
its domain on the [DNS](dns.md) tab, with the server's **Public IP** (the Public IP address of
the DNS settings), **Internal interface IP** or **External interface IP**. A host name in none of
the router's domains gets no record.
the server's domains gets no record.
A host name may be the router's FQDN, on a port of the site's own, such as 443, which the router's
own services leave free. Such a site is User managed: the record of the router's FQDN stays with
A host name may be the server's FQDN, on a port of the site's own, such as 443, which the server's
own services leave free. Such a site is User managed: the record of the server's FQDN stays with
the DNS of its domain.
## Actions
@@ -39,11 +39,11 @@ the DNS of its domain.
## Rules
- The router's own ports, such as 22, 7081, 7443, 7444 and 7445, cannot be taken by a site.
- The server's own ports, such as 22, 7081, 7443, 7444 and 7445, cannot be taken by a site.
- Sites sharing a port need host names of their own, the same Listen and the same kind of TLS.
- Let's Encrypt needs host names that resolve to the router from the internet, and port 80.
- Let's Encrypt needs host names that resolve to the server from the internet, and port 80.
- A certificate and key must belong together and name the host names.
- An issuing CA's certificates are trusted by browsers that trust the router's root CA.
- An issuing CA's certificates are trusted by browsers that trust the server's root CA.
## WebDAV
+4 -4
View File
@@ -1,6 +1,6 @@
# System
The System tab manages the router's operating system.
The System tab manages the server's operating system.
## System updates
@@ -8,10 +8,10 @@ The System tab manages the router's operating system.
new version, as of apt's last update of its package lists.
- **Check update** updates apt's package lists and lists the packages again.
- **Upgrade** appears when a package can be upgraded; after a confirmation it runs
`apt-get upgrade -y` on the router and shows its output. It upgrades the installed packages
`apt-get upgrade -y` on the server and shows its output. It upgrades the installed packages
only: none is installed or removed, and a package that needs a new one is kept back.
- Services restart during the upgrade; when `vpn-router` is upgraded, the page may not
- Services restart during the upgrade; when `linux-manager` is upgraded, the page may not
answer for a while, and **Reload page** loads its new version.
- A reboot is offered when a package asks for one, as after a new kernel.
- Only one upgrade runs at a time: this one or the upgrade of `vpn-router` on the
- Only one upgrade runs at a time: this one or the upgrade of `linux-manager` on the
[Overview](router.md) tab.
+5 -5
View File
@@ -1,6 +1,6 @@
# Users
The users of the router's directory, without the [service accounts](service-accounts.md).
The users of the server's directory, without the [service accounts](service-accounts.md).
## Kinds of users
@@ -15,7 +15,7 @@ The users of the router's directory, without the [service accounts](service-acco
- **Passkeys:** how many passkeys the user signs in to the Manager with.
- **Console:** for a member of `admins`, the console login: off, the user's own POSIX account with
its uid, or the local account it runs as; marked as refused while the user is not enrolled for
TOTP. Root switches it on the router with `vpn-router-user console`.
TOTP. Root switches it on the server with `linux-manager-user console`.
## Actions
@@ -23,9 +23,9 @@ The users of the router's directory, without the [service accounts](service-acco
- **Edit:** the names and the e-mail address of a VPN user, the e-mail address of a Manager-only
account.
- **Password**, **Disable**, **Enable**, **Unlock** after failed logins, and **Remove**.
- **Profile:** downloads the OpenVPN client profile, while the router runs OpenVPN.
- **Apple VPN profile** (Apple icon): downloads a `.mobileconfig` that sets up the router's IKEv2
VPN on a Mac, iPhone or iPad, while the router runs IKEv2. The password you type protects the
- **Profile:** downloads the OpenVPN client profile, while the server runs OpenVPN.
- **Apple VPN profile** (Apple icon): downloads a `.mobileconfig` that sets up the server's IKEv2
VPN on a Mac, iPhone or iPad, while the server runs IKEv2. The password you type protects the
user's key in the profile; the device asks for it when the profile is installed.
- **OTP:** enrols an authenticator app with a QR code, stored once a code of the app is entered,
or removes the enrolment.