Not amateur radio
Mobile ad hoc networks (MANETs)
Networks with no fixed infrastructure, where every node may relay for the others.
Not amateur radio
Networks with no fixed infrastructure, where every node may relay for the others.
A mobile ad hoc network (MANET) is a network with no fixed infrastructure in charge. RFC 2501 describes it as a set of nodes, which may combine the roles of router and host, that "themselves form the network routing infrastructure in an ad hoc fashion." Nodes are free to move, so the pattern of who can hear whom changes. The RFC also lists "mobile mesh networking" and "mobile, multihop, wireless networking" as names for the same idea.
In plain words: there is no tower or central router. Each radio can also relay for its neighbors, so a message can reach someone who is out of direct range by hopping through other nodes.
RFC 2501 lists the traits that make these networks awkward to design:
Sharing one radio channel adds its own problems. The Meshtastic documentation describes two of them: nodes listen before transmitting and wait a random time if the channel is busy, and every packet carries an ID so that a node can drop a copy it has already handled. A hop limit stops a packet from circulating forever.
Flooding. Every node that hears a message rebroadcasts it, up to a hop limit. Nobody needs to know the layout of the network, so it keeps working as nodes move. The cost is airtime, since many nodes repeat the same message. Meshtastic uses a refined version that lets nodes hold back, covered in Managed flooding.
Learned routes. The network works out a path first, then sends later messages along it so that only nodes on the path repeat them. That saves airtime, but a path can break when a node leaves. The MeshCore FAQ describes sending the first message by flood, learning the path from the reply, and falling back to flooding when a stored path fails; see Path routing.