Aemeath dc0f159447
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.14.0
- A device is renamed where its name stands on its card: a click on the
  name, Return or Space on it, or Rename in the ⋯ menu turns it into a
  field with the name selected. Return saves, and the words shimmer until
  the router answers. Esc or a click elsewhere puts the old name back. The
  rename window is gone, and the page no longer redraws under a name being
  edited
- Device names take up to 20 characters: letters of any language, digits,
  spaces and - _ . The router refuses anything else when a device is added
  or renamed, so a name can't carry symbols into configurations, file
  names or the AmneziaVPN key. The portal and the admin turn a character
  like that away as it is typed: the field shakes, its outline goes red
  and a short line says why. Suggested names (a phone's model, "Phone 2")
  are stripped of such characters and cut to fit. Names set before this
  stay as they are
- LAN Bypass: Add a device, in the portal and in the admin, has a switch
  that keeps the device's own local network (printer, TV, NAS) reachable
  while it is connected. It is off by default and stays as chosen; the
  admin's device drawer shows it. With home and internet access the switch
  says which addresses still lead to the home network
- Health warns when a server's home network is on one of the subnets home
  routers come with (192.168.0.x, 192.168.1.x and others). People with
  home access who connect from a network on the same addresses reach your
  home instead of their own, LAN Bypass or not
- The router tells when a device can't connect properly. After the problem
  lasts three minutes, the portal card and the admin drawer name it:
  can't finish connecting (the network may block it), connected but no
  data (an outdated configuration, and the card offers Reconnect), on two
  devices at once, or a connection that keeps dropping. Activity lists
  these under Problems, one line per device per hour, and says when the
  device connects normally again
- The set-up sheet's connection line follows what the device does:
  waiting, can't finish, connected, or connected but no data. The sheet
  closes by itself only once data comes through. On the device itself and
  for a router, the steps regroup to what fixes the problem: "Set it up
  again" when the handshake never finishes, "Add the connection again"
  ("Import the configuration again" for a router) when no data comes
- Set-up in the portal: a QR code too long for a camera to read gives its
  place to a code that opens the set-up link (a LAN Bypass configuration
  or a long AmneziaVPN key can be that long). A TV, box or NAS added from
  a phone gets the steps for setting up from another device. Back from
  "Open on the device" keeps the kind, LAN Bypass and the name typed. The
  packet-size note under the kinds is gone
- The portal on phones keeps its place: nothing jumps when an access row
  opens or folds, a notice comes or goes, or Safari redraws the cards. A
  reload, or coming back from the VPN app, opens where the page was. Cards
  glide to their new height, and an animation interrupted half-way goes on
  from where it is instead of snapping. A double click no longer closes
  the sheet it just opened
- In the admin, a device's drawer has its own MTU and keep-alive (empty
  means the server's), each with a Change dialog. A change touches only
  that device's configuration and restarts nothing on the router. Opening
  the drawer no longer counts as handing out the configuration: "Update
  config" stays until the new configuration is shown as a QR code,
  downloaded or copied ("Show the new configuration"). New keys set the
  device up again, as the portal's Reconnect does
- "Speed now" on a server's Overview is live: one point a second over the
  last two minutes, all there as soon as the Overview opens. The agent
  keeps those two minutes in memory and writes them out only while someone
  is looking
- Disguise values that AmneziaWG refuses or crashes on are stopped before
  they reach the kernel. That covers overlapping H1-H4, Jmin above Jmax,
  broken I1-I5 tags, padding under 12 with header protection, and more.
  Import and restore refuse them. After a hand edit in uci, the server's
  tunnel stays down and Health and the service log say why and what to do.
  Errors are full sentences in the reader's language
- The header protection key no longer shows in the status that read-only
  users can see: the Server page says only that the key is set, and each
  device's configuration still has it. The server no longer turns off
  WireGuard's protection against handshake floods (devices keep
  DisableCookies). A device can't be added with a server's own key
- An AmneziaWG update whose kernel module can't be swapped (another
  AmneziaWG interface holds the old one) no longer fails. It is installed,
  the tunnels come back on the old module, and Health and Components say
  the update starts after a reboot. On apk firmware, an install that apk
  left at the old version counts as failed. A module installed by hand is
  recorded, so after a firmware upgrade Health can tell that it is gone
- Dawnline reads only its own tunnels, each one separately. Another
  AmneziaWG interface on the router no longer slows the agent's
  once-a-second check, has its keys read or breaks Dawnline's reads. A
  portal request reads only that person's server: one process however many
  servers there are
