enFlowMeshCore concepts

Core concepts

Once you understand the concepts below, you can tell which device a setting should be configured on.

Organizations and mesh networks

An organization manages members and who owns services. A mesh network is the private network that devices actually join. When connecting, use the address and credentials provided by the target mesh network; signing in to the same Wanflow account does not mean two devices are already in the same network.

Devices and mesh IP addresses

Each computer, server or router that joins a mesh network is a node. Its mesh IP address is used for communication within the mesh network and is separate from your home Wi-Fi address, office LAN address and public IP address.

On Linux, run flowmesh ip to see this device’s mesh IP address and flowmesh status to see its peers. Addresses such as 100.64.0.2 in these docs are examples only; use your actual output.

Control server and auth keys

The control server handles node registration, device information and policy distribution. The Linux client must be given --login-server the first time it connects; FlowMesh does not pick a default server automatically.

Auth keys are used to register devices and are different from the node identity a device stores after joining. Revoking an auth key does not remove devices that have already joined. See Access and access control.

Direct connections and relays

With a direct connection, the two ends send encrypted data directly to each other. When a direct connection isn’t possible, a relay helps forward traffic. Communicating through a relay is also a normal connection outcome; the actual path depends on the networks at both ends and the mesh network’s policies.

Subnet routes and exit nodes

FeatureProblem it solvesExample
Device-to-deviceReach devices that have joined the mesh networkA laptop connects to a Linux server
Subnet routesReach a LAN subnetReach 192.168.10.0/24 through the office gateway
Exit nodesHand internet traffic to a specific nodeA laptop reaches the internet through a specific server

Subnet routes require the gateway to advertise the subnet, an admin to approve it, and the accessing device to accept the routes. Exit nodes must be enabled and selected separately; using one does not automatically open up the entire LAN the exit node is on.

DNS and access control

DNS resolves device names to addresses; access control decides whether a connection is allowed. A name that resolves does not mean the port is allowed, and a node showing as online does not mean every service on it is reachable.

Next: Connect two devices.