Platforms and clients
Choose the connection method for your device. The Linux commands in these docs don’t apply to the Windows, macOS, iOS or Android clients.
Choose a connection method
| Device | Connection method | Next step |
|---|---|---|
| Windows / macOS | Wanflow desktop client | Download Center |
| iOS / Android | Wanflow mobile client | Download Center |
| On-site network | Wanflow Cloud Gateway | Add a device to FlowMesh |
| Linux server | Open-source FlowMesh client: install script, deb/rpm or static binary | Linux installation guide |
| OpenWrt router | Open-source FlowMesh client: package feed, with an optional LuCI interface | OpenWrt installation guide |
The FlowMesh client used on Linux / OpenWrt is an open-source project. Source code and documentation are on GitHub.
The Linux install script supports x86_64 and aarch64. The OpenWrt package feed supports OpenWrt 21.02–25.12 on x86_64, aarch64 and armv7 with VFP; MIPS is not supported yet. The release page or package feed is the authority on which packages are available.
Connect computers and phones
- Get the Wanflow client app for your device from the downloads page and install it.
- Sign in with an account that has access to the target mesh network, and select the target organization and mesh network.
- Turn on the connection as the client prompts, and allow the VPN or network extension permission the operating system requests.
- In the console, confirm the device has joined the target mesh network, then access services on existing nodes.
Exact button names may change between client versions. If you can’t see the target mesh network, first check which organization your account belongs to and its mesh network permissions. Don’t paste Linux connection commands into the desktop or mobile clients.
Linux / OpenWrt feature limits
The FlowMesh client provides device-to-device connectivity, subnet routes, exit nodes, DNS, diagnostic commands, and sharing of local HTTP / TCP services. Actual availability also depends on the client version, build options and the configuration pushed by the control server.
Don’t assume the following capabilities behave the same as in other clients:
- Automatic exit node selection:
--exit-node=auto:anyis not supported; you must select a node explicitly. - HTTPS service sharing and public publishing: not currently supported. Shared services should explicitly use HTTP or TCP mode.
- App connectors and hosted services: control server support is currently incomplete, so these are not treated as available features in this guide.
- File transfer between devices: not currently provided by the FlowMesh client.
- SSH server: depends on a build with SSH support and on the control server’s SSH policy; the Linux packages’ default systemd sandbox also needs specific adjustments. Setting
--sshalone is not enough to deploy it. - SSH check delegation and session recording: rules that require these capabilities will deny logins.
- Automatic updates: the client doesn’t upgrade itself. Use the upgrade method for your platform.
These limits apply to the FlowMesh Linux / OpenWrt client described here. They don’t mean other Wanflow clients have exactly the same feature set.