You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The relay you chose is the one used. nfltr-send takes its relay from --relay, else $NFLTR_SEND_RELAY, else the relay nfltr config set-relay saved, else grpc.nfltr.xyz:443. Reading the saved relay
reads only its address and pin, never an account or key. Before, it
always dialled nfltr.xyz.
Connect errors name the relay. A send that cannot reach its relay
says which relay it tried and that --relay names another (`relay
(--relay names another): ...`); a machine certificate made for
another relay says so and names `--relay`.
A --once sender always learns that the transfer finished. When the
network dropped right after the receiver saved every file, the receive
exited 0 but the sender could keep serving. The receiver now waits for
the sender to confirm and, if the session was cut first, tells it again.
A sender whose direct-path receiver was killed exits promptly. After
a later receive completed, such a --once sender took over 20 s to
exit; now about 5 s. The reliability matrix's cut-receiver-*-direct
cells failed on this (relay client v0.23.7).
A cut stream is never taken for a whole one (link v0.12.17): a
session this side resets ends its reads with an error, not a clean end.
The install snippet installs into ~/.local/bin and creates it first.
make reliability runs nfltr-send built from the checkout (released
binaries with SEND_VERSION=), so it can prove a commit before release.
Built on link v0.12.17, relay client v0.23.7, relay proto v0.21.1 and
relay-core v0.16.6.