Files
dawnline/package/luci-app-dawnline/Makefile
T
Aemeath 31a2065f05 Dawnline 0.6.0
- 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
2026-10-18 15:32:27 +03:00

59 lines
2.1 KiB
Makefile

# SPDX-License-Identifier: MIT
#
# Dawnline — AmneziaWG access server for OpenWrt with a LuCI admin UI and a
# personal self-service portal.
include $(TOPDIR)/rules.mk
PKG_NAME:=luci-app-dawnline
PKG_VERSION:=0.6.0
PKG_RELEASE:=1
PKG_LICENSE:=MIT
LUCI_TITLE:=Dawnline - AmneziaWG access server
# AmneziaWG itself (kmod-amneziawg, amneziawg-tools, luci-proto-amneziawg) is not
# in the OpenWrt feeds: install.sh and the Components page install a build made for
# the router's firmware. The portal's HTTPS needs any libustream TLS module and
# openssl-util; Settings offers to install them when the portal is turned on.
# Runtime dependencies only (control file Depends): the package ships scripts
# and web files, so the SDK has nothing to build for them, and as build
# dependencies ip-full (iproute2) and kmod-veth would pull in the whole kernel.
# OpenWrt 25.12's luci.mk wants a version on each; (>=0) means any.
LUCI_EXTRA_DEPENDS:=luci-base (>=0), rpcd-mod-ucode (>=0), ucode (>=0), ucode-mod-fs (>=0), ucode-mod-uci (>=0), \
ucode-mod-ubus (>=0), ucode-mod-uloop (>=0), ip-full (>=0), kmod-veth (>=0), uhttpd (>=0)
LUCI_PKGARCH:=all
# The web bundles are already minified by esbuild (LuCI's jsmin cannot parse modern JS).
LUCI_MINIFY_JS:=0
LUCI_MINIFY_CSS:=0
PKG_MAINTAINER:=tickcount
LUCI_MAINTAINER:=tickcount
LUCI_URL:=https://github.com/tickcount/luci-app-dawnline
define Package/luci-app-dawnline/conffiles
/etc/config/dawnline
endef
# /etc/dawnline (keys, backups, usage, history) survives a sysupgrade too:
# root/lib/upgrade/keep.d/dawnline-data (the package's own keep.d file is
# generated from conffiles).
define Package/luci-app-dawnline/prerm
#!/bin/sh
[ -n "$${IPKG_INSTROOT}" ] && exit 0
# An upgrade keeps everything running; only a removal tears down.
[ "$$1" = "upgrade" ] && exit 0
/etc/init.d/dawnline stop 2>/dev/null
/usr/bin/dawnline teardown 2>/dev/null
# The heartbeat check would point at a removed file.
grep -qs /usr/libexec/dawnline/ /etc/crontabs/root && {
sed -i '\#/usr/libexec/dawnline/#d' /etc/crontabs/root
/etc/init.d/cron restart 2>/dev/null
}
exit 0
endef
include $(TOPDIR)/feeds/luci/luci.mk
# call BuildPackage - OpenWrt buildroot signature