User Tools

Site Tools

radio:mesh

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
radio:mesh [2025/11/17 09:54] – cocoradio:mesh [2026/03/31 12:54] (current) – [OLSR] Humphrey Boa-Gart
Line 48: Line 48:
 === MeshCore === === MeshCore ===
  
-[[github>meshcore-dev/MeshCore|MeshCore]] is another LoRa-based mesh, similar to Meshtastic and even runs on the same devices. Unlike Meshtastic's "flooding" approach //(where all messages are rebroadcast by any node until they reach their destination or hop limit)// Meshcore takes a "flood-then-direct" approach //(it floods initially to discover paths & efficient routes, falling back to flood only when necessary)//. This and several other features makes MeshCore useful for planned urban networks where Meshtastic would be overloaded by congestion. +[[github>meshcore-dev/MeshCore|MeshCore]] is another LoRa-based mesh, similar to Meshtastic and even runs on the same devices. Unlike Meshtastic's "flooding" approach //(where all messages are rebroadcast by any node until they reach their destination or hop limit)// Meshcore takes a "flood-then-direct" approach //(it floods initially to discover paths & efficient routes, falling back to flood only when necessary)//. 
 + 
 +This and several other features makes MeshCore useful for large planned mesh networks. Since Meshtastic is primarily designed for quick-deployment by hobbyists, hikers & emergency response, it is easily overwhelmed in congested urban & corporate environments.
  
  
Line 81: Line 83:
  
 [[https://syncthing.net|Syncthing]] is an open-source, peer-to-peer file synchronization tool that continuously keeps folders identical across multiple devices //(phones, laptops, servers)// without relying on any central cloud server. It normally uses the internet for discovery and relaying, but when devices are on the same local network //(ie: Wi-Fi or Bluetooth)// or when internet is unavailable, it can automatically fall back to direct local connections and even route traffic through other nearby Syncthing nodes, effectively creating an ad-hoc mesh for file transfers. [[https://syncthing.net|Syncthing]] is an open-source, peer-to-peer file synchronization tool that continuously keeps folders identical across multiple devices //(phones, laptops, servers)// without relying on any central cloud server. It normally uses the internet for discovery and relaying, but when devices are on the same local network //(ie: Wi-Fi or Bluetooth)// or when internet is unavailable, it can automatically fall back to direct local connections and even route traffic through other nearby Syncthing nodes, effectively creating an ad-hoc mesh for file transfers.
 +
 +
 +
 +==== Open Routing Protocols =====
 +
 +There are several //"open source"// mesh routing protocols out there too. Since they exist as a set of rigidly defined standards, anyone can build a network around them. Since these standards have been field-tested across the world, they are a safe architectural bet if you are building a serious custom network. Some options include:
 +
 +
 +=== Babel ===
 +
 +[[https://docs.arednmesh.org/en/latest/arednHow-toGuides/babel.html|Babel]] is a modern open routing protocol built for networks that are messy in the real world: mixed wired and wireless links, changing topology, and nodes that may come and go without much warning. In standards terms it is a loop-avoiding distance-vector protocol, but the practical takeaway is simpler: Babel is designed to be lightweight, fast to adapt, and unusually good at coping with unreliable links, which is why it has become one of the better-known open protocols for wireless mesh networking. Read [[rfc>8966|RFC 8966]] for more information.
 +
 +
 +
 +=== OLSR ===
 +
 +OLSR, or Optimized Link State Routing, is an older open routing protocol for wireless mesh networks. It came out of the mobile ad hoc network (MANET) world, where devices form a network on the fly by connecting directly and relaying traffic for one another without fixed infrastructure. OLSR’s key idea was reducing routing chatter by designating certain nodes as relays, so not every device had to repeat every update.
 +
 +That made OLSR one of the defining early open protocols in the history of mesh networking. It is less modern and efficient than newer options like Babel, but it remains an important example of how decentralized networks learned to keep themselves stitched together. Read [[rfc>3626|RFC 3626]] for more information.
  
  
Line 86: Line 107:
 ==== Local Area Mesh ==== ==== Local Area Mesh ====
  
-While the above applications & protocols make some types of mesh networking easier, you do not need any of them. Any **LAN** or **local area network** can be set up as a type of mesh network. Pretty much every major operating system has LAN support, meaning all you have to do is plug your computer into the LAN and it will usually autodetect. There is nothing stopping you from running miles of LAN cables and wifi repeaters with your friends to create a city-wide LAN. In fact, residents of cities like Havana, New York, Barcelona, Berlin, Rome, Toronto and more, have done exactly that to varying degrees of success.+While the above applications & protocols make some types of mesh networking easier, you do not need any of them. Any **LAN** or **local area network** can be set up as a type of mesh network. Pretty much every major operating system has LAN support, meaning all you have to do is plug your computer into the LAN and it will usually autodetect. There is nothing stopping you from running miles of LAN cables and wifi repeaters with your friends to create a city-wide LAN. In fact, residents of cities like Havana, New York, Barcelona, Berlin, Rome, Toronto and more, have done exactly that to varying degrees of success. Toronto's local mesh for example uses Babel as we just described above.
  
 If your mesh requires persistent connections, fast speeds and the ability to transfer large files, this is the type of mesh you will want to build. If your mesh requires persistent connections, fast speeds and the ability to transfer large files, this is the type of mesh you will want to build.
 +
  
  
Line 110: Line 132:
  
  
-{{tag>Communications}}+{{tag>Communications Networking}}
radio/mesh.1763373258.txt.gz · Last modified: by coco

Find this page online at: https://bestpoint.institute/radio/mesh