Tag: Relay

The Wireleap relay software now supports tracking the amount of traffic it relays, both globally and per contract. Using this data, it is also now possible to limit the amount of the traffic it will relay during a configured period, also, both globally and per contract.

This is particularly useful for two reasons. To not exceed any hosting bandwidth quota limits (which may incur unexpected charges), and to allow the allocation of specific amounts of bandwidth per Wireleap network they support.

Wireleap now uses built-in h/2 mechanisms instead of the previous implementation which encoded the initial payload (ie. next-hop and sharetoken) and the status messages on error or connection close in the request body.

This results in simplifying the code, simplifying the protocol, faster establishment and closing of connections, and improved performance. Traffic literally passes bytewise from client to target and back with no modification.

Please note, this is a backwards incompatible release.

Due to protocol versioning, it is highly recommended to keep relays up to date. This release simplifies the process, bringing automatic relay upgrade functionality, including an upgrade supervisor, migration support and update channels.

This update brings multiplexing as well as experimental TUN device support for the client (on Linux) which forwards all traffic (UDP and TCP) over the circuit.

Please note, this is a backwards incompatible release.

This sequence diagram shows the high-level flow and behind the scenes interaction between Wireleap components, from the perspective of the relay.

This documentation is imported from the wireleap/relay README.md. Find a typo? Something not clear? Edit on Github

This documentation is imported from the wireleap/relay CLI.md. Find a typo? Something not clear? Edit on Github