- Access rules fail closed: when the table cannot load, no device is loaded into the tunnels (the firewall alone would let every loaded device reach everything); an older table that survived a failed rebuild keeps its rules and a revoked device still leaves. The agent re-syncs within a minute when the table is gone - A change the router saved but could not put into effect (access rules that did not load, a server that refused its devices) is said in the admin UI instead of a plain "Saved" - The guard judges every packet, not only a connection's first: a change of access, a pause or a limit now cuts open connections too - Each server's home networks are its own: with several servers, "all home" on one no longer reaches the other's networks where firewall zones overlap - People limited to some home networks reach the router only on the addresses in those networks (LuCI and SSH on the main LAN stay closed) - Internet-only people can open their personal portal with the VPN on - Tunnel DNS reaches the resolver and the LAN's DNS from servers that do not forward to those zones on their own (Home-only names on servers without "like a home device", LAN DNS on servers with no home network) - A new personal link offers to remove the devices added through the old one, so a leaked link is really contained - Import and restore refuse an inconsistent file (devices with addresses outside their server, shared addresses, malformed keys, broken references); Health reports one, and the sync leaves such a device out instead of failing its server. A config write that did not reach flash is an error, not a silent success - Backups are kept per kind (nightly ones no longer push out manual or pre-delete ones), nightly and pre-change backups hold the config only, archives are written whole or not at all, and a failed nightly backup is logged. A restore no longer has its history overwritten by the agent's in-memory counters - Settings defaults and ranges come from one place (dawnline.schema) - Portal: anything not shaped like a personal link is answered by a shell before ucode starts (a scan on the root costs nothing); 4 portal processes at once instead of 16; a link may make 40 changes a quarter hour; over plain HTTP the page shows but configurations, new devices and new keys are refused with the HTTPS twin of the link; the connect sheet polls only while the first connection is awaited, with backoff, and stops once the link stopped working - Updates: after Dawnline's own package changes, a shell checks that LuCI reaches it and the agent runs, and puts the kept previous version back when they do not (automatic runs always keep it); the AmneziaWG module reload verifies rmmod and modprobe; installs check free space; on apk a reinstall that changed nothing is an error; uninstall.sh hands the update lock to the removal it calls; an upgrade restarts the service only where it was enabled; the release workflow pins the SDK images by digest and the actions by commit - AmneziaWG: features count only when both the tools and the kernel module have them; a server whose disguise this build cannot run (a 3.1 preset after a rollback to 2.0) is kept down and reported; Components tells 1.0 builds from 2.0 ones; `awg show dump` is parsed by shape; Maximum's DNS-shaped signature packets are made for each server and its keep-alive is a 25-35 s range - CI compiles every ucode file and runs the new tests/ucode unit tests (54 tests on the real libuci) in OpenWrt 24.10 and 25.12 rootfs containers; scripts/compile-ucode.sh does the same wherever ucode runs and scripts/ucode-container.sh locally with docker; lint-ucode checks POSIX regexes and module layering; a tag builds only after CI passes
49 lines
1.7 KiB
Ucode
49 lines
1.7 KiB
Ucode
// Dawnline — changes to /etc/config/dawnline, the one way: under the config
|
|
// lock, against a model loaded inside that lock, committed with the file kept
|
|
// private. rpcd, the portal, the CLI and the agent all go through here, so
|
|
// no change is made on a stale model and none is lost to another writer.
|
|
|
|
import { lock, unlock } from 'dawnline.util';
|
|
import * as core from 'dawnline.core';
|
|
|
|
/** Section names that are never ids of people, devices, servers, services or circles. */
|
|
export const RESERVED_IDS = [ 'settings', 'main', 'global', 'defaults' ];
|
|
|
|
/**
|
|
* Commit the dawnline config and keep it readable by root only. A commit
|
|
* that did not reach flash (full or read-only overlay) is an error: the
|
|
* caller's change never happened, and nothing downstream may act on it.
|
|
*/
|
|
export function commit(c) {
|
|
if (!c.commit(core.CONFIG))
|
|
die(`Couldn't save /etc/config/dawnline: ${c.error() ?? 'the write failed'}. Is the flash full?`);
|
|
system('chmod 600 /etc/config/dawnline');
|
|
};
|
|
|
|
/**
|
|
* Run fn(c, m) with the config lock held, on a fresh cursor and model; commit
|
|
* when fn returns (the return value is passed on). Anything fn throws aborts
|
|
* without committing and is rethrown with the same message.
|
|
*/
|
|
export function transact(fn) {
|
|
let l = lock('config');
|
|
try {
|
|
let c = core.open_cursor();
|
|
let m = core.load(c);
|
|
let r = fn(c, m);
|
|
commit(c);
|
|
unlock(l);
|
|
return r;
|
|
}
|
|
catch (e) {
|
|
unlock(l);
|
|
die(e.message ?? `${e}`);
|
|
}
|
|
};
|
|
|
|
/** Is `id` used by anything in the model (any kind of section), or reserved? */
|
|
export function id_taken(m, id) {
|
|
return index(RESERVED_IDS, id) >= 0 || m.servers?.[id] != null || m.people?.[id] != null || m.devices?.[id] != null ||
|
|
m.services?.[id] != null || m.circles?.[id] != null;
|
|
};
|