Skip to content

v0.1.8

Latest

Choose a tag to compare

@malisetti malisetti released this 22 Nov 10:29
· 1 commit to main since this release
  • A direct session uses less CPU. On a direct path each byte is now
    encrypted once, by the direct QUIC connection's TLS 1.3 (it already
    checks the other end's pinned key and is bound to the session), instead
    of a second time by the session's end-to-end TLS inside it; a relayed
    path keeps the session's TLS, also when a session moves between relayed
    and direct (relay client v0.25.0). nfltr-send's 10 GiB direct transfer,
    on the same change between two 8-vCPU cloud machines in one zone, took
    6 % less CPU per GiB on the sender and 6-8 % less on the receiver at an
    unchanged rate; nfltr-pipe was not measured.
  • Hard cut on the direct path: both ends need v0.1.8 for direct.
    Between v0.1.8 and v0.1.7 or earlier no direct path forms: a listener
    with an account carries the session relayed (every byte, as before);
    to a listener with no account a v0.1.8 dialler exits 12
    (direct_required) at once, and a v0.1.7 dialler exits 6 (a protocol
    error: its reset names the listener's reason, no direct path and no
    account). The relayed path is unchanged.
  • Fewer acknowledgements on paths that reorder deeply. v0.1.7's ACK
    Frequency did not reduce acknowledgements on a real long path (measured
    with nfltr-send, Helsinki to Singapore, 260 ms): on a path that reorders
    packets by more than 10 places, the receiving end still acknowledged
    each such late packet at once. Now, once the sending end sees that
    reordering, it asks again for no immediate acknowledgement of reordered
    packets (quiclink v0.9.0, its QUIC fork v0.63.1-nfltr.9). This aims to
    cut acknowledgements and their CPU on such paths; it is not measured on
    a real path yet.
  • Built on link v0.13.3, pathswitch v0.1.4, quiclink v0.9.0, relay client
    v0.25.0, relay proto v0.22.2 and relay-core v0.19.6.