Repository navigation
install linux
Linux is a CLI-first platform. The GUI builds for Linux, but the command-line client (lightspeed-client) is the supported path for headless and power-user setups.
Grab the latest release from the Releases page. Pick the archive that matches your CPU:
| Your machine | Target | File |
|---|---|---|
| x86_64 (Intel/AMD) | x86_64-unknown-linux-gnu |
lightspeed-client-...-x86_64-unknown-linux-gnu.tar.xz |
| ARM64 (Ampere, Graviton, Raspberry Pi 4/5) | aarch64-unknown-linux-gnu |
lightspeed-client-...-aarch64-unknown-linux-gnu.tar.xz |
Not sure which you have? Run:
uname -mx86_64 means 64-bit Intel/AMD; aarch64 or arm64 means ARM64.
The shell installer is the easiest path. It detects your architecture and installs the client:
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/ShibbityShwab/lightspeed/releases/latest/download/lightspeed-client-installer.sh | shOr install manually from the archive:
# Replace the filename with the one you downloaded.
tar -xf lightspeed-client-...-x86_64-unknown-linux-gnu.tar.xz
sudo mv lightspeed-client /usr/local/bin/Verify the binary runs:
lightspeed-client --versionThe Linux interceptor uses nftables (or iptables) to redirect game UDP traffic, which requires root. Run the client with sudo when you start the interceptor:
sudo lightspeed-client --start-interceptor --game rustDiscovery, probing, and diagnostics (--probe-proxies, --test-control, --check) do not need root.
Make sure nftables is installed if your distribution does not ship it by default:
# Debian/Ubuntu
sudo apt install nftables
# Fedora/RHEL
sudo dnf install nftables
# Arch
sudo pacman -S nftablesThe client discovers the community relays automatically through the signed registry. No proxy address is needed.
# Probe the community relays and print a report
lightspeed-client --probe-proxies
# Start the interceptor for your game
sudo lightspeed-client --start-interceptor --game rustCheck relay discovery. Run:
lightspeed-client --probe-proxiesThis performs one discovery/probe pass and prints a visible report listing each discovered relay and its latency. You should see all eight community relays (Los Angeles, New Jersey, Singapore, Frankfurt, Tokyo, Mumbai, Madrid, Sydney).
Check control-plane registration. Run:
lightspeed-client --test-controlThis connects to the QUIC control plane, registers a session, pings, and disconnects, printing the result of each step. A successful registration proves the control plane is reachable and auth is working.
Check the environment. Run:
lightspeed-client --checkThis reports interceptor availability, root status, game detection, and proxy reachability.
Check packet flow. Once the interceptor is running and your game is connected to a server, the client's packet counters should climb. If "Packets Sent" stays at 0, the interceptor has not seen game traffic yet; see Troubleshooting.