how to PC (AP, 802.11gbn) <-> mesh root (STA, 802.111bgn), mesh root (AP, 802.11lr) <-> many mesh nodes (STA, 802.11lr)

[beta-tester]

hi, i am new to this forum...

i am wondering, if i can use an ESP32 wifi mesh with long range capability, where one ESP32 acts as the "gateway" between normal WiFi access point to my internal network, where my PC is and the ESP32-mesh-nodes, where each ESP-mesh node can communicate to my PC via TCP or UDP.

something like:

Code: Select all

PC
<->
WiFi router, 802.11bgn, AP (my normal local network router)
<->
{
    ESP-mesh as root node (802.11bgn, STA-mode)
    <->
    bridge/NAT/repeater
    <->
    ESP-mesh as root node (802.11 LR, AP-mode)
}
<->
ESP-mesh nodes (802.11 LR, STA-mode)

i think this ESP32 root node must have a bridge, NAT or repeater capability between,
must use 802.11bgn Wifi in STA-mode to interconnect with my normal local network router and
must use 802.11 LR WiFi in AP-mode to interconnect to the ESP-mesh, because i want to use the ESP32 long range capability in the mesh itself.

would this be possible to build with the esp-idf / esp-mdf?
is there already something like this as an example?

[rrelande]

This question is quite legitimate as it would help a lot.
in the ESP MESH OVERVIEW, https://www.espressif.com/en/products/s ... h/overview
there is actually an icon claiming that

ALL NODES GET IP CONNECTIVITY

but as we go through in more details,
devices need to communicate using ESP-MESH datagrams. then only the root node will create the IP packet.

which means that nodes DO NOT HAVE NATIVE IP CONNECTIVITY

It could make sense to this clarification. MDF is a great way to route data but it DOES NOT provide IP connectivity to all nodes as of now.

[willemmerson]

Have you seen this? I've never tried it but from the log it seems like each node does have ip connectivity:
https://github.com/espressif/esp-idf/tr ... al_network

[rrelande]

seems promising feature and in theory it should work.

not all but many protocol are able to traverse NAT or even multiple NAT correctly without a need for application on the gateway side. This includes MQTT.

however any change in mesh structure also implies a change in the related IP network. Each client will get a new IP address in another NAT when any parent upstream changes.

in case the endpoint is connected, it would also mean it needs to reconnect to related cloud service to ensure receiving subsequent messages from the cloud.

any experience of trying this in practice would make it easier to start using it.