Skip to content

Orbit 2.5.0 (orbit-net 1.3.0)

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Oct 23:00
· 17 commits to main since this release
v2.5.0
798d3ae

Orbit 2.5.0 and orbit-net 1.3.0 close out Orbit as a distributed-systems project. This is the first published 2.x release. It includes everything since 2.0: native WAN pairing and sync, the keyboard TUI and the onboarding work.

Highlights

  • No default service (since 2.4). A fresh install uses the local network. To sync across networks, run your own service with one command:
    orbit-net init --dir ~/orbit-service --origin https://HOST:8443 --stun HOST:3478
  • Member sponsorship (orbit-net 1.3.0). An allowlisted service now admits the devices in its devices' Orbits automatically. You list your first device once. Every device that later joins one of its Orbits gets the relay with no server step. orbit-net devices remove revokes a device. orbit-net init turns this on by default.
  • Admission allowlist (orbit-net 1.2.0). A service can serve only its operator's devices. Unlisted devices can still pair toward a listed device.
  • Route accounting. orbit network status --routes shows how much of each peer's traffic went over the LAN, direct WAN (TCP/QUIC) or the relay, for 24 hours and 30 days.
  • Measurements. NAT/firewall cells, transfer rates and known limitations are in the case study.

Downloads

  • orbit packages: .deb, .rpm and tarballs for amd64 and arm64 (see SHA256SUMS and release-manifest.json).
  • orbit-net-v1.3.0-linux-{amd64,arm64}.tar.gz: the connection service, with systemd units and the operator guide.
    sha256: amd64 9d8f8e913231d6b091a6c962a203a7889609991dbb331f2a045b8887f36aacf6, arm64 cb0b86ede9705756d5fbce0cc9c30c6222206dd37848dce3146abdc34f4b8dbe

Known issues

  • A few timing-sensitive runtime tests (TestFinalR00*, TestSponsorshipRuntimeJoinNeedsNoOperator) fail intermittently, about 1 run in 6, in the CI race-detector job, which runs all packages concurrently. They pass locally, including with the race detector at GOMAXPROCS=1. Under that load a fresh relay runtime is sometimes slow to announce. The cause is under investigation.
  • Linux only. No TURN, UPnP or port mapping: when no direct path exists, traffic uses the service's budgeted relay.
Assets 12
Loading