Friendly Name Mesh Nodes

Installing and Using OpenWrt
21

Unfortunately no.
This topic/thread is not the place to go into this, but I will "briefly" answer.

If using mesh11sd:

  1. The 802.11s mesh is dynamically configured by the mesh11sd service daemon.
  2. A layer 2 HWMP mac-routing backhaul is created.
  3. A hashed mesh id and mesh key is generated from a text strings in the mesh11sd config. All nodes wanting to join the backhaul must use the same text strings. The hashed values are used to authenticate to the backhaul and to encrypt traffic on the backhaul.
  4. A mesh backhaul does not have an SSID. Normal user devices cannot connect directly to the backhaul. They do so indirectly using a Mesh Gate, aka an Access Point, usually built into the meshnode.
  5. Every mesh node, by default will have two mesh gates, aka user wireless network access points, a standard and a guest.
  6. All SSIDs are different by default and incorporate a suffix indicating the wireless band and the last 4 digits of the mac address of the meshnode. Anyone knowing the wifi password can use any of the SSIDs. All of this is configurable with many options in the mesh11sd config file.

Your laptop would use the standard wireless network.
Your IoT device would use the IoT network (by default called Guest-xx-yyyy, but can be anything you like)

Finally, you can get an Access Point statistics report, for all mesh gates (APs), in json format, centrally on the mesh portal.

But please, start a new topic if you want to continue to discuss this.

22

Thanks but are there any advantages to Mesh11SD over Batman Adv? It seems to me the most major one is supposedly ease of use but I’ve read the instructions three times and still don’t see how to add an extra guest network, so it isn’t that easy anyway.