feat: surface sidecar QUIC + circuit-relay flags through the launcher#102
Merged
Conversation
The Go sidecar already implements the NAT-traversal stack (DCUtR hole-punching, circuit-relay-v2 client/server, AutoNAT, a -quic udp listener) but the Python launcher had no way to turn any of it on — so a home/residential GPU behind NAT/CGNAT could not be launched with the features that let it join. Thread three flags through sidecar_cmd + launch_sidecar, driven by env and OFF by default (an untouched launch stays byte-identical to the legacy tcp-only form): SHARD_QUIC=1 -> -quic (also listen on udp/quic-v1 at the tcp port) SHARD_RELAYS=a,b -> -relays (reserve a circuit on public relays when NAT'd) SHARD_RELAY=1 -> -relay (be a public relay + AutoNAT server for others) Unit-tested token-exact (split, not substring) so -relays never masquerades as -relay; 39 launcher-hardening tests green. This is the wiring; the end-to-end QUIC-vs-TCP and relay/hole-punch validation is pending the residential (Ghent) link. Note for vast: QUIC reach also needs the udp port mapped (-p 29600:29600/udp).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Surfaces the sidecar NAT-traversal stack (already built in Go) through the Python launcher, so a home or NAT-bound GPU can actually be launched with it. Three env flags, OFF by default (untouched launch = byte-identical legacy tcp-only):
SHARD_QUIC=1->-quic(udp/quic-v1 listener at the tcp port; better hole-punch on lossy/CGNAT)SHARD_RELAYS=a,b->-relays(reserve a circuit on public relays when behind NAT)SHARD_RELAY=1->-relay(be a public relay + AutoNAT server)Unit-tested token-exact (split, not substring) so
-relaysnever masquerades as-relay; 39 launcher tests green.Safe/additive (off by default, launcher-only, no serving-path change) but left as a PR rather than auto-merged because the residential/relay strategy is actively being decided (DZ relay-bridge pivot). The end-to-end QUIC-vs-TCP + hole-punch validation is pending the Ghent link (tasks #6/#7). vast note: QUIC reach also needs the udp port mapped (
-p 29600:29600/udp). Tasks #7/#8.