An unofficial, experimental compatibility project
ExitLag for Linux
and Apple Silicon Mac.
Use the official ExitLag Windows client through Wine, with a native bridge for game traffic. Graphical installers handle setup; your own ExitLag account handles the service.
Free bridge code, GPL-3.0-only. Requires the official ExitLag client and an active subscription or trial. Not affiliated with, endorsed by, or supported by ExitLag.
Download for your system
Choose one installer. Setup instructions are linked underneath each download.
Linux · Arch and Ubuntu
x86_64 · one shared installer archive
Download Linux installerLinux dependencies and setupLinux dependencies use apt on Ubuntu or pacman on Arch. Other x86_64 distributions need their own compatibility reports. Advanced downloads: optional Ubuntu package, uninstaller, source and checksums.
Platform support
Linux · Arch and Ubuntu
Arch Linux and Ubuntu 22.04/24.04 use the same archive and installation script. Automated checks pass on both Ubuntu versions and Arch userspace in a container.
Real WoW Classic Era gameplay was verified on Arch Linux with the original bridge. The Arch container uses the CI host kernel; it is separate from that gameplay evidence.
Mac · Apple Silicon
A macOS 15+ installer with a graphical launcher and native routing helper. Open ExitLag Bridge to reach the official dashboard.
Current routing is WoW-specific and IPv4 TCP only. Live testing used macOS 27.2. Intel binaries are not supplied. Mac installers are unsigned and not notarized.
Install ExitLag Bridge
- Choose your platform's package above, follow its setup guide, and open ExitLag Bridge.
- Open the bridge and click Download from ExitLag to visit the official download page. Download the Windows
.exe, then click Choose installer… and select it in the file picker. - Review and complete the vendor wizard. Keep
C:\ExitLagand uncheck Launch ExitLag at the end. - On Linux, use Configure games… and Launch ExitLag. Sign in directly in the official dashboard, apply your game's route, then make a new game connection. The native helper uses normal administrator authorization.
No proprietary installer or account data is bundled. The Windows NDIS driver warning 0x80004001 can be acknowledged because the native backend replaces that driver; other installer failures are not ignored.
Games tested: what actually worked
| Game / platform | Result | Observed scope |
|---|---|---|
| WoW Classic Era · Arch Linux | Working | Maintainer-verified gameplay on Arch with the original bridge. |
| WoW Classic Era · Mac | Working | Stable world gameplay with bidirectional relay traffic. |
| WoW Forever · Mac | Partial | Relayed character selection only. World entry was unavailable before release. |
| Minecraft Java · Linux | Unstable | Traffic relayed, but sessions disconnected. |
| Dota 2 / Tibia · Linux | Detection only | Traffic recognized; working relay routing was not established. |
| Other games | Untested | Community reports and pull requests are welcome. |
Earlier Linux experiments were not all repeated with the new packaged installer. Dashboard recognition and synthetic installer checks alone do not establish gameplay compatibility.
Your game, through the official ExitLag route
Game ↔ native bridge ↔ official ExitLag client under Wine ↔ ExitLag relays ↔ game server
The native backend handles interception, process attribution and steering into the official client's local proxy. The official client performs account authentication, route selection and relay transport. The bridge does not independently implement ExitLag's remote route API or relay protocol.
ExitLag on Linux and Mac: common questions
Does ExitLag work on Linux?
WoW Classic Era gameplay has been verified on Arch Linux with the original bridge. Arch users can follow the linked portable setup guide. The shared Linux archive passes install, fresh-runtime, routing-helper and removal checks on Ubuntu 22.04/24.04 and Arch userspace in a disposable container. The container uses the Ubuntu CI host kernel; these checks are separate from gameplay verification. Other games require their own compatibility evidence.
Can I use ExitLag on an Apple Silicon Mac?
Yes, within the current experimental scope: macOS 15+ on Apple Silicon, with WoW-specific IPv4 TCP routing. Classic Era world gameplay and Forever character selection were verified. Intel, UDP and IPv6 routing are not supported by this Mac release.
Do Arch and Ubuntu use the same Linux installer?
Yes. Download the same x86_64 archive for Arch Linux or Ubuntu 22.04/24.04, install the dependencies with pacman or apt, and follow the shared Linux setup guide. The optional Ubuntu .deb is an alternative installation method; choose one method at a time.
Where do I choose the ExitLag Windows .exe?
Open ExitLag Bridge after installation. Click Download from ExitLag to open the official website, then Choose installer… to select the downloaded Windows executable. The bridge does not bundle or automatically download the proprietary client.
Is ExitLag Bridge free?
The bridge's own code is free under GPL-3.0-only. The official ExitLag client and your own valid account with an active subscription or trial are still required. No accounts or service access bypass are supplied.
Do I have to run a routing script every time?
No developer Terminal script is needed for the packaged app. Open ExitLag Bridge, apply the game's route in the official dashboard, and connect the game. The native helper starts through the installed app and normal administrator authorization.
Can it route Proton or other Wine prefixes?
The Linux bridge supports exact native-executable and Wine/Proton-prefix mappings. Use Configure games and the Windows identity expected by ExitLag. A prefix mapping applies to the whole prefix. This capability is not a guarantee that every game's transport will work.
Will it reduce my ping?
There is no guaranteed latency reduction. Relay selection, server location and local network conditions affect results. Compare the same game's latency on the same server under similar conditions.
Is the commercial NetFilter SDK included?
No commercial SDK implementation or vendor filtering driver is bundled. The bridge supplies its own compatibility shim and native backend. The incomplete original authoring record for some interface declarations is documented in the repository's third-party and provenance notes.
Complete setup FAQContributingPlain-text documentation index