easymesh in ekh03

General
1

hello

I have used mm6108-ekh03 in a Star topology (AP, STA). And I have noticed that in the configuration of this kit, there is an option for activating the easy mesh method and in the datasheet, I have realised that it was stated that this method is only for ekh01. I wonder, can we use EasyMesh directly in ekh01?

2

Hi @m.aminezzatimofarah

I wonder, can we use EasyMesh directly in ekh01?

You mean EKH03?

An EKH03 should function as an EasyMesh agent, but it is a resource constrained device, so we wouldn’t advise using it as an EasyMesh controller.

3

Oh, sorry about that. Yes, I meant EKH03

You mean it is impossible to use as an EasyMesh controller or not recommended, because I have successfully configured it as an EasyMesh controller, and now I have a big problem:

We have a network setup consisting of two EKH03 kits. One is configured as an EasyMesh Controller and the other as an EasyMesh Agent. Each kit is connected to a separate Windows PC via its Ethernet port.

The HaLow mesh network operates on the 192.168.1.0/24 subnet, and the Ethernet LAN interfaces are configured on the 10.42.0.0/24 subnet.

But besides accessing the administration panel of each kit, these two kits (I mean the PC connected to the kit) have no available connection with each other on the network. I can’t share any data in the network, and I even can’t use the ping command in CMD to ping other PC’ IP addresses.

I have done these steps to solve this problem, but I failed :

  1. Enabled “Traffic Forwarding”
  2. Disabled Client Isolation
  3. Checked Firewall Rules
  4. Corrected DHCP Configuration
  5. Verified PC Network Profiles
  6. Swapped Kit Roles

Is there any specific operation that I have’nt done to do this action correctly or there is another problem?

4

The main issue here is that you have two separate subnets. If you want connectivity between all ethernet and HaLow devices, you should only have one subnet.

This is likely a result of selecting the Upstream ‘none’ mode, where it creates isolated subnets. This mode is not intended for deployments but for testing the HaLow links easily from the devices.

To fix this, the easiest thing to do is to select an Upstream network in the wizard. However, since the EKH03 has only one port, this will mean that you should plug it into your local router.

Alternatively, after configuring it as ‘None’, go to the Quick Config page, remove your ethernet port from the lan network, and add it into the ‘ahwlan’ network.

5

Thanks for your help. I tried the second method and it solved my issue. One interesting point was that I didn’t need to remove my Ethernet port from the LAN network — just adding it to the ahwlan network was enough. Thanks again for your guidance.

6

Great! It’s a little strange it didn’t force you to remove the port from the lan network - it should fail to save with an error in this case, as having the port in two separate networks doesn’t make sense for OpenWrt - but I guess if it’s working we’re all good here.

Just watch out for having overlapping distinct subnets (i.e. don’t run a 10.42.0.1 + DHCP Server on your Agent/STA if you’re connecting to an AP/Controller that also has a 10.42.0.1 address).

1 Like