> For the complete documentation index, see [llms.txt](https://docs.morsemicro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morsemicro.com/application-notes/appnote-32-how-to-configure-802.11s-mesh.md).

# APPNOTE-32 How to Configure 802.11s Mesh

[Download as PDF](https://www.morsemicro.com/resources/appnotes/MM_APPNOTE-32_How_to_configure_802.11s_Mesh.pdf)

## 1 Scope

This application note provides a guide on configuring and verifying using the 802.11s Mesh feature on Morse Micro OpenWRT products.

This document outlines the configuration of an 802.11s Mesh network designed to provide backhaul connectivity for 802.11bgn Wi-Fi and LAN connections through 802.11ah HaLow links. The described scenario serves as a representative reference configuration. Please note that the latency and throughput of the network will depend on the 802.11ah link performance and the number of hops in the mesh.

The prerequisites for this application note are:

* 2 x [Morse Micro](https://www.google.com/url?q=https://www.morsemicro.com/end-products/\&sa=D\&source=editors\&ust=1783414770558592\&usg=AOvVaw0s3GXqmH-aKIdVbG-hToxv) [HaLow](https://www.google.com/url?q=https://www.morsemicro.com/end-products/\&sa=D\&source=editors\&ust=1783414770558704\&usg=AOvVaw333llVZQTWYGwTVpcS7RyD)[Link1](https://www.google.com/url?q=https://www.morsemicro.com/end-products/\&sa=D\&source=editors\&ust=1783414770558765\&usg=AOvVaw21RQ1RjXk2qPQsy_uUzkkg) devices, with the latest software installed (this guide was written based on v.2.7.3).[\[1\]](#ftnt1)
* 1+ x additional [Morse Micro HaLowLink1](https://www.google.com/url?q=https://www.morsemicro.com/end-products/\&sa=D\&source=editors\&ust=1783414770559110\&usg=AOvVaw0e1tPdOPf75Ji-anReNZ2X) devices are required to test meshing behaviour such as self-healing and dynamic route finding.
* 1 x laptop with ping, and traceroute installed.
* 1 x internet connection accessible via 2.4GHz Wi-Fi with access credentials known.
* Familiarity with accessing and configuring Morse Micro HaLowLink1 devices, as per the User Guide.

By following this application note you will learn:

* How to configure HaLowLink1 devices to setup an 802.11s mesh;
* How to validate the mesh is operating; and
* How to validate that the mesh is self-healing.

***

## 2 Theory of Operation

802.11s Mesh is a Wi-Fi feature that allows multiple wireless devices to “interconnect to create a[wireless LAN](https://www.google.com/url?q=https://en.wikipedia.org/wiki/Wireless_LAN\&sa=D\&source=editors\&ust=1783414770560931\&usg=AOvVaw1BYODfbuKIW1r4POhFI1Bz) mesh network”. \[[link](https://www.google.com/url?q=https://en.wikipedia.org/wiki/IEEE_802.11s\&sa=D\&source=editors\&ust=1783414770561049\&usg=AOvVaw00HFe5gAAzE8y10yYWKWnA)] This can be used to extend the area covered by a network by creating wireless links that manage the multiple paths between nodes and is capable of automatically recovering connectivity and dynamically adjusting routes in response to environmental changes..

This application note uses multiple HaLowLink1 devices to create an 802.11s mesh network over the 802.11ah HaLow radios. This application note chooses to target a network that:

* uses an 802.11bgn 2.4 GHz radio as a client connecting to a Wi-Fi hotspot running on mobile phone for uplink to the internet
* provides a laptop access to the internet via 802.11bgn 2.4 GHz Access Points that are backhauled by the 802.11s mesh network via the 802.11ah HaLow radios.

Note: an 802.11s mesh network can extend any network over wireless; can use Ethernet or other wireless for internet access; and can use Ethernet or other wireless as the means for accessing the mesh. This application note chooses the above topology to remove options in order to simplify the guide.

The target network architecture from the choices above is shown below:

![](/files/bc248767fe0a5c6e1be07c55c82487b619c2ab7d))

This network will demonstrate that from a laptop connected to Device 2 via 2.4GHz Wi-Fi can communicate to the internet via the 802.11ah Mesh network.

The physical devices will be moved (or mesh thresholds changed) so the network topology changes to rely on a network path through Device 3, as shown in the diagram below:

![](/files/ea81836b02a084317b99f7b1c2981ce9a4b16e6c))

This topology will demonstrate the mesh self-heals, and will validate that the laptop connected to the 802.11bgn 2.4 GHz can still communicate to the internet via the mesh network.

## 3 How to Configure

This guide covers two different ways to configure 802.11s mesh in HaLowLink1 devices:

1. An approach that uses the UI Wizard and push button DPP (Device Provisioning Protocol). This is the easiest method.
2. An approach that uses manual configuration via the UI. This is more involved, but is more tailorable.

Both approaches configure the following:

* A single device (Device 1) is configured as the Mesh Gate - i.e. the device that provides integration to another distribution system. This device uses its 2.4GHz radio for uplink to an existing Wi-Fi network that has an internet connection.
* A number of devices (e.g. Device 2, Device 3) that are configured as mesh nodes. These devices use their 802.11ah HaLow radio to participate in the mesh, and use their 802.11bgn 2.4GHz radio to provide an Access Point.

Both approaches are documented below.

Note: This guide does not cover setting regulatory domain, or channels for these devices. It is assumed you have set this correctly and are otherwise using the devices with factory defaults.

Refer to the HaLowLink1 User Guide for detailed instructions regarding proper configuration of regulatory domain and wireless channels.

***

### 3.1 Recommended Approach - Configuring HaLowLink1 via Wizard and Push Button

#### 3.1.1 Overview

The HaLowLink1 device supports configuring an 802.11s Mesh and adding Extender devices to the mesh via a UI Wizard and DPP push buttons. This is the easiest way to configure an 802.11s mesh network.

Pre-requisites:

* 2 x HaLowLink devices, loaded with the latest software (2.7.3+)
* Additional HaLowLink1 devices are required if you would like to test a multi-hop mesh and/or mesh self-healing.
* 1 x laptop
* 1 x mobile phone with Wi-Fi hotspot capability and an internet connection

The high-level network architecture is shown in the diagram below:

![](/files/c3ec132ec77ef2b370efd315caf9c65104ff3e75))

* Device 1 will provide the uplink to the internet by connecting as a client to the mobile phone’s “uplink” hotspot. Device 1 will operate as a Mesh Gate in the 802.11s mesh.
* Device 2 will connect to the 802.11s mesh, will operate as a node in the 802.11s mesh, and will also operate an 802.11bgn Access Point.
* The laptop will connect as a client to the 802.11bgn Access Point from Device 2, and will be able to reach the internet by having traffic travel over the mesh to Device 1, and then via the mobile phone to the internet.

***

#### 3.1.2 Step-by-step guide for Wizard and Push Button approach

The following is a step by step guide to configure and validate a mesh network. The two devices used as examples are HaLowLink1s with the following:

* Device 1 - SSID: halowlink1-af0f
* Device 2 - SSID: halowlink1-ae6b

To provide an uplink for this guide, determine the SSID and password of your 2.4GHz uplink (this guide uses a phone hotspot configured with SSID: uplink and Password: uplink-password).

**Step 1: Configuring Device 1 as a Mesh Gate**

1. Connect your laptop to Device 1 via its 802.11bgn 2.4 GHz (e.g. Wi-Fi SSID halowlink1-af0f, password printed on device label )
2. Access the web UI at [http://192.168.12.1](https://www.google.com/url?q=http://192.168.12.1\&sa=D\&source=editors\&ust=1783414770569146\&usg=AOvVaw35XASRN1eRJj6mEBp4BTfH), login using the “Device Password” (printed on device label) and select the “Wizard” from the menu (direct [link](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/morseapwizard\&sa=D\&source=editors\&ust=1783414770569382\&usg=AOvVaw3vZs6JKv4CAWOjMmD3EKi7))
3. Choose HaLow Mode: 802.11s Mesh and Network Mode: “...use 2.4 GHz for an uplink”\
   ![](/files/e08c7e14d2c7013e5d13188c774016b09378bd80))
4. Click “Save and apply”
5. The device is now running an Access Point and Mesh Point on its 802.11ah radio and is still running an Access Point on its 802.11bgn radio. The device’s Wi-Fi SSID (halowlink1-af0f) is used as the Access Point SSID, and the Mesh ID.
6. Go to Home ([http://192.168.12.1/cgi-bin/luci/admin/home](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/home\&sa=D\&source=editors\&ust=1783414770570106\&usg=AOvVaw09WItrMrxO0dJ-Q9xjC65-))
7. Find the Uplink(2.4GHz) card, which should say “Disconnected”
8. Click the word “Disconnected” and provide the uplink network details (uplink / uplink-password)\
   ![](/files/86adeaad20d6ff544f0ae81b01af4e1aa9924254))

**Step 2: Validating Internet Connectivity on Device 1**

Device 1 should now provide uplink to the internet via the configured 2.4 GHz uplink network. Steps to validate are:

1. Connect to Device 1’s 2.4 GHz Access Point (halowlink1-af0f) with your laptop.
2. Check you can reach the internet (i.e. load [www.morsemicro.com](https://www.google.com/url?q=http://www.morsemicro.com\&sa=D\&source=editors\&ust=1783414770571124\&usg=AOvVaw07biGoHSZKEgRfd9K9h9Ms) in your browser).\
   Note: Please ensure that your laptop is not connected to the internet via another network during this test.

**Step 3: Configuring Device 2 as a Mesh Extender**

For more information, see the “HaLow extender” section in the HaLowLink1 User guide.

1. Put Device 2 into Extender mode by holding down the physical push button until the status light flashes aqua (i.e. 10+ seconds).
2. Wait for Device 2 to reboot into Extender mode (i.e. Status LED is solid Aqua)
3. Pair Device 2 with Device 1 by doing the following:
4. First press and release button on Device 1 to put it into pairing mode (Wi-Fi HaLow Status LED slowly blinks)
5. Press and release button on Device 2 to pair it with Device 1 (Wi-Fi HaLow Status LEDs should slowly blink in both devices).
6. Wait 30+ seconds, and both devices' HaLow status light should stop slow flash, and show solid/blinking traffic.

**Step 4: Validating Mesh Connectivity on Device 2**

Device 2 should now provide uplink to the internet via Device 1. Steps to validate are:

1. Connect to Device 2’s 2.4 GHz Access Point (halowlink1-ae6b) with your laptop
2. Check you can reach the internet (i.e. load [www.morsemicro.com](https://www.google.com/url?q=http://www.morsemicro.com\&sa=D\&source=editors\&ust=1783414770573091\&usg=AOvVaw0iLZp6qMgYT5PbDWIb2mFB) in your browser)

You now have a functioning 802.11s mesh network.

 

**Configure and Validate Additional Devices (e.g. Device 3)**

Additional devices (e.g. Device 3) are configured and validated using the same steps as for Device 2.

Repeat the “Device 2” process for Device 3 to add another Extender to the mesh. Test the self-healing behaviour of the mesh by moving Device 2 out of range of Device 1, and/or by adjusting the “RSSI threshold for joining” mesh setting (see Troubleshooting section for more information).

Note: If testing on your desk, we recommend a cabled test setup with the appropriate attenuation and RF splitter/hubs for the thresholds you set.

***

####

#### 3.1.3 Detailed explanation for Wizard and Push Button configuration

The following annotates the prior diagram with more details from the example configured, including the 802.11 mesh terminology (as per [Certified Wireless Network Professional 802.11s Mesh guide](https://www.google.com/url?q=https://www.cwnp.com/uploads/802-11s_mesh_networking_v1-0.pdf\&sa=D\&source=editors\&ust=1783414770574837\&usg=AOvVaw2c7Qa2fHFpBThM1NtcFyZ9)):

![](/files/168e926a6094c25a6aa8cefb0a3dc4efc7d0cf53))

The points to note are:

* Both Device 1 and Device 2 participate in the 802.11s Mesh as Mesh Stations. The Mesh ID and settings come from the Device 1 configuration, and are distributed to Device 2 via DPP (push button).
* Device 1 is configured to have a static address 192.168.12.1 and to operate a DHCP server on the lan network (i.e. the mesh; its 802.11bgn 2.4 GHz Access Point; and LAN and USB LAN ports). This is identical to the out-of-the-box configuration for a HaLowLink1.
* Device 2 is configured to obtain its address via DHCP. It also has all physical ports (LAN, USB LAN, and WAN), and its 802.11bgn 2.4 GHz Access Point into its lan network.
* I.e. connecting to any physical port or the Access Point in Device 2 will provide access to the internet via the mesh->Device1->phone hotspot->phone internet connection.

This is a detailed diagram of the two devices, and the resulting configuration from an OpenWRT perspective:![](/files/460c0efa07c32c403c461010f4e19d293798b05b))

### 3.2 Advanced Approach - Configuring via UI without Wizard

#### 3.2.1 Overview

The HaLowLink1 supports 802.11s and can be configured without relying on the wizard and push button pairing. This process is more complex. There are many inter-related settings which must be correct - setting incorrect configuration parameters may result in temporary loss of device connectivity or administrative access..

NOTE: We expect this process to be followed by users familiar with configuring 802.11s mesh networks and/or users that are experimenting with 802.11s. It is expected that occasional connectivity issues may occur as part of the learning process. A common cause is being unable to determine the IP address of a device because it changes from using a static IP address to a DHCP provided IP address. See Troubleshooting for more guidance.

Common objections to the Wizard and Push Button configuration are:

1. It does not have the SSIDs I want in all of the devices.
2. It does not have an 802.11ah HaLow Access Point as well as an 802.11bgn 2.4 GHz Access Point in all of the devices.
3. I do not know how to incorporate this with other 802.11ah HaLow products that support 802.11s meshing.

We will address points 1 and 2 in this section. Point 3 is out of scope for this document, but will be similar to the configuration performed in this guide.

Note: This section will perform the full configuration from scratch via the UI - but the approach is similar to adjust the configuration from the previous Wizard and Push Button section to address the objections.

***

#### 3.2.2 Requirements for the example via UI

The Wizards and Push Button example ignored some of the requirements from the original plan for ease of use. This example will use requirements from an expected IoT deployment where:

* REQ1 - There are existing 2.4 GHz only Wi-Fi IoT devices that are configured as clients with SSID: “ot-network” and Password: “ot-network-password”.
* REQ2 - These 2.4 GHz only devices are geographically dispersed, and we want to use an 802.11ah HaLow mesh to provide coverage to them, so our 2.4 GHz Access Points must use this SSID.
* REQ3 - There are also 802.11ah Wi-Fi IoT devices configured as clients with the same ‘ot-network’ configuration, and we also want the mesh to provide coverage to them.
* REQ4 - At the uplink we do not want the uplinking mesh device to also run any 802.11bgn 2.4GHz Access Points, as these will add unnecessary interference, but we do want to run an 802.11ah Access Point at the uplink mesh device.

The conceptual architecture for this example is below. Note it includes “IoT Devices” which we will not cover in this guide:![](/files/f380f43136a90b3d2a19ff6171925d461de190ba))

And this is a detailed diagram of the network, including the two HaLowlink devices we will configure :![](/files/109f4cdff02596d072ad78087866808ef1192ea5))

#### 3.2.3 Step-by-step guide for configuring entirely via UI

The following is a step by step guide to configure and validate a mesh network. The two devices used as examples are HaLowLink1s running v2.7.3 with the following:

* Device 1 - SSID: halowlink1-af0f
* Device 2 - SSID: halowlink1-ae6b

To provide an uplink for this guide, determine the SSID and password of your 2.4GHz uplink (this guide uses a phone hotspot configured with SSID: uplink and PW: uplink-password).

**Configure Device 1 to have 2.4 GHz uplink to internet**

1. Connect your laptop to Device 1 via its 802.11bgn 2.4 GHz\
   (e.g. Wi-Fi SSID halowlink1-af0f)
2. Access the web UI at [http://192.168.12.1](https://www.google.com/url?q=http://192.168.12.1\&sa=D\&source=editors\&ust=1783414770581942\&usg=AOvVaw3jhUBa-7mntWNpoByOI_Fs), login using the “Device Password”
3. Select Quick Config page (you may have to toggle “Advanced Config”)\
   ([http://192.168.12.1/cgi-bin/luci/admin/config](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/config\&sa=D\&source=editors\&ust=1783414770582237\&usg=AOvVaw2DUNpEPZcsw3nZoT4Yrsfb))
4. Add a new wireless device to the 802.11b/g/n radio\
   ![](/files/01cdbd5f89ce17800276bd46e3ff8791381434a0))
5. Input the following details:
6. Ensure ‘enabled’ is selected
7. Network: wan
8. Mode: client
9. ESSID: uplink
10. Encryption: Match the security protocol exactly to that configured on the uplink hotspot (commonly WPA2-PSK).
11. Key/Security: uplink-password
12. Remove the wan Ethernet device from the wan network by deselecting ‘wan’ in the Ethernet dropdown.\
    ![](/files/3d5fbbd27e2fc3f7dcd65d7809c7e92dbfbfb018))
13. Click Save & Apply

Validate Device 1 has an internet 2.4 GHz uplink

1. Ensure your hotspot is enabled.
2. Connect to Device 1’s 2.4 GHz Access Point (i.e. halowlink1-af0f) with your laptop.
3. Check you can reach the internet (i.e. load [www.morsemicro.com](https://www.google.com/url?q=http://www.morsemicro.com\&sa=D\&source=editors\&ust=1783414770583606\&usg=AOvVaw3pGn2Vh7QaKkOyDQBlJzWD) in your browser).

**Troubleshooting**

* If you cannot see your device’s 802.11bgn 2.4 GHz Access Point, it may be that your hotspot is unavailable or the device has incorrect parameters.
* The HaLowLink1 only brings up its 802.11bgn 2.4 GHz Access Point after its 802.11bgn 2.4 GHz client successfully connects to the ‘uplink’ SSID.

**Configure Device 1 to have 802.11ah Access Point with “ot-network” SSID**

4. Select Quick Config page\
   ([http://192.168.12.1/cgi-bin/luci/admin/config](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/config\&sa=D\&source=editors\&ust=1783414770584502\&usg=AOvVaw2lEPhPTmia0BHJ4eCR7zRm))
5. Change the settings for the existing Access Point for the 802.11ah radio
6. ESSID: ot-network
7. Key/Security: ot-network-password

![](/files/bda70eb7be4a9f03f6453da0e7aed49bc86b3909))

6. Click “Save & Apply” (note you might lose connection and need to reconnect)

**Configure Device 1 to have 802.11ah Mesh Point with “ot-mesh” SSID**

7. Select Quick Config page\
   ([http://192.168.12.1/cgi-bin/luci/admin/config](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/config\&sa=D\&source=editors\&ust=1783414770585308\&usg=AOvVaw1bKy-zsYnbuK9J0BW2pPFl))
8. Add a new wireless device to the 802.11ah radio\
   ![](/files/fbecf74fc9b782cb724492f313c23b4fc94d9c42))
9. Input the following details:
10. Enabled: true
11. Network: lan
12. Mode: Mesh Point (Note: this is called 802.11s mesh in Network > Wireless config page)
13. MeshId: ot-mesh
14. Encryption: WPA3-SAE
15. Key/Security: ot-mesh-password

![](/files/84c460a385c3f62443f445ec6677010154cd4952))

10. Click “Save & Apply” (note you might lose connection and need to reconnect)

***

**Validate Device 1 802.11ah configurations**

We cannot validate the 802.11ah mesh is working yet, but we can validate by inspecting the expected configuration on the Network > Wireless page\
([http://192.168.12.1/cgi-bin/luci/admin/network/wireless](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/network/wireless\&sa=D\&source=editors\&ust=1783414770586755\&usg=AOvVaw2kRi1tiJLJ1yGW1scESSa7)).

![](/files/6c8ab5466a8b4388fd530398aa5472bd5efd3a8e))

Note that we have not met REQ4 yet, and are keeping the 802.11bgn 2.4 GHz Access Point configured now to maintain access to Device 1.

***

**Configure Device 2 to have ‘ot-network’ for Access Point on both 802.11bgn and 802.11ah radio**

11. Connect your laptop to Device 2 via its 802.11bgn 2.4 GHz (e.g. Wi-Fi SSID halowlink1-ae6b)
12. Access the web UI at [http://192.168.12.1](https://www.google.com/url?q=http://192.168.12.1\&sa=D\&source=editors\&ust=1783414770587567\&usg=AOvVaw3_SjcgmNU9bFcXN6c8NWU_), login using the “Device Password”.
13. Select Quick Config page (you may have to toggle “Advanced Config”)\
    ([http://192.168.12.1/cgi-bin/luci/admin/config](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/config\&sa=D\&source=editors\&ust=1783414770587958\&usg=AOvVaw2ibMdoUTDoRhptvonvbZHq))
14. Change the settings for the existing Access Points for both the 802.11ah and 802.11bgn radios
15. ESSID: ot-network
16. Key/Security: ot-network-password

![](/files/84d33861f874a654a576b80289d46fcb03d1dd53))

15. Click “Save & Apply”. You will lose connection to Device 2, as its SSID will change from the device default to “ot-network”.

Reconnect to Device 2 using “ot-network / ot-network-password”.

***

**Configure Device 2 to have 802.11ah Mesh Point with “ot-mesh” SSID**

1. Select Quick Config page\
   ([http://192.168.12.1/cgi-bin/luci/admin/config](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/config\&sa=D\&source=editors\&ust=1783414770589051\&usg=AOvVaw2C6xIHlyK_Q0D6tedhJ8N5))
2. Change the lan network to have:
3. DHCP Server: Disabled
4. Protocol: DHCP Client

![](/files/e017b6a183d9566eccd4b18a81dcb3aaf9e84802))

3. Add a new wireless device to the 802.11ah radio\
   ![](/files/fbecf74fc9b782cb724492f313c23b4fc94d9c42))
4. Input the following details:
5. Enabled: true
6. Network: lan
7. Mode: Mesh Point (Note: this is called 802.11s mesh in Network > Wireless config page)
8. MeshId: ot-mesh
9. Encryption: WPA3-SAE
10. Key/Security: ot-mesh-password

![](/files/84c460a385c3f62443f445ec6677010154cd4952))

5. Click “Save & Apply” (note you might lose connection and need to reconnect).
6. You will be warned about a connectivity change. Choose “Apply and keep settings”.\
   ![](/files/0d13d1af7386b407ac95ef6f79bcc725e92673d9))

Note: We will likely lose connectivity for longer than 90 seconds, as Device 2 will get a new IP from Device 1’s DHCP server, but it will take time for us to determine it and get back into the UI.

**Validate Device 2 configurations and the mesh network**

We have now configured the mesh with two devices, where your laptop has connectivity to the internet.

Before we validate, you must check:

* The “uplink” hotspot is up and has an active internet connection
* Device 1 is powered on (and has all three status lights on - Status & Wi-Fi 2.4 GHz green; Wi-Fi HaLow purple)
* Device 2 is powered on (and has all three status lights on - Status & Wi-Fi 2.4 GHz green; Wi-Fi HaLow purple)
* Your laptop is connected to the “ot-network” SSID (i.e. the one provided by Device 2)

Check connectivity to Device 1

Go to [http://192.168.12.1](https://www.google.com/url?q=http://192.168.12.1\&sa=D\&source=editors\&ust=1783414770591776\&usg=AOvVaw3JqFVrMBapZt_OaiPdLatE) and login with Device 1’s credentials.

* Your laptop is connecting to Device 1 through the following path:

  laptop -> “ot-network” 2.4 AP -> Device 2 -> “ot-mesh” link -> Device 1

If you cannot connect to Device 1, please refer to the troubleshooting section

Check connectivity to the Internet

Go to [www.morsemicro.com](https://www.google.com/url?q=http://www.morsemicro.com\&sa=D\&source=editors\&ust=1783414770592394\&usg=AOvVaw0vSfGhVvrxK_3kGCTELN6r) in your browser.

* Your laptop is connecting to the internet through the same path as to Device 1

Examine traceroute from laptop to see hop via Device 1

Running traceroute 8.8.8.8 (i.e. a Google DNS server) you can see that the first hop is via the 192.168.12.1 link.

![](/files/c59479e9053cf52f80fcd1a8dbb28692526f1aee))

Inspect DHCP leases in Device 1 to determine Device 2’s address

Login to Device 1’s UI, and go to Home\
([http://192.168.12.1/cgi-bin/luci/admin/home](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/home\&sa=D\&source=editors\&ust=1783414770593643\&usg=AOvVaw02RHgtKakoSG93pHVtD1IP)).

Click on “DHCP Leases”, and look for the MAC address of Device 2. For example, here is the table for the two devices used throughout this guide:\
![](/files/371209f31fbb413ef4111c15661ae7bf580d8019))

Use the IP address found here to get to the UI of Device 2.

**Configure and validate Device 3**

To configure another device, follow the same steps as for Device 2. Any device configured this way will join the mesh network and behave just like Device 2.

***

## 4 Troubleshooting

I’m connected to my device, but I don’t know its IP address. How do I find it?

There are a few techniques:

Method A: Using DHCP Server Leases

1. Log into the device that is running the DHCP server and go to the Home page\
   ([http://192.168.12.1/cgi-bin/luci/admin/home](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/home\&sa=D\&source=editors\&ust=1783414770595817\&usg=AOvVaw0JhFHyGRUoBbf8p1vFSG_h)).
2. Click on “DHCP Leases”, and look for the MAC address of the device you want to find.

Method B: Accessing via Debug IP (10.22.121.111)

1. HalowLink1 devices bind a static IP address 10.22.121.111/31 for retaining debug access.
2. Add a static IP address to your laptop’s network connection: 10.22.121.110/31 (i.e. with netmask 255.255.255.254)
3. Connect to the debug IP address 10.22.121.111, ensuring your laptop is only connected to one device.

I am unable to separate the HaLowLink1 devices sufficiently to test mesh self-healing. What can I do?

This is expected, as HaLow’s strength is the extended range! You can see the performance of the mesh in two ways:

1. Move Device 1 and 2 far enough apart that they cannot communicate, so you know they are communicating via Device 3.
2. Move Device 1 and 2 far enough apart so their throughput is low, and see that introducing Device 3 improves the throughput.

To achieve “move the devices further apart”, there are a few options:

* Physically separating the devices - though this is very impractical for a demo;
* Separating the devices in RF isolation chambers with controllable attenuation;
* Configuring the “RSSI threshold for joining” mesh advanced option - which will prevent stations for joining a mesh if they are below the threshold; and
* Configuring the “mesh\_max\_peer\_links” mesh setting - which will restrict the number of peers a node has.

Providing physical or RF separation is out of the scope of this document.

***

To adjust the Mesh RSSI threshold for joining:

* Go to Network > Wireless settings\
  ([http://192.168.12.1/cgi-bin/luci/admin/network/wireless](https://www.google.com/url?q=http://192.168.12.1/cgi-bin/luci/admin/network/wireless\&sa=D\&source=editors\&ust=1783414770600008\&usg=AOvVaw1r0egSJ3LtwyZH1PbSP1k6))
* Click “Edit” on the “ot-mesh” device
* Update the RSSI threshold for joining under “Mesh Settings”\
  ![](/files/caca748eefd25d7f383bce8ec23993af160b43eb))

This threshold determines the minimum RSSI a node must see to establish a peer connection in the mesh. A value of 0 means “peer with any device”. A value of -75 means “peer only with devices that have RSSI greater than -75”.

To adjust the mesh\_max\_peer\_links setting:

* Log into the device via ssh (e.g. ssh root\@192.168.12.1)
* Use an editor to update the file /etc/config/mesh11sd.
* Update the mesh\_max\_peer\_links to the value you desire.
* Save the file and restart the wireless (e.g. wifi down && wifi up)

This setting  will limit the number of peer links a node establishes. For example, set this to 2 for a number of devices and they will form a chain.

***

## 5 Frequently Asked Questions (FAQ)

Why does this application note use 2.4GHz for the uplink to the internet?\
Multiple methods exist to configure the network topology under examination. This application note utilizes a smartphone-provided hotspot as it is universally accessible and simplifies network testing. We believe this choice is the simplest for any user to test - even in an office environment - as it does not require plugging Ethernet cables into existing infrastructure.

Can I use the WAN or LAN Ethernet for uplink to the internet?\
Yes you can.

* To use the WAN port - you would connect the WAN port to your uplink gateway (on its ‘lan’ side). You should also ensure the uplink 2.4 GHz client is not connected.
* To use the LAN port - this is more complex, as the ‘lan’ side of your uplink gateway is probably running a DHCP server already (to hand out DHCP leases in your network). You should:
* Change Device 1’s lan interface to be a DHCP client.
* Plug the LAN port into the lan side of your uplink gateway.
* Use the DHCP lease table from your uplink gateway to determine the IP addresses given to Device 1 and Device 2.

Can I connect to the mesh via the LAN port on the HaLowLink (Device 2 / Device 3) instead of via the 2.4 GHz Wi-Fi network?\
Yes, if your device has an available Ethernet port this is possible. For example EKH01 platforms do not have an additional 2.4 GHz radio, so using the Ethernet port is required. When you connect via a LAN port on Device 2 or 3 your laptop will receive an IP address from the DHCP server on the network (i.e. likely from Device 1).

What will the throughput and latency be like?\
As with all wireless links, the throughput and latency will depend on the quality of the radio link (i.e. noise, distance etc). For 802.11s mesh links another factor is the number of hops needed to route frames. For the 802.11ah throughput performance, please refer to the expected data rate \[[link](https://www.google.com/url?q=https://en.wikipedia.org/wiki/IEEE_802.11ah%23Data_rates\&sa=D\&source=editors\&ust=1783414770606733\&usg=AOvVaw2phTezi-Hs85w6PJHilyP9)] and your device capability.

***

## 6 Revision History

| Release Number | Release Date | Release Notes   |
| -------------- | ------------ | --------------- |
| 1.0            | 2025-04-02   | Initial release |