Aemeath 466ca6c7b0
Build packages / CI (push) Blocked by required conditions
Build packages / Version (push) Waiting to run
CI / Web (format, types, tests, bundles) (push) Blocked by required conditions
CI / ShellCheck (push) Blocked by required conditions
CI / ucode static checks (push) Blocked by required conditions
CI / ucode compiles and tests pass (OpenWrt 24.10) (push) Blocked by required conditions
CI / ucode compiles and tests pass (OpenWrt 25.12) (push) Blocked by required conditions
Dawnline 0.8.0
- Every field says what is wrong as you type, in the router's own words,
  and Save refuses what the router would: UDP port when editing a server,
  MTU, keep-alive, public address, DNS for devices, person name, device
  limit, end date and data limit, device names (the next free "Phone 2"
  is offered), home services, circles, portal title, redirect and other
  addresses, defaults, update time
- Cyrillic names give Latin ids, hostnames and file names; names are
  counted in characters, the rule names the characters it refuses; end
  dates must exist on the calendar; a mistyped extra portal address is
  refused instead of dropped
- The public address is checked on the router as it is typed: points at
  this router, at another address, behind Cloudflare, or the WAN is
  private or CGNAT; the wizard says so before the first step, never
  pre-fills a private WAN address and says where its suggestion came
  from; the Connection card says when the server was last reached from
  the internet; IPv6 names and literals work throughout
- A person can be moved to another server from their page; a server's
  tunnel network can be changed in the Danger zone (devices are
  renumbered and marked "Update config"); WAN and LAN zones come from the
  router's actual devices; when the public IPv4 changed, one click puts
  the new one in
- Over the data limit or outside the allowed hours the tunnel stays
  connected and the portal explains why nothing gets through, instead of
  a silent handshake failure; Health's "devices loaded" compares the
  peers themselves, not their count
- Portal: install links for this platform, two first steps on a first
  visit, the phone's back button closes a sheet, the file goes through
  the share sheet into the app, two QR codes (AmneziaVPN camera, AmneziaWG
  and WireGuard apps), the sheet notices the first connection
- Admin: Enter submits a dialog, arrow keys walk the menus, Find in People
  ("/" focuses it), a device of a paused, ended or over-limit person says
  so, "Keep access" past its end date is said on the Overview, Allowed
  hours enforce nothing until saved, the invite card shares the link
- Health warns when another package's policy routing (mwan3, pbr) sends
  tunnel traffic past the home-device path
- CLI: person ls, device ls, log with -n, --since, --level, --src and
  --json; exit code 2 for an unknown command and 1 when health finds an
  error; person rm asks for --yes when devices would go; devices added
  from the command line get their event and "issued" marker like the
  UI's
- Three disguises: Off, Balanced and Maximum. Standard and Strong (1.0-style
  junk only, which networks learned to spot) are no longer offered; a server
  still on one keeps running and its card says to switch. A new server gets
  the strongest disguise its router can run
- Portal: setting up a device is one sheet with two steps. Get the app
  (AmneziaVPN first; AmneziaWG, and WireGuard with the disguise off, behind
  "Another app") from the store of the device in hand, with the GitHub release
  where no store has it and the version the server needs said once; then add
  the connection (open in AmneziaVPN, copy the key, share or download the
  file). A device set up from another device gets its link to take there, as a
  QR code for a phone; a phone set up from a computer also gets the connection
  as a code, one code revealed at a time so the camera cannot read the wrong one
- Portal motion: the first visit comes in once (blocks in reading order,
  meters fill, the sun rises in the logo); a repaint glides cards to their
  new places and brings changed values into focus; sheets slide up on
  phones and can be pulled down, come into focus on a computer, follow
  their content's height and turn into the next sheet in place; tabs and
  segments slide, menus, tooltips and toasts grow out of what opened them,
  copy buttons turn into a check, buttons waiting for the router spin;
  with reduced motion only the fades remain
- Portal: while a device is set up, a card at the top shows the way from
  it to the router with a light running along it; on the first connection
  the way fills green, the steps fold away and the sheet closes by itself.
  The first connection is the first fresh handshake, so it is no longer
  missed while the watcher catches up (or after new keys), and the device's
  card goes on to Connected
- Portal: QR codes are light dots on a black card, fuller on dense keys,
  with "Show a light code" for scanners that read only dark on light (every
  code switches, the choice is kept); the link and code a set-up sheet
  hands to another device open that device's set-up there at once
