AirVPN WireGuard import #209

New issue

Open

opened 2026-08-29 13:14:14 -04:00 by mysticalsoap · 0 comments

mysticalsoap commented

2026-08-29 13:14:14 -04:00

Owner

Same shape as the ProtonVPN work (#196): fetch/register whatever key material the API wants, stage the interface template, mark servers WireGuard-capable. Exact endpoint and field names need a source-dive (gluetun and the API docs) before any claims - not training-memory territory.

Should land on the unified entry model (#208) rather than adding another round of -WireGuard sibling entries.

AirVPN runs WireGuard fleet-wide and exposes it through the same key-authenticated API the import already uses - the server list carries a dedicated WireGuard entry-IP field (gluetun's AirVPN support is built on it), and the client-area config generator produces per-device configs. Same shape as the ProtonVPN work (#196): fetch/register whatever key material the API wants, stage the interface template, mark servers WireGuard-capable. Exact endpoint and field names need a source-dive (gluetun and the API docs) before any claims - not training-memory territory. Should land on the unified entry model (#208) rather than adding another round of `-WireGuard` sibling entries.