Question from Nikita about mesh

[ESP_Alen]

This one - Which protocol is using on MAC layer to control access to media?
Also have such question - u have marked all connections red and said its TCP. Does this TCP connections are sets on demand or they are establish for all the time?

1. Ieee802.11 with CSMA/CA
2. All the tcp connections are persist connect.

[ESP_Alen]

Please paste error log of server here.

[CipiCips]

Dear Alen,


1. You've told us that packet from server is distributed all over mesh to every node in that mesh. For example if we have 20 nodes and they are listed like 1, 2, 3, 4, 5, ect. is it possible to send data to specific node not all ?


Regards

Ivan

[ESP_Alen]

Dear Alen,


1. You've told us that packet from server is distributed all over mesh to every node in that mesh. For example if we have 20 nodes and they are listed like 1, 2, 3, 4, 5, ect. is it possible to send data to specific node not all ?


Regards

Ivan

Yes, you just build packet using destination node's MAC as destination address, the packet will be forwarded to the node.

[Nikita Belyaev]

Please paste error log of server here.

Hi Alen!
I'll post my logs a bit later.

Now i have really important question - why have you chose MAC adr. as main adr for routing?
Why we cant use IP? You sad befor, that IP adr is now unique, but its not so!!
Its so unussual to make routing by using MAC adr. on layer above TCP.

One more question - how does routing table looks like (structure).

Thanks

[ESP_Alen]

Please paste error log of server here.

Hi Alen!
I'll post my logs a bit later.

Now i have really important question - why have you chose MAC adr. as main adr for routing?
Why we cant use IP? You sad befor, that IP adr is now unique, but its not so!!
Its so unussual to make routing by using MAC adr. on layer above TCP.

One more question - how does routing table looks like (structure).

Thanks

1. Because IP address is not unique, there are multiple devices with the same IP address.
MAC address is unique. So we use MAC address.

2. child-1 ----------mac list table(mac address list)
child-2-----------mac list table(mac address list)
child-3-----------mac list table(mac address list)
child-4-----------mac list table(mac address list)

[Nikita Belyaev]

Please paste error log of server here.

Hi Alen!
I'll post my logs a bit later.

Now i have really important question - why have you chose MAC adr. as main adr for routing?
Why we cant use IP? You sad befor, that IP adr is now unique, but its not so!!
Its so unussual to make routing by using MAC adr. on layer above TCP.

One more question - how does routing table looks like (structure).

Thanks

1. Because IP address is not unique, there are multiple devices with the same IP address.
MAC address is unique. So we use MAC address.

2. child-1 ----------mac list table(mac address list)
child-2-----------mac list table(mac address list)
child-3-----------mac list table(mac address list)
child-4-----------mac list table(mac address list)

Hi! Thanks for answers!

Can you explain why its so - there are multiple devices with the same IP address.
I have started my small network of 3 esp and there are 3 different IP - 2.255.255.1, 2.255.255.2 and 2.255.255.3

Am I right if say that when leaf node want to send data, he create p2p packet and send it to his non-leaf (parent) node. If this node have information about desired destination he create p2p packet to this destination? But if he don't have desired mac he send packet to upper parent and so on till any node with destination MAC in routing table.
So, does the node create each time p2p packets while transmitting data?

Is this a table on root node?

[/list]

2. child-1 ----------mac list table(mac address list)
child-2-----------mac list table(mac address list)
child-3-----------mac list table(mac address list)
child-4-----------mac list table(mac address list)

P.S. Is it possible to measure sped of connection between nodes?

[ESP_Alen]

Hi! Thanks for answers!

Can you explain why its so - there are multiple devices with the same IP address.
I have started my small network of 3 esp and there are 3 different IP - 2.255.255.1, 2.255.255.2 and 2.255.255.3

Am I right if say that when leaf node want to send data, he create p2p packet and send it to his non-leaf (parent) node. If this node have information about desired destination he create p2p packet to this destination? But if he don't have desired mac he send packet to upper parent and so on till any node with destination MAC in routing table.
So, does the node create each time p2p packets while transmitting data?

Is this a table on root node?

[/list]

2. child-1 ----------mac list table(mac address list)
child-2-----------mac list table(mac address list)
child-3-----------mac list table(mac address list)
child-4-----------mac list table(mac address list)

P.S. Is it possible to measure sped of connection between nodes?

1. The SoftAP's IP of all nodes with IP address of 2.255.255.* is 3.255.255.1, so their sub-nodes are possible to have the same IP address.

2. You don't need to care the forwarding path, you just build packet with destination mac, then use espconn_mesh_sent to send packet.
the routing is composed of upwards routing and downwards routing.
If current node successes to find destination mac address in route table, it uses downwards routing, otherwise, it uses upwards routing.
In another word, the mesh will forward packet according to route table, if the current node fails to find destination device in route table, it forwards the packet to its parent. the parent is default routing path.

3. you can build multiple packet and send the packet one by one.

4. You can use ucast or p2p packet to communicate between tow nodes.

5. We have measured the speed of connection, every node send packet to its parent, and parent echo the packet back to node.
and mean performance about round robin is 10pps with maximum length packet(1300).

[Nikita Belyaev]

1. The SoftAP's IP of all nodes with IP address of 2.255.255.* is 3.255.255.1, so their sub-nodes are possible to have the same IP address.

2. You don't need to care the forwarding path, you just build packet with destination mac, then use espconn_mesh_sent to send packet.
the routing is composed of upwards routing and downwards routing.
If current node successes to find destination mac address in route table, it uses downwards routing, otherwise, it uses upwards routing.
In another word, the mesh will forward packet according to route table, if the current node fails to find destination device in route table, it forwards the packet to its parent. the parent is default routing path.

3. you can build multiple packet and send the packet one by one.

4. You can use ucast or p2p packet to communicate between tow nodes.

5. We have measured the speed of connection, every node send packet to its parent, and parent echo the packet back to node.
and mean performance about round robin is 10pps with maximum length packet(1300).

What does it mean SoftAP of 2.255.255.*? I don't have such 3.255.255.1.
Things you are talking about are the same with picture from 2-nd page https://github.com/espressif/ESP8266_MESH_DEMO/blob/master/document/Mesh%20protocol%20architecture.pdf. But I cant understand( Would u pleas explain?

Routing is exactly what is interesting for me.

[ESP_Alen]

SoftAP of all the nodes with two hops away from router has the same IP address, it's 2.255.255.1.

I think you don't need to care about the mesh, please focus on the Application packet based on mesh;