enFlowMeshInstall the OpenWrt client

Install the OpenWrt client

After installing FlowMesh on a router, you can join a mesh network through LuCI and choose to share the local LAN or provide an exit node.

Before you begin

Have admin access to the router and the connection details for the target mesh network. The package feed supports OpenWrt 21.02–25.12 on x86_64, aarch64 and armv7 with VFP; MIPS is not supported yet.

OpenWrt uses dedicated packages to manage the service and settings. Don’t run the Linux install.sh on the router.

1. Add the package feed

Sign in to the router over SSH and run:

wget -qO- https://dl.wanflow.com/flowmesh/openwrt/add-feed.sh | sh

The script detects the architecture and package manager, imports the signing public key and adds the package feed. If it reports that the architecture isn’t supported, check the device’s architecture first; don’t force-install packages built for another architecture.

2. Install the packages

OpenWrt 21.02–24.10, which use opkg:

opkg update
opkg install luci-app-flowmesh

OpenWrt 25.12, which uses apk:

apk update
apk add luci-app-flowmesh

luci-app-flowmesh also installs flowmesh. If you only need the command line, install flowmesh instead.

3. Connect in LuCI

  1. Open 服务 → FlowMesh (Services → FlowMesh).
  2. Paste the Linux install command generated in the console into the connection screen, or enter the mesh address and auth key manually. Here LuCI reads the connection details; you are not running the Linux install script in the router’s terminal.
  3. Enter a device name, for example office-gw, and click 接入 (Connect).
  4. Confirm the device is online in LuCI or the console.

Check from the command line:

flowmesh status
flowmesh ip

4. Share the LAN

First confirm which LAN subnet you want remote devices to reach, then turn on 共享本地局域网 (Share local LAN) in LuCI. The package configures a flowmesh firewall zone and bidirectional forwarding between it and lan; also check the range allowed by the mesh network’s access policy.

After the routes are advertised, an admin still needs to approve them, and the accessing devices need to accept subnet routes. See Subnet routes for the full process.

Where settings are stored

/etc/config/flowmesh stores the router settings and /etc/flowmesh/ stores the node identity. Make changes through LuCI where possible; settings applied directly with flowmesh set may be overwritten by the UCI configuration the next time the service reloads.

For example, to persistently enable “accept routes advertised by other nodes” from the command line:

uci set flowmesh.main.accept_routes='1'
uci commit flowmesh
/etc/init.d/flowmesh reload

By default the router lets dnsmasq continue to manage DNS, so don’t copy the Linux approach of taking over /etc/resolv.conf.

Update and uninstall

opkg systems:

opkg update
opkg upgrade flowmesh luci-app-flowmesh

apk systems:

apk update
apk upgrade flowmesh luci-app-flowmesh

To uninstall, use opkg remove luci-app-flowmesh flowmesh on opkg systems or apk del luci-app-flowmesh flowmesh on apk systems. The node identity directory is kept; to revoke the device’s access, also log out or remove the device in the console.

Firmware upgrades keep the FlowMesh configuration and node identity but usually don’t keep additionally installed packages. After upgrading, add the package feed again and reinstall the packages; the device can reconnect using the preserved identity.