- Fewer false disconnects: a tunnel that netifd sets up again no longer
  logs everyone as leaving and coming back, and a device with a long
  keep-alive stays online between handshakes. One configuration on two
  devices isn't logged as roaming every few seconds, and new keys end the
  old session at once. A tunnel that is missing devices is synced within a
  minute, and traffic across a tunnel restart is no longer undercounted
- Renaming a server no longer restarts its tunnel. If a tunnel's interface
  is edited outside Dawnline (LuCI, uci), the watchdog sets it up again
  with Dawnline's settings and names only the changed options. The routing
  rules for "Internet like a home device" change one at a time, new ones
  first, so traffic never falls between them. Health and the Server page
  warn when the address's AAAA record isn't this router's, or the router
  has no public IPv6: devices that prefer IPv6 fail to connect
- The README screenshots come in English and Russian; the portal's are
  taken from its demo. The demo has a switch beside × in the set-up sheet
  to show each state of the connection line. In Russian, long labels in
  the admin's wide option buttons wrap under their icon. DESIGN.md
  describes the switch, renaming on the card, the shimmer, the shake and
  how the portal scrolls. New tests cover link states, the meter, access,
  Health, firewall rules, network settings and packages
2026-10-22 00:11:50 +03:00
2026-10-20 19:33:52 +03:00
2026-10-20 19:33:52 +03:00
2026-10-22 00:11:50 +03:00
2026-10-22 00:11:50 +03:00
2026-10-22 00:11:50 +03:00
2026-10-22 00:11:50 +03:00
2026-10-22 00:11:50 +03:00
2026-10-22 00:11:50 +03:00
2026-10-21 01:42:23 +03:00
2026-10-22 00:11:50 +03:00
2026-10-20 19:33:52 +03:00
2026-10-22 00:11:50 +03:00
2026-10-22 00:11:50 +03:00
2026-10-20 19:33:52 +03:00

Dawnline

Dawnline

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

Latest release CI Downloads License
OpenWrt 24.10 OpenWrt 25.12 AmneziaWG 2.0 and 3.1

Quick start  ·  Live demo  ·  Features  ·  How it works  ·  Screenshots  ·  FAQ  ·  Development

English  ·  Русский


Dawnline runs an AmneziaWG server on your OpenWrt router and gives every person you invite a personal link. They open it, add their own phones and computers and connect with AmneziaVPN, AmneziaWG or WireGuard. You decide what each of them may reach (the home network, the internet, or both) and for how long, how much and when.

The personal portal: devices and access, and adding a phone in three steps
A person's own page: their devices and access. Adding a phone takes three steps, and the page sees it connect. Try it in the live demo: nothing installs and nothing connects.

💡 Why Dawnline?

Sharing a home VPN usually means making a config file by hand, sending it over a messenger and hoping nobody shares it further. Dawnline turns that around:

A VPN by hand With Dawnline
Setting up a device You make a config and send it They add it themselves from their link
Who can do what Everyone gets the same Home, internet or both, per person
Ending access Find and delete their peers A date, a data limit, or one click
Knowing what goes on Read wg show Who is online, traffic, places, a log
When something breaks You find out from them A watchdog notices and repairs it

It 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.

🚀 Quick start

  1. Install on the router (it asks before it changes anything):

    sh -c "$(wget -qO- https://raw.githubusercontent.com/tickcount/luci-app-dawnline/main/install.sh)"
    
  2. Set up in LuCI: Network › Dawnline, and follow the wizard. It suggests the port, the public address and the networks.

  3. Invite someone: Add person, then send them the link or the invite card with its QR code. They do the rest.

Tip

Behind Cloudflare, give the portal a port Cloudflare proxies: 2053, 2083, 2087, 2096 or 8443.

✨ Features

Three words, like vpn.example.com/kamiro-telosu-bavine. The link is the key: no sign-up, no password, and a new link locks the old one out at once.

📱 Their own devices

People add, rename and remove devices up to their limit. Adding one walks them through it: the right app, then a QR code, a link, a key or a file.

👥 People, not peers

One card per person with their devices, who is online, traffic, end date and data limit. Filter by who needs attention or is paused.

🧭 Who reaches what

The home network, the internet or both; only some networks or devices at home (a NAS, Home Assistant). Family sees family, guests see guests.

⏳ Limits

End dates, monthly or total data limits, allowed hours, a pause button. Changes apply at once, without dropping anyone else's connection.

🕶️ Disguise

Presets that make the VPN traffic harder to spot and block, with what each one needs from the apps.

🏠 Internet like a home device

Turn it on and people's devices go online the way the devices at home do, so your proxies, ad and DNS filters cover them too. Off by default: it costs speed.

