# MM8108-EKH19 in 802.11s

**URL:** https://community.morsemicro.com/t/mm8108-ekh19-in-802-11s/1158
**Category:** General
**Created:** [December 17, 2025, 1:07am UTC](https://community.morsemicro.com/t/mm8108-ekh19-in-802-11s/1158 "2025-12-17T01:07:29Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![PNW](https://avatars.discourse-cdn.com/v4/letter/p/71c47a/32.png) [@PNW](https://community.morsemicro.com/u/PNW)
#### Post date: [December 17, 2025, 1:07am UTC](https://community.morsemicro.com/t/mm8108-ekh19-in-802-11s/1158/1 "2025-12-17T01:07:29Z")

</div>

I have configured 3 units in 802.11s as described in the User Manual. I have an ethernet IP camera connected to a far mesh point. The mesh gate is connected to my PCs network (via the included MM router). The problem I am having is that I am not seeing the halow mesh route through any hops. It only takes a direct route between camera mesh point and PC mesh gate. My camera is configured for TCP and have it set at a low resolution and data rate (about 3Mbps). I have used attenuators to weaken the direct signal between the PC mesh gate and the camera mesh point so the signal between them is below the RSSI threshold. The system never uses the intermediate mesh point that is at a much higher signal level to both the camera mesh point and the mesh gate.

I have tried using traceroute which shows no hops. The realtime graph for wlan0 does not show any appreciable data flow (in or out) on the intermedia mesh point. Wireshark only shows the packet source and destination and nothing in between.

Thank you

---

<div class="post-metadata">

### Author: ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)
#### Post date: [December 24, 2025, 3:51am UTC](https://community.morsemicro.com/t/mm8108-ekh19-in-802-11s/1158/2 "2025-12-24T03:51:05Z")

</div>

Hi @PNW

> [@PNW](#):
>
> I have tried using traceroute which shows no hops.

The mesh will be layer 2, so you won’t see the hops with traceroute. You might want to check mesh paths with `iw dev wlan0 mpath dump`.

> [@PNW](#):
>
> The system never uses the intermediate mesh point that is at a much higher signal level to both the camera mesh point and the mesh gate.

This might be the network settling into a state it deems is most suitable. What is the metric reported by mpath dump on the mesh gate?

For testing purposes, you can force the mesh gate to limit it’s peers to 1 with `uci set mesh11sd.mesh_params.mesh_max_peer_links=1` and then `reload_config` from the terminal on the mesh gate. Of course, this won’t be helpful for a real deployment.
