enFlowMeshAccess and access control

Access and access control

Connection credentials determine how a device joins a mesh network; access control determines which resources it can reach after joining.

Both access control and auth keys are configured on the mesh network management page: sign in to the Wanflow Console, click 万联组网 (FlowMesh) in the left navigation, and open the target mesh network.

Access control modes

On the 访问控制 (Access control) tab of the mesh network management page, you can choose the mode at the top of 访问规则 (Access rules):

ModeBehavior
全部互通 (Allow all) (default)All devices in the mesh network can reach each other
自定义规则 (Custom rules)Only the rules listed below are allowed; any access that doesn’t match a rule is denied

In Custom rules mode, a device being online does not mean it can reach every node and port. In either mode, accounts and permissions on the target system itself still need to be managed separately.

Configure access rules

Work out rules from the actual connections your business needs: who needs to reach which device, on which ports. For example, operations staff need SSH access to servers, while other members only need the business web service.

  1. In 访问控制 → 访问规则 (Access control → Access rules), select 自定义规则.

  2. Click 新增规则 (Add rule) in the upper right. Fill in each rule:

    FieldDescription
    启用 (Enabled)Turns the rule on or off
    来源 (Source)First choose a type (for example, terminal), then choose specific objects
    可访问 (Can access)The allowed destinations, for example 所有终端 (All terminals) or specific devices
    端口 (Ports)The allowed ports; supports *, 80,443 and 8080-8090 formats
    备注 (Notes)Optional; describes what the rule is for
  3. Verify allowed connections from the device that actually needs access, and verify that a device that shouldn’t be authorized is denied. Checking whether nodes are online does not verify the access policy.

Rules apply only to devices that have successfully joined the mesh network; when a new device joins, the policy is automatically recalculated and pushed out. The number of rules is limited by the mesh network plan’s quota; 套餐与授权 (Plan and licenses) on the mesh network management page shows how many are used and available.

The left side of 访问控制 also provides 规则测试 (Rule testing) and 版本历史 (Version history), as well as definitions for 用户组(Group) (User groups), 标签(Tag) (Tags), IP sets and Host that can be referenced in rules. To edit the policy text directly, switch to the JSON view.

Manage auth keys

Auth keys let Linux servers join the mesh network. They are managed on the 密钥 (Keys) tab of the mesh network management page:

  • Click 生成密钥 (Generate key) to create a new key. You can also generate one along with the install command when you use 添加终端 (Add terminal).
  • A key whose 属性 (Type) is 一次性 (One-time) can be used only once and suits a single device; a 可重用 (Reusable) key can be used to deploy multiple devices in bulk while it’s valid.
  • 状态 (Status) shows whether a key is valid, used, expired or invalidated. If connecting fails, check the status of the key you used first.
  • To stop a key from registering any more devices, click the revoke icon at the end of its row.
  • Install commands may contain the full key; remove it before sharing screenshots or logs.

Revoking an auth key does not automatically take devices that have already joined offline. If a device is lost or no longer needs access, an admin should also remove the device or revoke its access in the console.

Tags can express what a server is used for. The Linux client can request tags:

sudo flowmesh set --advertise-tags=tag:server

This command sets the list of tags this device advertises; if it already has other tags, list every tag you want to keep, separated by commas. Whether a tag is granted is decided by the control server’s policy; a client requesting a tag does not mean it was granted.

Temporarily block incoming connections

When a Linux device needs to block new incoming connections while still receiving responses to connections it initiates:

sudo flowmesh set --shields-up=true

To go back to handling incoming connections according to the mesh network policy:

sudo flowmesh set --shields-up=false

This is not a port-level access rule editor. If you only want to restrict a particular service, adjust the mesh network access rules and the target host’s firewall.

Temporarily disconnect and log out

ActionResult
sudo flowmesh downStops the connection; keeps the login and settings
sudo flowmesh logoutContacts the control server to log out the current node, and restores default settings
Revoke the auth key in the consolePrevents the key from registering more devices; existing devices are unaffected

logout requires the control server to be reachable. If it fails, don’t assume the device identity on the server side has been invalidated; check and complete the revocation in the console.

On OpenWrt, manage the connection and configuration through LuCI where possible. For permission troubleshooting, see Troubleshooting.