Repository navigation
AWG Agent v1.2.0
Companion release for the admin's wg-quick import (#8). Both awg-agent (kernel) and awg-agent-userspace are affected.
New
GET /interfaces/unmanaged— lists live WireGuard/AmneziaWG devices on the host that the agent has no stored config for (interfaces brought up bywg-quick/awg-quickor by hand), with the link kind (amneziawg/wireguard). Scanned on every request, so an interface raised after the agent started shows up without a restart. The admin uses it to show "Not managed" interfaces and to refuse creating a new interface under such a name.GET /interfaces/{name}/import-source— returns the host's wg-quick conf for the interface (/etc/amnezia/amneziawg/<name>.conf, then/etc/wireguard/<name>.conf) as{path, content};404when neither exists,400for a name that isn't a valid interface name. Read-only; the admin parses it and pushes the resulting config back through the usualPUT /interfaces, which adopts a live link in place.
Fixed
- amneziawg-dkms v3.0 hosts (#11):
wgctrlnow speaks the v3 netlink wire format (u32 keepalive, u64H1–H4), so device enumeration no longer fails on the first v3 device — this had broken per-peer metrics and orphan detection. The fix ships via theks-tool/wgctrl-gofork (pinned inagent/go.modandagent/e2e/go.mod). Note: dkms v3 does not acceptH1–H4ranges; pushing a config with ranges to a v3 host now fails with a clear error instead of a parse panic.
Compatibility
- Purely additive API; no config or storage format changes. An older admin keeps working against this agent, but the import feature in the admin requires this version or newer (it treats the
404from an older agent as "unknown"). - The literal path
/interfaces/unmanagedtakes precedence overGET /interfaces/{name}, so an interface literally namedunmanagedcan't be fetched by name.