`py-multiaddr` already ships the entire tunnel compose/peel
surface and this module was reimplementing it — a raw
`maddr.split('/')` plus index arithmetic, sitting directly under
a comment congratulating itself for not hand-rolling a parser.
Same NIH trap gh #429 existed to close, just one layer up. The
API was linked from gh #443's own 2nd bullet the whole time.
So every cut now goes through the real thing,
| need | API |
| --- | --- |
| isolate the bearer | `.decapsulate_code(P_WG)` |
| per-seg maddrs | `.split()` |
| rejoin a seg tail | `Multiaddr.join()` |
| read the key | `.value_for_protocol('wg')` |
| recompose | `.encapsulate()` |
`.decapsulate_code()` turns out to handle the infix `/wg/` seg
cleanly *because* it cuts on proto-code and never tries to match
an addr value — the key seg has no addr of its own, which was
the exact thing I'd assumed would need bespoke handling.
Deats,
- rename the role fields `inner`/`inner_proto` ->
`overlay`/`overlay_proto`, matching `py-multiaddr`'s
encapsulation model (earlier segs wrap later ones) and #443's
owner table. `inner` collided head-on w/ call-stack `inner`,
where it reads as higher-up + later-called, while here the
encapsulated addr is bound *first* and sits deeper.
- drop `_segments()` and its degraded hand-split path entirely.
W/o the codec there's now one actionable `RuntimeError`
instead of a silent downgrade, superseding the swallow fix in
|
||
|---|---|---|
| .. | ||
| README.md | ||
| host_a_srv.py | ||
| host_b_client.py | ||
| wg_maddr.py | ||
README.md
tractor over a WireGuard tunnel, declared as one maddr
A two-host LAN setup: a tractor actor tree on host A, dialed from host B, with the endpoint declared as a single wg multiaddr.
Supersedes the example set in gh #482 — see what changed.
Why
examples/multihost/?tests/test_docs_examples.pywalksexamples/recursively and runs everything it collects as a subproc, assertingrc == 0. These need a real second host and a livewgtunnel, so they can’t satisfy that;'multihost' not in p[0]is already in the test’s exclusion list, which is what keeps them out of CI.
the maddr form
/ip4/192.168.1.50/udp/51820/wg/u<A_pub>/ip4/10.0.11.1/tcp/1616
\____ wg bearer ___________/\__ key __/\____ tractor ep _____/
underlay, wg `ListenPort` overlay, on the wg iface
(kernel/`wg(8)` owns it) (the ONLY part tractor binds)
Three parts, three different owners:
| part | who binds it | in the runtime? |
|---|---|---|
/ip4/../udp/51820 bearer |
kernel via wg-quick/pyroute2 |
no |
/wg/u<key> |
nothing — it’s an identity | no, verified out-of-band |
/ip4/../tcp/1616 overlay |
tractor’s IPCServer |
yes, as .inner |
Verified against py-multiaddr #108: this composed form parses and round-trips (['ip4','udp','wg','ip4','tcp']).
requirements
py-multiaddr #108 is merged (2026-07-28) but ships in no release yet — the latest 0.2.0 (2026-03-17) predates it and has no wg codec. So pyproject.toml carries a temporary [tool.uv.sources] rev pin at the merge commit, and a plain
uv syncgets you a wg-aware multiaddr. That pin goes away once a release carries the codec. You also need multibase:
uv pip install multibaseWithout the codec wg_maddr.py degrades to a plain segment split — the examples still run, but you lose per-segment validation (incl. the 32-byte key-length check), so a malformed key reaches the returned struct instead of raising. _have_wg_maddr_proto() is the gate. It deliberately does not hand-roll a wg codec (gh #429 was about dropping our NIH parser).
0. tunnel setup (out-of-band, both hosts)
Host A is the service host (underlay e.g. 192.168.1.50), host B your workstation. Overlay net 10.0.11.0/24.
umask 077
wg genkey | tee wg_priv.key | wg pubkey > wg_pub.key/etc/wireguard/wg0.conf on host A:
[Interface]
PrivateKey = <A_priv>
Address = 10.0.11.1/24
ListenPort = 51820[Peer]
PublicKey = <B_pub>
AllowedIPs = 10.0.11.2/32on host B:
[Interface]
PrivateKey = <B_priv>
Address = 10.0.11.2/24[Peer]
PublicKey = <A_pub>
Endpoint = 192.168.1.50:51820
AllowedIPs = 10.0.11.1/32
PersistentKeepalive = 25Note how ListenPort and Endpoint are exactly the maddr’s bearer segment, and [Interface] Address is its overlay host.
sudo wg-quick up wg0 # both hosts
ping -c1 10.0.11.1 # from B1. get your pubkey into the maddr
python -c "
import base64, multibase
key = open('wg_pub.key').read().strip()
print(multibase.encode('base64url', base64.b64decode(key)).decode())
"Paste the u... output into WG_MADDR in both scripts (they use the same string — A’s bearer, A’s key, A’s overlay ep).
2. run
# host A
python host_a_srv.py
# host B
python host_b_client.pyhost_a_srv.py must be importable on host B too, since portal.run() refs the fn by module path — standard tractor RPC semantics.
what changed vs #482
Four corrections, all from ai/tpt-backends/03_wg_tunnel_bindspace.md:
- the maddr semantics were inverted. #482 used
/ip4/10.0.11.1/tcp/1616/wg/u<key>— that parses, but it puts the overlay addr where the bearer belongs andtcpwhere wg’sudpListenPortgoes, and it declares no overlay ep at all.parse_wg_maddr()now rejects it with an actionable error. - parsing is pure. #482’s helper had the key-check adjacent to the parse;
verify_wg_peer()is now a separate, explicitly composed step that the caller invokes. A parser that shells out is a nasty surprise. - no
sudo. #482 ransudo wg show; a library/example must never escalate.wg showworks unprivileged for read on most setups; if yours needs root, run the script as root rather than embeddingsudo. - no new
Addressproto-type. The tunnel rides beside the inner addr in a frozenWGTunnelledAddr, and only.innercrosses intoopen_nursery(). #482 §6 floated aWGAddressregistered in_address_types— that table is abidict(1:1 proto-key↔︎type) and_addr_to_transportwants aMsgTransportper addr-type, whichwgdoesn’t have.
next
WGTunnelledAddr is deliberately example-local. Promoting it to tractor.discovery as a TunnelledAddress whose .proto_key/.unwrap() delegate to .inner, plus open_bindspace() @acms that create/tear down the iface + netns via pyroute2, is layers A→C of the plan doc.