I will also echo the following statement made in THIS thread:
Wi-Fi EasyMesh - Site Feedback and Other Questions - OpenWrt Forum
"@Pablomagno, if you would care to share some code or point to your repository"
I decided to use some Google-fu to investigate this more and what I found was:
No explanation if this is just an overview of EasyMesh with the trademarked name EasyMesh (that the Wi-Fi Alliance owns BTW) removed or not. However, of interest on this page:
"prplOS (formerly prplWRT)"
From what I can suss out from all of this prplMesh essentially manipulates WDS to create a "sort of mesh" I guess.
But, the many locations in the github tremendously complicate understanding of it, and there seems to be no code at all up on that github tree that can be added into a typical OpenWRT build for an access point other than addin for lede which seems to be used for configuring it - but WHAT it's configuring is unknown.
In other words - the entire thrust of this effort seems incredibly similar to EVERYTHING I have read so far about EasyMesh - it's merely an attempt to get wifi radio chipset vendors to fork over money for some kind of mesh implementation. Code that can build on a real life wifi router does not seem to be supplied as there's no reference implementation of either system anywhere I can find, APIs don't seem to be supplied.
For ANYTHING like PrplMesh or EasyMesh or whatever other proprietary trademarked "mesh" implementation to get traction in the industry you MUST have a binary or firmware that can be downloaded, flashed to a half dozen access points, and deployed in a test environment.
It is easy to do this with IEEE802.11s The current version of OpenWRT comes with it included in the default load off the OpenWRT website. Anyone can take a bunch of APs from random thrift stores for very little money, flash them to OpenWRT, configure a 802.11s mesh, and distribute them through a building then run some radio tests with common phones, laptops, and other wifi clients, and see what happens. I'm sure that this is probably an assigned project in many college courses on wifi/network engineering.
But nothing like that is possible with EasyMesh unless you fork over many hundreds of dollars per AP and use the vendor's proprietary firmware. And the same is true with PrplMesh or any other kind of proprietary mesh solution - many of which these days are subscription based (like Cisco Meraki's) - so not only do you get the thousand dollar or so capital cost of acquiring the APs - you are now stuck forking over hundreds of dollars a month to keep it all running.
Pablomagno, when you started this prplmesh project 7 years ago what did you use for testing your initial project? OpenWRT, a free Open Source project. What are you using now? Ubuntu 18, Docker, and so on = all free OSS products. WORKING products that anyone can download and boot. You knew then the POWER of free, unencumbered, non-vendor-proprietary solutions. So why in heaven's name do you think that EasyMesh is going to win long term? It's proprietary. Even your own prplmesh has this to say:
" it is scoped as a reference implementation and will leave ample room for differentiation, for example for proprietary IP algorithms making intelligent decisions for the whole Multi-AP network."
Last I checked, "proprietary" is the OPPOSITE of Linux, of OpenWRT, of Ubuntu, of Docker - all things your "reference implementation" utterly depends on.
Do you NOT see how futile all this is?
Produce an OpenWRT community build of prplMesh, for a commonly available AP and post it on your multitude of github repositories and as icing on the cake, make a video or at least post some screenshots - proving how superior all this stuff is to IEEE802.11s