mirror of
https://github.com/markqvist/Reticulum.git
synced 2024-12-23 04:10:18 +00:00
477 lines
23 KiB
HTML
477 lines
23 KiB
HTML
<!doctype html>
|
||
<html class="no-js" lang="en">
|
||
<head><meta charset="utf-8"/>
|
||
<meta name="viewport" content="width=device-width,initial-scale=1"/>
|
||
<meta name="color-scheme" content="light dark"><meta name="generator" content="Docutils 0.19: https://docutils.sourceforge.io/" />
|
||
<link rel="index" title="Index" href="genindex.html" /><link rel="search" title="Search" href="search.html" /><link rel="next" title="Code Examples" href="examples.html" /><link rel="prev" title="Configuring Interfaces" href="interfaces.html" />
|
||
|
||
<meta name="generator" content="sphinx-7.1.2, furo 2022.09.29.dev1"/>
|
||
<title>Building Networks - Reticulum Network Stack 0.7.3 beta documentation</title>
|
||
<link rel="stylesheet" type="text/css" href="_static/pygments.css?v=a746c00c" />
|
||
<link rel="stylesheet" type="text/css" href="_static/styles/furo.css?digest=189ec851f9bb375a2509b67be1f64f0cf212b702" />
|
||
<link rel="stylesheet" type="text/css" href="_static/copybutton.css?v=76b2166b" />
|
||
<link rel="stylesheet" type="text/css" href="_static/styles/furo-extensions.css?digest=30d1aed668e5c3a91c3e3bf6a60b675221979f0e" />
|
||
<link rel="stylesheet" type="text/css" href="_static/custom.css?v=bb3cebc5" />
|
||
|
||
|
||
|
||
|
||
<style>
|
||
body {
|
||
--color-code-background: #f8f8f8;
|
||
--color-code-foreground: black;
|
||
|
||
}
|
||
@media not print {
|
||
body[data-theme="dark"] {
|
||
--color-code-background: #202020;
|
||
--color-code-foreground: #d0d0d0;
|
||
--color-background-primary: #202b38;
|
||
--color-background-secondary: #161f27;
|
||
--color-foreground-primary: #dbdbdb;
|
||
--color-foreground-secondary: #a9b1ba;
|
||
--color-brand-primary: #41adff;
|
||
--color-background-hover: #161f27;
|
||
--color-api-name: #ffbe85;
|
||
--color-api-pre-name: #efae75;
|
||
|
||
}
|
||
@media (prefers-color-scheme: dark) {
|
||
body:not([data-theme="light"]) {
|
||
--color-code-background: #202020;
|
||
--color-code-foreground: #d0d0d0;
|
||
--color-background-primary: #202b38;
|
||
--color-background-secondary: #161f27;
|
||
--color-foreground-primary: #dbdbdb;
|
||
--color-foreground-secondary: #a9b1ba;
|
||
--color-brand-primary: #41adff;
|
||
--color-background-hover: #161f27;
|
||
--color-api-name: #ffbe85;
|
||
--color-api-pre-name: #efae75;
|
||
|
||
}
|
||
}
|
||
}
|
||
</style></head>
|
||
<body>
|
||
|
||
<script>
|
||
document.body.dataset.theme = localStorage.getItem("theme") || "auto";
|
||
</script>
|
||
|
||
|
||
<svg xmlns="http://www.w3.org/2000/svg" style="display: none;">
|
||
<symbol id="svg-toc" viewBox="0 0 24 24">
|
||
<title>Contents</title>
|
||
<svg stroke="currentColor" fill="currentColor" stroke-width="0" viewBox="0 0 1024 1024">
|
||
<path d="M408 442h480c4.4 0 8-3.6 8-8v-56c0-4.4-3.6-8-8-8H408c-4.4 0-8 3.6-8 8v56c0 4.4 3.6 8 8 8zm-8 204c0 4.4 3.6 8 8 8h480c4.4 0 8-3.6 8-8v-56c0-4.4-3.6-8-8-8H408c-4.4 0-8 3.6-8 8v56zm504-486H120c-4.4 0-8 3.6-8 8v56c0 4.4 3.6 8 8 8h784c4.4 0 8-3.6 8-8v-56c0-4.4-3.6-8-8-8zm0 632H120c-4.4 0-8 3.6-8 8v56c0 4.4 3.6 8 8 8h784c4.4 0 8-3.6 8-8v-56c0-4.4-3.6-8-8-8zM115.4 518.9L271.7 642c5.8 4.6 14.4.5 14.4-6.9V388.9c0-7.4-8.5-11.5-14.4-6.9L115.4 505.1a8.74 8.74 0 0 0 0 13.8z"/>
|
||
</svg>
|
||
</symbol>
|
||
<symbol id="svg-menu" viewBox="0 0 24 24">
|
||
<title>Menu</title>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor"
|
||
stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather-menu">
|
||
<line x1="3" y1="12" x2="21" y2="12"></line>
|
||
<line x1="3" y1="6" x2="21" y2="6"></line>
|
||
<line x1="3" y1="18" x2="21" y2="18"></line>
|
||
</svg>
|
||
</symbol>
|
||
<symbol id="svg-arrow-right" viewBox="0 0 24 24">
|
||
<title>Expand</title>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor"
|
||
stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="feather-chevron-right">
|
||
<polyline points="9 18 15 12 9 6"></polyline>
|
||
</svg>
|
||
</symbol>
|
||
<symbol id="svg-sun" viewBox="0 0 24 24">
|
||
<title>Light mode</title>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor"
|
||
stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" class="feather-sun">
|
||
<circle cx="12" cy="12" r="5"></circle>
|
||
<line x1="12" y1="1" x2="12" y2="3"></line>
|
||
<line x1="12" y1="21" x2="12" y2="23"></line>
|
||
<line x1="4.22" y1="4.22" x2="5.64" y2="5.64"></line>
|
||
<line x1="18.36" y1="18.36" x2="19.78" y2="19.78"></line>
|
||
<line x1="1" y1="12" x2="3" y2="12"></line>
|
||
<line x1="21" y1="12" x2="23" y2="12"></line>
|
||
<line x1="4.22" y1="19.78" x2="5.64" y2="18.36"></line>
|
||
<line x1="18.36" y1="5.64" x2="19.78" y2="4.22"></line>
|
||
</svg>
|
||
</symbol>
|
||
<symbol id="svg-moon" viewBox="0 0 24 24">
|
||
<title>Dark mode</title>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor"
|
||
stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" class="icon-tabler-moon">
|
||
<path stroke="none" d="M0 0h24v24H0z" fill="none" />
|
||
<path d="M12 3c.132 0 .263 0 .393 0a7.5 7.5 0 0 0 7.92 12.446a9 9 0 1 1 -8.313 -12.454z" />
|
||
</svg>
|
||
</symbol>
|
||
<symbol id="svg-sun-half" viewBox="0 0 24 24">
|
||
<title>Auto light/dark mode</title>
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor"
|
||
stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" class="icon-tabler-shadow">
|
||
<path stroke="none" d="M0 0h24v24H0z" fill="none"/>
|
||
<circle cx="12" cy="12" r="9" />
|
||
<path d="M13 12h5" />
|
||
<path d="M13 15h4" />
|
||
<path d="M13 18h1" />
|
||
<path d="M13 9h4" />
|
||
<path d="M13 6h1" />
|
||
</svg>
|
||
</symbol>
|
||
</svg>
|
||
|
||
<input type="checkbox" class="sidebar-toggle" name="__navigation" id="__navigation">
|
||
<input type="checkbox" class="sidebar-toggle" name="__toc" id="__toc">
|
||
<label class="overlay sidebar-overlay" for="__navigation">
|
||
<div class="visually-hidden">Hide navigation sidebar</div>
|
||
</label>
|
||
<label class="overlay toc-overlay" for="__toc">
|
||
<div class="visually-hidden">Hide table of contents sidebar</div>
|
||
</label>
|
||
|
||
|
||
|
||
<div class="page">
|
||
<header class="mobile-header">
|
||
<div class="header-left">
|
||
<label class="nav-overlay-icon" for="__navigation">
|
||
<div class="visually-hidden">Toggle site navigation sidebar</div>
|
||
<i class="icon"><svg><use href="#svg-menu"></use></svg></i>
|
||
</label>
|
||
</div>
|
||
<div class="header-center">
|
||
<a href="index.html"><div class="brand">Reticulum Network Stack 0.7.3 beta documentation</div></a>
|
||
</div>
|
||
<div class="header-right">
|
||
<div class="theme-toggle-container theme-toggle-header">
|
||
<button class="theme-toggle">
|
||
<div class="visually-hidden">Toggle Light / Dark / Auto color theme</div>
|
||
<svg class="theme-icon-when-auto"><use href="#svg-sun-half"></use></svg>
|
||
<svg class="theme-icon-when-dark"><use href="#svg-moon"></use></svg>
|
||
<svg class="theme-icon-when-light"><use href="#svg-sun"></use></svg>
|
||
</button>
|
||
</div>
|
||
<label class="toc-overlay-icon toc-header-icon" for="__toc">
|
||
<div class="visually-hidden">Toggle table of contents sidebar</div>
|
||
<i class="icon"><svg><use href="#svg-toc"></use></svg></i>
|
||
</label>
|
||
</div>
|
||
</header>
|
||
<aside class="sidebar-drawer">
|
||
<div class="sidebar-container">
|
||
|
||
<div class="sidebar-sticky"><a class="sidebar-brand" href="index.html">
|
||
|
||
<div class="sidebar-logo-container">
|
||
<img class="sidebar-logo" src="_static/rns_logo_512.png" alt="Logo"/>
|
||
</div>
|
||
|
||
<span class="sidebar-brand-text">Reticulum Network Stack 0.7.3 beta documentation</span>
|
||
|
||
</a><form class="sidebar-search-container" method="get" action="search.html" role="search">
|
||
<input class="sidebar-search" placeholder="Search" name="q" aria-label="Search">
|
||
<input type="hidden" name="check_keywords" value="yes">
|
||
<input type="hidden" name="area" value="default">
|
||
</form>
|
||
<div id="searchbox"></div><div class="sidebar-scroll"><div class="sidebar-tree">
|
||
<ul class="current">
|
||
<li class="toctree-l1"><a class="reference internal" href="whatis.html">What is Reticulum?</a></li>
|
||
<li class="toctree-l1"><a class="reference internal" href="gettingstartedfast.html">Getting Started Fast</a></li>
|
||
<li class="toctree-l1"><a class="reference internal" href="using.html">Using Reticulum on Your System</a></li>
|
||
<li class="toctree-l1"><a class="reference internal" href="understanding.html">Understanding Reticulum</a></li>
|
||
<li class="toctree-l1"><a class="reference internal" href="hardware.html">Communications Hardware</a></li>
|
||
<li class="toctree-l1"><a class="reference internal" href="interfaces.html">Configuring Interfaces</a></li>
|
||
<li class="toctree-l1 current current-page"><a class="current reference internal" href="#">Building Networks</a></li>
|
||
<li class="toctree-l1"><a class="reference internal" href="examples.html">Code Examples</a></li>
|
||
<li class="toctree-l1"><a class="reference internal" href="support.html">Support Reticulum</a></li>
|
||
</ul>
|
||
<ul>
|
||
<li class="toctree-l1"><a class="reference internal" href="reference.html">API Reference</a></li>
|
||
</ul>
|
||
|
||
</div>
|
||
</div>
|
||
|
||
</div>
|
||
|
||
</div>
|
||
</aside>
|
||
<div class="main">
|
||
<div class="content">
|
||
<div class="article-container">
|
||
<a href="#" class="back-to-top muted-link">
|
||
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
|
||
<path d="M13 20h-2V8l-5.5 5.5-1.42-1.42L12 4.16l7.92 7.92-1.42 1.42L13 8v12z"></path>
|
||
</svg>
|
||
<span>Back to top</span>
|
||
</a>
|
||
<div class="content-icon-container">
|
||
<div class="theme-toggle-container theme-toggle-content">
|
||
<button class="theme-toggle">
|
||
<div class="visually-hidden">Toggle Light / Dark / Auto color theme</div>
|
||
<svg class="theme-icon-when-auto"><use href="#svg-sun-half"></use></svg>
|
||
<svg class="theme-icon-when-dark"><use href="#svg-moon"></use></svg>
|
||
<svg class="theme-icon-when-light"><use href="#svg-sun"></use></svg>
|
||
</button>
|
||
</div>
|
||
<label class="toc-overlay-icon toc-content-icon" for="__toc">
|
||
<div class="visually-hidden">Toggle table of contents sidebar</div>
|
||
<i class="icon"><svg><use href="#svg-toc"></use></svg></i>
|
||
</label>
|
||
</div>
|
||
<article role="main">
|
||
<section id="building-networks">
|
||
<span id="networks-main"></span><h1>Building Networks<a class="headerlink" href="#building-networks" title="Permalink to this heading">#</a></h1>
|
||
<p>This chapter will provide you with the knowledge needed to build networks with
|
||
Reticulum, which can often be easier than using traditional stacks, since you
|
||
don’t have to worry about coordinating addresses, subnets and routing for an
|
||
entire network that you might not know how will evolve in the future. With
|
||
Reticulum, you can simply add more segments to your network when it becomes
|
||
necessary, and Reticulum will handle the convergence of the entire network
|
||
automatically.</p>
|
||
<section id="concepts-overview">
|
||
<h2>Concepts & Overview<a class="headerlink" href="#concepts-overview" title="Permalink to this heading">#</a></h2>
|
||
<p>There are important points that need to be kept in mind when building networks
|
||
with Reticulum:</p>
|
||
<blockquote>
|
||
<div><ul>
|
||
<li><div class="line-block">
|
||
<div class="line">In a Reticulum network, any node can autonomously generate as many addresses
|
||
(called <em>destinations</em> in Reticulum terminology) as it needs, which become
|
||
globally reachable to the rest of the network. There is no central point of
|
||
control over the address space.</div>
|
||
</div>
|
||
</li>
|
||
<li><div class="line-block">
|
||
<div class="line">Reticulum was designed to handle both very small, and very large networks.
|
||
While the address space can support billions of endpoints, Reticulum is
|
||
also very useful when just a few devices needs to communicate.</div>
|
||
</div>
|
||
</li>
|
||
<li><div class="line-block">
|
||
<div class="line">Low-bandwidth networks, like LoRa and packet radio, can interoperate and
|
||
interconnect with much larger and higher bandwidth networks without issue.
|
||
Reticulum automatically manages the flow of information to and from various
|
||
network segments, and when bandwidth is limited, local traffic is prioritised.</div>
|
||
</div>
|
||
</li>
|
||
<li><div class="line-block">
|
||
<div class="line">Reticulum provides sender/initiator anonymity by default. There is no way
|
||
to filter traffic or discriminate it based on the source of the traffic.</div>
|
||
</div>
|
||
</li>
|
||
<li><div class="line-block">
|
||
<div class="line">All traffic is encrypted using ephemeral keys generated by an Elliptic Curve
|
||
Diffie-Hellman key exchange on Curve25519. There is no way to inspect traffic
|
||
contents, and no way to prioritise or throttle certain kinds of traffic.
|
||
All transport and routing layers are thus completely agnostic to traffic type,
|
||
and will pass all traffic equally.</div>
|
||
</div>
|
||
</li>
|
||
<li><div class="line-block">
|
||
<div class="line">Reticulum can function both with and without infrastructure. When <em>transport
|
||
nodes</em> are available, they can route traffic over multiple hops for other
|
||
nodes, and will function as a distributed cryptographic keystore. When there
|
||
is no transport nodes available, all nodes that are within communication range
|
||
can still communicate.</div>
|
||
</div>
|
||
</li>
|
||
<li><div class="line-block">
|
||
<div class="line">Every node can become a transport node, simply by enabling it in it’s
|
||
configuration, but there is no need for every node on the network to be a
|
||
transport node. Letting every node be a transport node will in most cases
|
||
degrade the performance and reliability of the network.</div>
|
||
</div>
|
||
<blockquote>
|
||
<div><p><em>In general terms, if a node is stationary, well-connected and kept running
|
||
most of the time, it is a good candidate to be a transport node. For optimal
|
||
performance, a network should contain the amount of transport nodes that
|
||
provides connectivity to the intended area / topography, and not many more
|
||
than that.</em></p>
|
||
</div></blockquote>
|
||
</li>
|
||
<li><div class="line-block">
|
||
<div class="line">Reticulum is designed to work reliably in open, trustless environments. This
|
||
means you can use it to create open-access networks, where participants can
|
||
join and leave in an free and unorganised manner. This property allows an
|
||
entirely new, and so far, mostly unexplored class of networked applications,
|
||
where networks, and the information flow within them can form and dissolve
|
||
organically.</div>
|
||
</div>
|
||
</li>
|
||
<li><div class="line-block">
|
||
<div class="line">You can just as easily create closed networks, since Reticulum allows you to
|
||
add authentication to any interface. This means you can restrict access on
|
||
any interface type, even when using legacy devices, such as modems. You can
|
||
also mix authenticated and open interfaces on the same system. See the
|
||
<a class="reference internal" href="interfaces.html#interfaces-options"><span class="std std-ref">Common Interface Options</span></a> section of the <a class="reference internal" href="interfaces.html#interfaces-main"><span class="std std-ref">Interfaces</span></a>
|
||
chapter of this manual for information on how to set up interface authentication.</div>
|
||
</div>
|
||
</li>
|
||
</ul>
|
||
</div></blockquote>
|
||
<p>Reticulum allows you to mix very different kinds of networking mediums into a
|
||
unified mesh, or to keep everything within one medium. You could build a “virtual
|
||
network” running entirely over the Internet, where all nodes communicate over TCP
|
||
and UDP “channels”. You could also build such a network using other already-established
|
||
communications channels as the underlying carrier for Reticulum.</p>
|
||
<p>However, most real-world networks will probably involve either some form of
|
||
wireless or direct hardline communications. To allow Reticulum to communicate
|
||
over any type of medium, you must specify it in the configuration file, by default
|
||
located at <code class="docutils literal notranslate"><span class="pre">~/.reticulum/config</span></code>. See the <a class="reference internal" href="interfaces.html#interfaces-main"><span class="std std-ref">Supported Interfaces</span></a>
|
||
chapter of this manual for interface configuration examples.</p>
|
||
<p>Any number of interfaces can be configured, and Reticulum will automatically
|
||
decide which are suitable to use in any given situation, depending on where
|
||
traffic needs to flow.</p>
|
||
</section>
|
||
<section id="example-scenarios">
|
||
<h2>Example Scenarios<a class="headerlink" href="#example-scenarios" title="Permalink to this heading">#</a></h2>
|
||
<p>This section illustrates a few example scenarios, and how they would, in general
|
||
terms, be planned, implemented and configured.</p>
|
||
<section id="interconnected-lora-sites">
|
||
<h3>Interconnected LoRa Sites<a class="headerlink" href="#interconnected-lora-sites" title="Permalink to this heading">#</a></h3>
|
||
<p>An organisation wants to provide communication and information services to it’s
|
||
members, which are located mainly in three separate areas. Three suitable hill-top
|
||
locations are found, where the organisation can install equipment: Site A, B and C.</p>
|
||
<p>Since the amount of data that needs to be exchanged between users is mainly text-
|
||
based, the bandwidth requirements are low, and LoRa radios are chosen to connect
|
||
users to the network.</p>
|
||
<p>Due to the hill-top locations found, there is radio line-of-sight between site A
|
||
and B, and also between site B and C. Because of this, the organisation does not
|
||
need to use the Internet to interconnect the sites, but purchases four Point-to-Point
|
||
WiFi based radios for interconnecting the sites.</p>
|
||
<p>At each site, a Raspberry Pi is installed to function as a gateway. A LoRa radio
|
||
is connected to the Pi with a USB cable, and the WiFi radio is connected to the
|
||
Ethernet port of the Pi. At site B, two WiFi radios are needed to be able to reach
|
||
both site A and site C, so an extra Ethernet adapter is connected to the Pi in
|
||
this location.</p>
|
||
<p>Once the hardware has been installed, Reticulum is installed on all the Pis, and at
|
||
site A and C, one interface is added for the LoRa radio, as well as one for the WiFi
|
||
radio. At site B, an interface for the LoRa radio, and one interface for each WiFi
|
||
radio is added to the Reticulum configuration file. The transport node option is
|
||
enabled in the configuration of all three gateways.</p>
|
||
<p>The network is now operational, and ready to serve users across all three areas.
|
||
The organisation prepares a LoRa radio that is supplied to the end users, along
|
||
with a Reticulum configuration file, that contains the right parameters for
|
||
communicating with the LoRa radios installed at the gateway sites.</p>
|
||
<p>Once users connect to the network, anyone will be able to communicate with anyone
|
||
else across all three sites.</p>
|
||
</section>
|
||
<section id="bridging-over-the-internet">
|
||
<h3>Bridging Over the Internet<a class="headerlink" href="#bridging-over-the-internet" title="Permalink to this heading">#</a></h3>
|
||
<p>As the organisation grows, several new communities form in places too far away
|
||
from the core network to be reachable over WiFi links. New gateways similar to those
|
||
previously installed are set up for the new communities at the new sites D and E, but
|
||
they are islanded from the core network, and only serve the local users.</p>
|
||
<p>After investigating the options, it is found that it is possible to install an
|
||
Internet connection at site A, and an interface on the Internet connection is
|
||
configured for Reticulum on the Raspberry Pi at site A.</p>
|
||
<p>A member of the organisation at site D, named Dori, is willing to help by sharing
|
||
the Internet connection she already has in her home, and is able to leave a Raspberry
|
||
Pi running. A new Reticulum interface is configured on her Pi, connecting to the newly
|
||
enabled Internet interface on the gateway at site A. Dori is now connected to both
|
||
all the nodes at her own local site (through the hill-top LoRa gateway), and all the
|
||
combined users of sites A, B and C. She then enables transport on her node, and
|
||
traffic from site D can now reach everyone at site A, B and C, and vice versa.</p>
|
||
</section>
|
||
<section id="growth-and-convergence">
|
||
<h3>Growth and Convergence<a class="headerlink" href="#growth-and-convergence" title="Permalink to this heading">#</a></h3>
|
||
<p>As the organisation grows, more gateways are added to keep up with the growing user
|
||
base. Some local gateways even add VHF radios and packet modems to reach outlying users
|
||
and communities that are out of reach for the LoRa radios and WiFi backhauls.</p>
|
||
<p>As more sites, gateways and users are connected, the amount of coordination required
|
||
is kept to a minimum. If one community wants to add connectivity to the next one
|
||
over, it can simply be done without having to involve everyone or coordinate address
|
||
space or routing tables.</p>
|
||
<p>With the added geographical coverage, the operators at site A one day find that
|
||
the original internet bridged interfaces are no longer utilised. The network has
|
||
converged to be completely self-connected, and the sites that were once poorly
|
||
connected outliers are now an integral part of the network.</p>
|
||
</section>
|
||
</section>
|
||
</section>
|
||
|
||
</article>
|
||
</div>
|
||
<footer>
|
||
|
||
<div class="related-pages">
|
||
<a class="next-page" href="examples.html">
|
||
<div class="page-info">
|
||
<div class="context">
|
||
<span>Next</span>
|
||
</div>
|
||
<div class="title">Code Examples</div>
|
||
</div>
|
||
<svg class="furo-related-icon"><use href="#svg-arrow-right"></use></svg>
|
||
</a>
|
||
<a class="prev-page" href="interfaces.html">
|
||
<svg class="furo-related-icon"><use href="#svg-arrow-right"></use></svg>
|
||
<div class="page-info">
|
||
<div class="context">
|
||
<span>Previous</span>
|
||
</div>
|
||
|
||
<div class="title">Configuring Interfaces</div>
|
||
|
||
</div>
|
||
</a>
|
||
</div>
|
||
<div class="bottom-of-page">
|
||
<div class="left-details">
|
||
<div class="copyright">
|
||
Copyright © 2023, Mark Qvist
|
||
</div>
|
||
Generated with <a href="https://www.sphinx-doc.org/">Sphinx</a> and
|
||
<a href="https://github.com/pradyunsg/furo">Furo</a>
|
||
|
||
</div>
|
||
<div class="right-details">
|
||
<div class="icons">
|
||
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
</footer>
|
||
</div>
|
||
<aside class="toc-drawer">
|
||
|
||
|
||
<div class="toc-sticky toc-scroll">
|
||
<div class="toc-title-container">
|
||
<span class="toc-title">
|
||
On this page
|
||
</span>
|
||
</div>
|
||
<div class="toc-tree-container">
|
||
<div class="toc-tree">
|
||
<ul>
|
||
<li><a class="reference internal" href="#">Building Networks</a><ul>
|
||
<li><a class="reference internal" href="#concepts-overview">Concepts & Overview</a></li>
|
||
<li><a class="reference internal" href="#example-scenarios">Example Scenarios</a><ul>
|
||
<li><a class="reference internal" href="#interconnected-lora-sites">Interconnected LoRa Sites</a></li>
|
||
<li><a class="reference internal" href="#bridging-over-the-internet">Bridging Over the Internet</a></li>
|
||
<li><a class="reference internal" href="#growth-and-convergence">Growth and Convergence</a></li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
|
||
</div>
|
||
</div>
|
||
</div>
|
||
|
||
|
||
</aside>
|
||
</div>
|
||
</div><script data-url_root="./" id="documentation_options" src="_static/documentation_options.js?v=cf108e5e"></script>
|
||
<script src="_static/doctools.js?v=888ff710"></script>
|
||
<script src="_static/sphinx_highlight.js?v=4825356b"></script>
|
||
<script src="_static/scripts/furo.js?v=2c7c1115"></script>
|
||
<script src="_static/clipboard.min.js?v=a7894cd8"></script>
|
||
<script src="_static/copybutton.js?v=f281be69"></script>
|
||
</body>
|
||
</html> |