🗺️ Overview and places

Who is online with what, speed now, the last 30 days, and a map of where people connect from, at city level.

🩺 Repairs itself

Health checks with one-click fixes, and a watchdog that checks the tunnels, access rules and portal every minute and mends them.

📦 Updates and backups

Dawnline and AmneziaWG built for your firmware in one place; nightly backups, and export and import to move to another router.

🌐 English and Russian

The portal follows the visitor's language and switches in its header. The admin pages and the router's messages come in Russian with the luci-i18n-dawnline-ru package.

🧩 How it works

flowchart LR
    you(["🛠️ You, in LuCI"]) -- "add a person" --> link["🔗 Their link"]
    link -- "they open it" --> portal["📱 Their portal"]
    portal -- "add a device" --> app["App and connection"]
    app == "AmneziaWG tunnel" ==> router["🌅 Dawnline<br>on your router"]
    router -- "if allowed" --> home["🏠 Home network"]
    router -- "if allowed" --> net["🌍 Internet"]
  1. You add a person in LuCI and choose what they may reach, their device limit, an end date or a data limit.
  2. They open their link on any device. The portal is theirs alone: it shows their devices and their access; access and limits stay yours to change.
  3. They add a device. The portal points them to the app for that system and hands over the connection; the router gives each device its own keys.
  4. The device connects through the router's AmneziaWG server, and Dawnline lets through what that person may reach, counts their traffic and keeps to their limits.

📸 A closer look

Overview: who is online, speed, the last 30 days and where people connect from
Overview: who is online, speed now, the last 30 days and a map of where people connect from.

People: everyone on the server, with their devices, data and state

People: online, ending soon, over the limit, outside their hours, paused.

A person: their devices, traffic, places and limits

A person: their devices, traffic, places and limits.

📋 Requirements

What Dawnline needs
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 they are missing
Free flash about 2 MB

📥 Install

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 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 Russian translation when LuCI is in Russian) and checks that LuCI can reach it.

Note

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), and puts them back if a step fails. 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.

Installer options

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
sh /tmp/dawnline-install.sh --lang ru             # with the admin's Russian translation
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 → Components). DAWNLINE_AWG does the same
--no-awg Same as --awg skip
--lang auto|ru|none The admin's translation, luci-i18n-dawnline-<lang>: auto (the default) adds it when LuCI is set to that language or has its LuCI translation; none adds none. An installed one is always kept up to date. Later: Dawnline → Components → Translation. DAWNLINE_LANG does the same
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)"
Installing 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

The Russian translation is luci-i18n-dawnline-ru-<version> from the same release, installed the same way after the app (then /etc/init.d/uhttpd restart).

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

Remove

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. After installing Dawnline again, restore the backup in Settings › Backups.

Important

AmneziaWG stays installed, since other tunnels may use it. Add --remove-awg to take it away too.

Uninstaller options

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.

❓ FAQ

Which apps do people use?

AmneziaVPN or AmneziaWG on phones and computers, and plain WireGuard when the disguise is off. The portal shows each person the app for their system and how to add the connection in it.

What happens when someone loses their link?

Make a new one on their page. The old link stops working at once; their devices keep working, unless you tick the ones to remove with it.

Does it touch the rest of my router?

Only what it created, and dawnline teardown removes all of it. The full list is under What Dawnline changes on the router.

How do I move to another router?

Export JSON in Settings › Backups on the old one, install Dawnline on the new one and import the file there.

Where do the places on the map come from?

From the address a device connects from, looked up at city level and cached on the router. It can be turned off in Settings.

🧾 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, which needs kmod-veth), 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. Access changes reach the tunnel with awg syncconf, without restarting the interface; dawnline log on the router shows the service log.

🧰 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
  po/                              the admin's string catalog (dawnline.pot, ru/dawnline.po)
web/                               TypeScript sources of the admin UI and the portal
web/i18n/                          catalog tools: collect strings, merge .po files, compile .lmo
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, catalogs, tests, minified bundles
npm run i18n          # collect new strings into the catalogs (then translate them in ru.po)

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 --demo   # the admin's README screenshots from a router, a demo cast in place of its people
scripts/capture-portal.mjs               # the portal's from its demo, in English and Russian
scripts/frame-screenshots.py             # frame them for this README

The web bundles and the catalogs are committed: CI fails when they are out of date or a string is untranslated (rules/i18n.md). Pushing a tag vX.Y.Z (matching PKG_VERSION) builds the packages and their translations with the OpenWrt SDK and publishes a release with sha256sums.txt.


Made for OpenWrt · MIT license · Back to top ↑
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%