espressif / esp-mesh-lite

A lite version Wi-Fi Mesh, each node can access the network over the IP layer.
126 stars 18 forks source link

mseh dhcps ip assignment problem (AEGHB-709) #104

Open yel-best opened 3 months ago

yel-best commented 3 months ago

Hi ,

Because my device is running in a group, and the group's router uses 192.168.xx.xx DHCP, and has some restrictions on this IP segment. When we use mesh, the mesh dhcp IPs obtained by the nodes that make up the network seem to start from 192.168.1.1, and different levels will have different, gradually, for example: 192.168.1.1, 192.168.1.2. Can I define this network segment? For example, if I use 10.22.xx.xx, I don't know if some of the slow intranet access problems I encounter are related to the DHCP allocation restrictions? Or is the internal network of the mesh actually one IP for the route, and this IP is allocated by the router?

I have read some instructions and tried to check the router management interface. In fact, only the mesh root node will be displayed in the list of connected terminals on the router.

tswen commented 3 months ago

For Mesh-Lite devices, the IP of each child node device is assigned by its parent node. For a Mesh-Lite network, only the root node is visible to the router.

You can set a specific network segment for softap through esp_bridge_netif_set_ip_info API.

yel-best commented 3 months ago

For Mesh-Lite devices, the IP of each child node device is assigned by its parent node. For a Mesh-Lite network, only the root node is visible to the router.

You can set a specific network segment for softap through esp_bridge_netif_set_ip_info API.

esp_bridge_netif_set_ip_info This seems to be a static IP?

So the sub-node network segment cannot be modified?

tswen commented 3 months ago

For station netif, it is to set the static IP, but for softap netif, it is to set the softap network segment.