a05fdd9c10
1. detect and fix root conflicts when router BSSID is not set. 2. when root can not connect to the router due to NO_MORE_STAS(reason code:5), root will stop re-connection and perform MESH_NWK_LOOK_FOR_NETWORK. 3. wifi: fix the disconnection caused by receiving a deauth frame from non-parent node during scanning. 4. fix routing table redundant issue. 5. modify the max routes limitation from 300 to 1000. 6. wifi: fix ap does not deauth sta which has not completed the 4-way handshake. |
||
|---|---|---|
| .. | ||
| main | ||
| CMakeLists.txt | ||
| Makefile | ||
| README.md | ||
Mesh Internal Communication Example
This example demonstrates how to use the mesh APIs to set up a mesh network, send and receive messages over the mesh network and etc.
Features Demonstrated
-
mesh initialization
-
mesh configuration
-
mesh start
-
mesh event handler
-
root send and receive
-
other nodes receive
Run make menuconfig to configure the mesh network channel, router SSID, router password and mesh softAP settings.
When the mesh network is established and if you happen to run this example on ESP-WROVER-KIT boards, the RGB light indicator will show you on which layer devices are. The pink reprents root; the yellow reprents layer 2; the red reprents layer 3; the blue reprents layer 4; the green reprents layer 5; the white reprents layer greater than 5. Root continuously sends an On / Off control message to all devices in its routing table. Devices including root itself receive this message and do the On / Off.