Platforms
תוכן זה אינו זמין עדיין בשפה שלך.
The phone side is the same everywhere. A computer needs four things to be a Ferry client: join the phone’s Wi-Fi network, run the shared Rust core, capture its own traffic, and point its DNS at the tunnel.
| Windows | macOS | Linux | |
|---|---|---|---|
| Status | V1, in testing | Planned | Planned |
| Join the network | Native Wi-Fi API | CoreWLAN | NetworkManager |
| Capture traffic | Wintun | utun (Network Extension) | TUN |
| DNS to the tunnel | NRPT rule | Resolver config | systemd-resolved |
| Privileged part | Windows service | System extension | systemd service |
The macOS and Linux columns are the expected approach, not decisions yet. Each will get its own design write-up here before code lands. See the roadmap.
Without a client
Section titled “Without a client”The phone has an opt-in SOCKS5 port (1083) for devices with no Ferry client, such as consoles. It carries only apps that support a proxy, and it doesn’t have per-device keys.