MASQUE doesn’t make your tunnel unblockable
Every circumvention release since 2024 leans on the same pitch: wrap the traffic so it looks like HTTPS and the filter stops seeing it. Aethery is a clean example of the pitch. Native Android client, Kotlin shell around a Rust core, MASQUE over HTTP/3 as the default transport, WireGuard underneath for networks where UDP survives.
The myth: protocol choice is what beats the censor
The implied claim is that transport decides who gets through. Pick MASQUE, look like QUIC, pass. Pick WireGuard, look like nothing in particular, get dropped. There’s a seed of truth in it, which is why the myth survives contact with reality, and a payload classifier really does struggle with a tunnel that speaks HTTP/3 to a genuine relay at the other end. But payload inspection is not the first tool a censor reaches for. It’s the last one, because it costs the most.
Reality: reachability first, lifecycle second
Cheap signals get scored before any bytes get inspected: destination IP reputation, port, the shape and duration of the connection, packet-size distribution. A relay IP handed to ten thousand users is a block decision that costs almost nothing. The same README that advertises MASQUE also states the constraints in plain language. HTTP/2 fallback when HTTP/3 isn’t available. WireGuard only where UDP is reachable. Nested WireGuard still needs a reachable outer WireGuard path. Every line in that list describes a network where your chosen transport is irrelevant, because the packet never leaves the device.
Networks that drop UDP/443 break QUIC outright. Captive portals do it, hotel Wi-Fi does it, and a growing number of mobile carriers do it without announcing anything.
The second failure lives on the phone and has nothing to do with cryptography. Android’s VpnService is a runtime contract, not a checkbox. The app declares routes, receives a TUN descriptor, and is then responsible for keeping the tunnel alive across Doze, memory pressure and radio changes. When the process dies, the TUN goes with it and the device quietly falls back to the resolver the network handed out. Those queries go out in clear unless the OS pushed DoH. A censor watching port 53 doesn’t need to break MASQUE. It only needs to watch the seconds between your tunnel dropping and your mail client retrying.
Aethery answers this the correct way: a foreground service with a persistent notification, plus a Quick Settings tile that reconnects from the last saved profile without opening the app. That’s the right architecture. It is still not a guarantee. A tile that reconnects in five seconds leaves a five-second DNS window, and every one of those seconds is a query.
The transport decides whether a network lets the connection exist. The client decides what leaks once the connection stops existing, and that is the half nobody benchmarks.
There’s a third surface nobody audits: profiles, keys, subscription URLs, sometimes an account token, all sitting in one process that also renders logs and accepts a pasted config. Anything that can paste a profile can also log one, and that is the price of the one-click model.
What to check before you trust the client
Test the failure path instead of the happy path. Connect, confirm traffic flows, then force the tunnel down and watch what the phone does with a DNS query. With adb attached, airplane mode is the fastest way to break the link:
adb shell cmd connectivity airplane-mode enable
adb shell dumpsys connectivity | grep -i dns
adb shell cmd connectivity airplane-mode disable
If the resolver lines that come back point at the carrier or the gateway, your tunnel is the only thing standing between your query history and the network. That’s the state you need to harden.
- Always-on VPN with “Block connections without VPN”. On an unrooted Android device this is the only kill switch that exists. Without it, a dead tunnel silently restores normal routing and nothing tells you.
- DNS pinned inside the tunnel, and outbound 53/853 blocked at any router you control. Both places, not one. A phone resolver that ignores the tunnel is a leak no matter what the transport is doing.
- Per-app routing reviewed deliberately. Every app you leave outside the tunnel also resolves DNS outside it, and the local resolver learns what you run.
- Proxy mode for apps that ignore VpnService. Aethery exposes SOCKS5 on 127.0.0.1:1819 and HTTP CONNECT on 127.0.0.1:1820 by default, which is what makes chaining from another client possible. Check the bind address. LAN sharing requires the generated password, and with it enabled every device on your Wi-Fi has a route through your phone.
What I’d measure next is the reconnect window on a network that drops UDP/443. MASQUE drops to HTTP/2 over TCP there, and the live connection log prints enough to see whether the fallback is usable or only nominally present. Fallback code that exists and fallback code that hands back a working tunnel in under a second are two different products.