Web interface documentation
qMp 4.0 Macondo
Device configuration => qMp easy setup
The Device configuration => qMp easy setup page provides a fast and simple wizard that helps configuring a qMp device with the minimum information possible for most of the typical and most common applications. It is divided into the following sections:
- Device identification
- Node mode and mesh-wide public IPv4 address
- Network interfaces
Device identification
Device name
The device name is used both to define the hostname of the router and to distinguish it from other devices participating in the mesh network. Leaving this field blank will make the device be given the default name.
During the first boot after installing qMp, devices are automatically given the default name "qMp-xxxx", where xxxx corresponds to the last four digits of the primary Ethernet interface (eth0) MAC address. For example, if a device has the MAC address 44:0D:C5:1D:3A:D7 on the primary Ethernet interface, it will be named by default "qMp-3ad7".
From a technical point of view, device names do not need to be unique in a qMp mesh network. However, it is advised not to repeat in order to ease the network management.
Community network details (optional)
qMp is often used in the context of community networks. If this is the case, you can select which community network the device belongs to from a predefined list, write a custom name for your own community network deployment or just leave it blank.
Some community networks, such as Guifi.net and tools shipped with qMp like LibreMap require this setting to be properly configured in order to work. In the specific case of Guifi.net, the specific mesh subnetwork and the device ID can also be configured.
Node mode and mesh-wide public IPv4 address
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 IPv4 address and network mask
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.
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).
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.
Network interfaces
Wired network interfaces
In qMp, wired interfaces (i.e., Ethernet interfaces) can be assigned the LAN or WAN role (or none of them).
A wired interface configured in LAN mode is used to provide network connectivity to local end-user devices. All the interfaces configured as LAN are added to the virtual br-lan interface (i.e. the LAN bridge), where a DHCP server is enabled to assign IP addresses and a default gateway to the end-user devices connected.
The WAN mode is used on wired interfaces connected to a gateway, for example, an Internet up-link or a connection to another network. Each wired interface configured in WAN mode runs a DHCP client and expects to obtain an IP address from a remote server.
A wired interface can only be assigned one of the LAN or the WAN roles at a time. If a wired interface interface is not assigned any role (i.e. None mode), it is neither used as LAN nor as WAN by qMp.
In some specific cases (usually, when two routers running qMp are deployed at the same physical location but are working on different wireless channels), devices can be interconnected between them via cable in order to expand the mesh. This is very common in the core nodes of big community network deployments. For these cases, a wired interface can be used to expand the mesh network via cable, in addition to being configured in the LAN or WAN roles (or none).
Wireless network interfaces
Wireless interfaces (i.e., WiFi) in qMp can be assigned different roles, or combinations of them. They can be used to join and expand the mesh network, to provide connectivity to end users, or combinations of both.
The following configurations are available to join a mesh network and expand it via WiFi:
-
The Ad hoc (mesh) mode is used to link, via wireless ad hoc, with other mesh nodes also operating in ad hoc (mesh) mode and expand the mesh network
-
The 802.11s (mesh) mode is used to link, via wireless 802.11s, with other mesh nodes also operating in 802.11 (mesh) mode and expand the mesh network
-
The AP (mesh) mode is used to create an access point for linking, via wireless AP-client infrastructure, with other mesh nodes operating in Client (mesh) mode and expand the mesh network
-
The Client (mesh) mode is used to connect to an access point for linking, via wireless AP-client infrastructure, with another mesh nodes operating in AP (mesh) mode and expand the mesh network
The following configurations are available to provide connectivity to end-user devices, or to connect to an access point and obtain connectivity to another network via WiFi:
-
The AP (LAN) mode is used to generate an access point for end-user devices. The wireless interface is added to the virtual br-lan interface (i.e. the LAN bridge), where a DHCP server is enabled to assign IP addresses and a default gateway to the end-user devices connected.
-
The Client (WAN) mode is used to connect the qMp device to a WiFi access point and get connectivity to another network via WiFI (e.g. to an Internet up-link)
Additionally, the following modes combinations are available:
-
Ad hoc (mesh) + AP (LAN) combines both modes on a single interface
-
802.11s (mesh) + AP (LAN) combines both modes on a single interface