- Portal: Remove and New keys ask in a small alert with the action's icon;
  the open one of two cards is not a button; device names are no longer
  repeated in every line of the set-up sheet; the code card lines up with
  the rest of its card (a class clash gave it the page's padding); text
  keeps the arrow cursor, store badges and link buttons are not underlined
2026-10-18 23:28:10 +03:00
2026-10-18 15:32:27 +03:00
2026-10-18 23:28:10 +03:00
2026-10-18 15:32:27 +03:00
2026-10-18 15:32:27 +03:00
2026-10-18 23:28:10 +03:00
2026-10-18 23:28:10 +03:00
2026-10-18 15:32:27 +03:00
2026-10-17 01:03:23 +03:00
2026-10-17 07:39:24 +03:00
2026-10-18 15:32:27 +03:00

Dawnline

CI Build packages

Your OpenWrt router as a private VPN for the people you choose.

Dawnline runs an AmneziaWG server on the router and gives every person a personal link. They open it, add their own devices (up to the limit you set) and connect with AmneziaVPN or AmneziaWG. You decide what each person may reach: the home network, the internet, or both.

Dawnline is the successor of Liminal: the same idea rebuilt around people instead of peers, with a personal portal, limits, live traffic and a LuCI admin that follows a modern design.

Overview

People A person
People Person
Personal portal Home network access
Personal portal Access

Features

  • People, not peers. One card per person with device chips, live status, traffic, end date and data limit. Add a person, send them the link or the invite card (QR code), and they do the rest.
  • Personal portal. Every person gets a link made of three words (https://vpn.example.com/kamiro-telosu-bavine). The link is the key: no accounts, no sessions, and a new link locks the old one out at once. People add, rename and remove their devices and get each one as a QR code, "Open in AmneziaVPN" (vpn://), a key or a .conf file. They cannot change access or limits. Links work on the portal's own port with a Let's Encrypt certificate (via ACME), several addresses at once (a Cloudflare-proxied name, a plain IP), the same link at home, and wrong links can redirect to your website. Behind Cloudflare, pick a port it proxies (2053, 2083, 2087, 2096 or 8443).
  • Access per person, enforced in an inet dawnline nftables table on the tunnel interface: home network only, internet only, or both, and optionally only some home networks or home services (picked from the devices the router sees over DHCP). Devices of different people reach each other never, always, or within circles (family sees family, guests see guests). "Who reaches what" sums up the rules and "Check access" walks them step by step for a device and an address.
  • Limits. End dates (pause, keep, or remove devices when they pass), monthly or total data limits, allowed hours, pause anyone. Devices drop off the tunnel at once (awg syncconf, no interface restart).
  • Disguise presets for AmneziaWG obfuscation (junk packets, header and padding parameters), with what each preset needs from the apps.
  • Internet like a home device. Tunnel clients' internet traffic enters the router from the LAN, through a small network namespace on the LAN bridge (needs kmod-veth). Whatever handles LAN traffic on the router (proxies, DPI bypass, DNS filters, the lan zone) handles VPN clients too, with no per-tool integration.
  • Overview. Who is online with what, speed now, today and the last 30 days, and a map of where people connect from (city level).
  • Diagnostics. Health checks with one-click fixes, including the ones that matter for reaching the portal from outside (DNS, port forwards, reply routing behind proxies such as SSClash/Mihomo, certificate coverage). A watchdog checks the tunnels, access rules, portal, resolver and LuCI link every minute and repairs them on its own (a cron job looks after the agent itself). One log holds people's activity and the service log: tunnel starts and stops with netifd's reasons, repairs and errors (dawnline log on the router).
  • Updates. Dawnline itself, AmneziaWG builds for your firmware (choose between Slava-Shchipunov and 2Grey, AmneziaWG 2.0 or 3.1), and the few OpenWrt packages Dawnline adds.
  • Backups nightly and before risky operations, JSON export/import to move to another router.

Requirements

  • OpenWrt 24.10 (opkg, .ipk) or 25.12 (apk, .apk)
  • AmneziaWG (kmod-amneziawg, amneziawg-tools, luci-proto-amneziawg): the installer adds a build made for your firmware when it is missing
  • About 2 MB of free flash

Install

On the router:

sh -c "$(wget -qO- https://raw.githubusercontent.com/tickcount/luci-app-dawnline/main/install.sh)"

The installer checks the firmware, the clock, free space and DNS, lets you pick a release (the latest is the default), shows the plan and asks before it changes anything. It downloads the Dawnline package for your package manager, checks it against sha256sums.txt, installs AmneziaWG built for your firmware if it is missing, then installs Dawnline with its dependencies and checks that LuCI can reach it. Then open LuCI → Network → Dawnline and run the setup wizard.

Before changing anything it saves /etc/config/{dawnline,network,firewall,dhcp,uhttpd} and the service state to /etc/dawnline/installer-backups/ (the newest three are kept); if a step fails, it puts them back. Packages are not rolled back: to return to an older release, run the installer with --tag. Everything it does is logged to /tmp/dawnline-install.log.

With options, download it first:

wget -O /tmp/dawnline-install.sh https://raw.githubusercontent.com/tickcount/luci-app-dawnline/main/install.sh
sh /tmp/dawnline-install.sh --dry-run             # check everything, change nothing
sh /tmp/dawnline-install.sh -y --tag 0.3.1        # a given release, no questions
sh /tmp/dawnline-install.sh --awg grey            # AmneziaWG from 2Grey
Option
-y, --yes No questions: the latest release (or --tag) and the recommended choices
-n, --dry-run Check the system, resolve, download and verify the release; change nothing
-v, --verbose / -q, --quiet More detail / only warnings and errors
--tag X.Y.Z A given release (sh install.sh 0.3.1 works too)
--awg auto|slava|grey|skip Where AmneziaWG comes from when it is missing: Slava-Shchipunov, then 2Grey (auto, the default), only one of them, or not at all (install it later from Dawnline → Updates). DAWNLINE_AWG does the same
--no-awg Same as --awg skip

When GitHub is slow or blocked, the installer retries downloads through ghfast.top and gh-proxy.com on its own. To fetch the installer itself through a mirror:

sh -c "$(wget -qO- https://cdn.jsdelivr.net/gh/tickcount/luci-app-dawnline@main/install.sh)"
sh -c "$(wget -qO- https://ghfast.top/https://raw.githubusercontent.com/tickcount/luci-app-dawnline/main/install.sh)"

By hand, from a release:

opkg update && opkg install ./luci-app-dawnline-0.1.0.ipk                 # OpenWrt 24.10
apk update && apk add --allow-untrusted ./luci-app-dawnline-0.1.0.apk     # OpenWrt 25.12

Upgrade from Dawnline → Updates, or run the installer again. Settings, keys and history are kept, and a backup is made first.

Remove on the router:

sh -c "$(wget -qO- https://raw.githubusercontent.com/tickcount/luci-app-dawnline/main/uninstall.sh)"

It backs up the configuration to /etc/dawnline/backups, runs Dawnline's own removal (the same as Settings → Remove Dawnline from this router), removes the package and cleans up what is left. AmneziaWG stays installed, since other tunnels may use it. After installing Dawnline again, restore the backup in Settings → Backups. With options, download it first:

wget -O /tmp/dawnline-uninstall.sh https://raw.githubusercontent.com/tickcount/luci-app-dawnline/main/uninstall.sh
sh /tmp/dawnline-uninstall.sh --dry-run
Option
-y, --yes Do not ask for confirmation
-p, --purge Also delete the configuration, keys, history and every backup (/etc/config/dawnline, /etc/dawnline); no backup is made
--remove-awg Also remove AmneziaWG, unless another interface still uses it (--keep-awg, the default, keeps it)
-n, --dry-run Show what would be removed; change nothing

By hand: Settings → Remove Dawnline from this router (keeps a backup), then opkg remove luci-app-dawnline or apk del luci-app-dawnline.

What Dawnline changes on the router

Only objects it created: network interfaces tagged _dawnline, firewall sections named dawnline_*, the inet dawnline nft table, /tmp/hosts/dawnline, the dawnline network namespace with its two veth links (dlx0, dll0, the latter a port of the LAN bridge), policy rules for the tunnel interfaces with one routing table, a second dnsmasq instance on port 5354 (/var/etc/dawnline-dns.conf), a cron line for the agent's heartbeat check and, while the portal is on, a uhttpd instance for it. dawnline teardown removes all of them.

Data lives in /etc/config/dawnline (mode 0600, contains private keys) and /etc/dawnline/ (usage, events, issued configurations, backups). Live counters are kept in /var/run/dawnline and flushed to flash at most hourly.

Development

package/luci-app-dawnline/
  root/usr/share/ucode/dawnline/   ucode library: model (core), AmneziaWG (awg), apply, live,
                                   ops, view, loop, portal
  root/usr/share/rpcd/ucode/       luci.dawnline RPC object
  root/usr/libexec/dawnline/       agent (usage, limits, presence) and updater
  root/usr/share/dawnline/portal/  portal CGI wrapper and its (minified) assets
  root/usr/bin/dawnline            command line (`dawnline help`)
  htdocs/                          LuCI views and the generated module dawnline/app.js
web/                               TypeScript sources of the admin UI and the portal
build/Dockerfile                   package build with the OpenWrt SDK
scripts/                           build, deploy and check scripts
cd web
npm ci
npm run format        # Prettier
npm run ci            # format check, types, tests, minified bundles

scripts/lint-ucode.py                 # static ucode checks
scripts/check-ucode.sh root@router    # compile every ucode file on a router
scripts/deploy.sh root@router         # install the working tree (backs up configs first)
scripts/build-packages.sh all         # .ipk and .apk with the OpenWrt SDK in Docker
scripts/capture-screenshots.mjs       # capture docs/screenshots/raw/*.png from a router
scripts/frame-screenshots.py          # frame them for this README

The web bundles are committed: CI fails when they are out of date. Pushing a tag vX.Y.Z (matching PKG_VERSION) builds both packages with the OpenWrt SDK and publishes a release with sha256sums.txt.

License

MIT

S
Description
No description provided
Readme MIT
29 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 55%
Go 31.5%
CSS 9.1%
Shell 2.4%
JavaScript 1.7%
Other 0.1%