Configuration Reference

What the engine is, what each setting does on the phone and on the server, the lines of a phone's file, where the phone's traffic and names go, and what the app keeps private.

Where this page comes from

The source code of both apps and of our Aether fork, the server as Aether server sets it up, and the cases of Test results, which the descriptions below name where they show a setting at work.

The engine

Aether is a Cloudflare WARP client by CluvexStudio (github.com/CluvexStudio/Aether, AGPL 3.0). The apps and the server guide build our fork of it, tag v2.4.0-srp.2 of github.com/bigmoveus/Aether: Aether 2.4.0 with these changes, each its own commit:

Public mode

SettingWhat it does
The WARP identityOn its first connection the engine registers a free WARP device and keeps its keys in the app's own storage, one for MASQUE and one for WireGuard. Later connections use them again. No account or e-mail address is involved.
TransportMASQUE carries the tunnel as an HTTP CONNECT-IP request to a WARP edge on port 443, over HTTP/3 (QUIC) or HTTP/2 (TLS over TCP). With Both, the app falls back to HTTP/2 when no HTTP/3 edge works. WireGuard is WARP's original transport over UDP. Over MASQUE, the engine opens the tunnel only after a packet has gone through it; an edge that takes the request but carries no traffic is given up.
Endpoint ScanBalanced checks more of WARP's edges and takes a good one. Turbo takes the first that answers, which saves time when it works.
WARP+ LicenseAt connect time the app binds the key to the WARP device in use and checks the account type. An invalid key is refused by WARP, and the connection goes on with free WARP (case ae-warp-plus-invalid-license).
TorWARP via Tor reaches the WARP edge through Tor, over MASQUE on HTTP/2; the traffic still leaves the internet at Cloudflare. Tor Only leaves the internet at a Tor exit, without WARP. Tor needs a few seconds to half a minute more to connect: 5 to 25 seconds in our runs.
TLS FragmentationSplits the ClientHello of the HTTP/2 connection's TLS handshake, for networks that block connections by the name in it.

The server's settings

The container of the server guide gets these settings:

SettingWhat it does
AETHER_PROTOCOL=masqueThe engine reaches WARP over MASQUE. Without it, the engine asks which protocol to use.
AETHER_SCAN=balancedThe endpoint scan, as in the app.
AETHER_NOIZE=firewallThe engine's profile for disguising its QUIC traffic: firewall is its default for MASQUE.
AETHER_TLS_VERIFY=1The engine checks the certificate of the WARP edge against the pins it carries (the apps set the same); without it the container logs tls verification: disabled and takes any certificate.
AETHER_QUICK_RECONNECT=1After a restart the engine goes back to the last edge that worked instead of asking whether to.
-v aether-data:/dataThe engine's WARP identity and its last working edge, kept across restarts and new images. The image sets AETHER_CONFIG=/data/aether.toml.
-p 10.66.66.1:1819:1819The engine's SOCKS5 port, which the image sets with AETHER_SOCKS=0.0.0.0:1819, published on wg0's address only.

The phone's file

In Private mode the app reads these lines of the file add-phone.sh makes:

LineWhat the app does with it
PrivateKeyThe phone's key for the WireGuard handshake.
AddressThe phone's address inside the tunnel. It must be IPv4, and the server's address must be the first of its network: the app reaches the engine at that address, port 1819.
PublicKey, PresharedKeyThe server's public key and the phone's preshared key. If either does not match, the server does not answer the handshake (cases ae-private-wrong-server-key and ae-private-closed-port show the message).
EndpointThe server and its UDP port; Server and Port in the profile fill in from it and, if changed, replace it.
AllowedIPsThe addresses the phone may reach through WireGuard: 10.66.66.1/32, the engine, is enough.
PersistentKeepaliveA keepalive every 25 seconds when nothing else is sent.

Routing and DNS

What stays private