Nada is a MASQUE network relay that tunnels TCP and UDP over HTTP/3.
Nada is compatible with Apple's NERelay API. The implementation is based on:
- CONNECT-UDP (RFC 9298)
- CONNECT (RFC 9114)
- HTTP/3 prioritization (RFC 9218)
- HTTP/3 Extended CONNECT (RFC 9220)
- HTTP Datagrams and the Capsule Protocol (RFC 9297)
As a prototype under construction, Nada is not intended for production. Please cite CITATION.cff if you use Nada in your research.
cp env-examples.sh env.sh
# Edit env.sh to match your deployment
vim env.sh
# Keep runtime settings in the current shell
source ./env.sh
# Install nada
bash build.shApplications can connect to Nada's local TCP or UDP listeners at [::1]:18018 or 127.0.0.1:18018.
Using the CLI for local testing requires specifying a --target to which all flows are sent.
# See available options
nada --help
# Start the relay
nada relay
# Open a CONNECT-UDP tunnel:
nada connect-udp --target 1.1.1.1:53
# Open a CONNECT tunnel:
nada connect --target 1.1.1.1:53
# Tunnel a DNS query through the relay:
dig @127.0.0.1 -p 18018 example.com +notcp +ignore
dig @::1 -p 18018 example.com +notcp +ignoreNada's Rust library can also be used to open tunnels directly with connect_udp or connect_tcp.
The HTTP/3 GET example opens a single client-relay connection and opens concurrent tunnels with potentially varying origins, paths, and priorities. Each tunnel carries an independent end-to-end HTTP/3 connection.
Run it from the repository root:
cargo run --release --example getScenarios can be specified in scenarios.txt, c.f. the example guide.
Nada uses unreliable transmission by default. Each endpoint selects its preferred substrate for all CONNECT-UDP tunnels. Both endpoints decode both incoming formats regardless of their outgoing mode.
| Client | Relay | Client → relay | Relay → client |
|---|---|---|---|
| default | default | QUIC DATAGRAM | QUIC DATAGRAM |
| default | --reliable |
QUIC DATAGRAM | DATAGRAM capsules |
--reliable |
default | DATAGRAM capsules | QUIC DATAGRAM |
--reliable |
--reliable |
DATAGRAM capsules | DATAGRAM capsules |
Reliability covers the client–relay segment. CONNECT always carries
HTTP/3 DATA frames reliably and is therefore not affected by --reliable.
TLS_CURVES_LIST is configurable in env.sh.
Library callers can use connect_udp_with_priority(target, urgency, incremental)
to choose each tunnel's priority.
CONNECT and CONNECT-UDP requests use HTTP Priority u=3,i by default.
Multipath support with cooperative scheduling extensions is available here. Artifacts of that legacy version are available here.