Mesh networking is now basically fixed, but keeping this open for a few enancements should do:

When doing mesh flooding we should include a random delay before each rebroadcast.

Implement DSR for unicast messages (currently we are just flooding broadcasts)

See remaining work items listed in comment at top of Router.cpp

I did read the files. Nice job @geeksville!

Unfortunately, I did not find information (most likely just didn't understand..) of what components the packet header is built of? Are the components, in the headers, kept same in every packet/message type?

The mesh is intended to work, correct me if I'm wrong, by these steps:

set channel settings from the app
send user information to the mesh by flooding
receive answers from the mesh of other nodes (change our node ID if necessary)
update our node database of other nodes (of all messages "heard")
send location update to the mesh (periodically or by request)
flood all messages to the mesh (in future, flood only messages with not only one recipient?)
switch to DSR to unicast messages (not yet in use), using the node database information
if a node is not in our node database, send a DSR route request (not yet in use)
update our node database per answers (not yet in use)
continue unicast messages per DSR and our node databases (not yet in use)

Uh oh!

Uh oh!

Make mesh networking work nicely for unicast messages #3

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions