Web interface documentation
qMp 4.0 Macondo
Device configuration => Network settings => Basic network settings
The Device configuration => Network settings => Basic network settings page allows to configure the basic network settings of a qMp device, like the node mode or the mesh-wide public IPv4 address. It is divided into the following sections:
- Node mode
- Mesh-wide public and private LAN IPv4 addresses (natted mode) or Mesh-wide public IPv4 address and network mask (public mode)
Node mode
Node mode
This option defines whether qMp makes the devices connected to the LAN interfaces of the node visible to the rest of the mesh network or hidden behind a NAT.
In public mode the qMp node is configured with a mesh-wide accessible IP address and subnetwork (e.g. 10.99.99.1/24). All the end-user devices (computers, laptops, smartphones, access points, servers, etc.) connected to the LAN interfaces of the node obtain are assigned a mesh-wide public IP address (10.99.99.100/24, 10.99.99.101/24, 10.99.99.102/24, etc.). Therefore, they can be reached or accessed from other devices anywhere in the mesh network. This mode is usually the preferred one in planned, static, long-term deployments such as community networks, where users want to make their devices reachable to other users in order to share services, contents or resources.
In natted mode the qMp node is configured with a single mesh-wide accessible IP address (e.g. 10.99.99.1/32). All the end-user devices (computers, laptops, smartphones, access points, servers, etc.) connected to the LAN interfaces of the node are assigned a private IP address (172.30.22.100/16, 172.30.22.101/16, 172.30.22.102/16, etc.) which is only reachable locally. Therefore, they can not be reached or accessed from other devices anywhere in the mesh network. This mode is used to create a local, private network that can connect to the rest of the mesh network, but that remains hidden to the rest of the mesh, or in quick, short-term or ephemeral deployments.
WARNING:
In public mode, end-user devices connected to the node are directly exposed to the mesh network. In natted mode, end-user devices connected to the node are hidden from the mesh network, but this is not a sufficiently secure mechanism to prevent them from being accessed from the rest of the mesh network. In both cases, make sure end-user devices they are properly protected against malicious users.
Mesh-wide public and private LAN IPv4 addresses (natted mode)
qMp nodes use mesh-wide public IPv4 addresses in order to allow end-user devices to reach and communicate with other mesh nodes and devices, access to content, resources and services or connect to the Internet. These mesh-wide public IPv4 addresses must be unique in a mesh network deployment. In order to avoid collisions in the addresses space, which may lead to some services or connections not function properly, it is advised to perform a minimum planning beforehand.
Mesh-wide public IPv4 address
In natted mode, a qMp device has a single, unique, mesh-wide public IPv4 address with a /32 netmask (e.g. 10.99.99.1/32), which can be reached from within any other device of the mesh. A specific address can be configured in this section or, if left blank, a random one is assigned (which is specially useful in quick deployments where having connectivity as soon as possible is a priority).
Private LAN IPv4 address
[WiP]
Private LAN IPv4 netmask
[WiP]
Mesh-wide public IPv4 address and network mask (public mode)
qMp nodes use mesh-wide public IPv4 addresses in order to allow end-user devices to reach and communicate with other mesh nodes and devices, access to content, resources and services or connect to the Internet. These mesh-wide public IPv4 addresses must be unique in a mesh network deployment. In order to avoid collisions in the addresses space, which may lead to some services or connections not function properly, it is advised to perform a minimum planning beforehand.
Mesh-wide public IPv4 address
In public mode, a qMp device manages a unique, mesh-wide public IPv4 subnetwork (e.g. 10.99.99.0/24) and has an IPv4 address within that subnetwork (e.g. 10.99.99.1/24). The whole subnetwork can be accessed from within any other device of the mesh network. Since in public mode the network is assumed to be planned before the actual deployment, in this case it can not be left blank.
IPv4 subnetwork mask
[WiP]