mirror of
https://github.com/markqvist/Reticulum.git
synced 2025-12-10 06:05:55 -05:00
Updated documentation
This commit is contained in:
parent
02945f960d
commit
006c70cd09
14 changed files with 97 additions and 8 deletions
|
|
@ -131,6 +131,22 @@ When you have experimented with the basic examples, it's time to go read the
|
|||
:ref:`Understanding Reticulum<understanding-main>` chapter.
|
||||
|
||||
|
||||
Reticulum on ARM64
|
||||
==============================================
|
||||
On some architectures, including ARM64, not all dependencies have precompiled
|
||||
binaries. On such systems, you will need to install ``python3-dev`` before
|
||||
installing Reticulum or programs that depend on Reticulum.
|
||||
|
||||
.. code::
|
||||
|
||||
# Install Python and development packages
|
||||
sudo apt update
|
||||
sudo apt install python3 python3-pip python3-dev
|
||||
|
||||
# Install Reticulum
|
||||
python3 -m pip install rns
|
||||
|
||||
|
||||
Reticulum on Android
|
||||
==============================================
|
||||
Reticulum can be used on Android in different ways. The easiest way to get
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Auto Interface
|
|||
The Auto Interface enables communication with other discoverable Reticulum
|
||||
nodes over UDP. It does not need any functional IP infrastructure like
|
||||
routers or DHCP servers, but will require at least some sort of switching
|
||||
medium between peers (a wired switch, a WiFi access point or similar), and
|
||||
medium between peers (a wired switch, a hub, a WiFi access point or similar), and
|
||||
that link-local IPv6 is enabled in your operating system, which should be
|
||||
enabled by default in almost all OSes.
|
||||
|
||||
|
|
@ -47,6 +47,17 @@ enabled by default in almost all OSes.
|
|||
|
||||
group_id = reticulum
|
||||
|
||||
# You can also select specifically which
|
||||
# kernel networking devices to use.
|
||||
|
||||
devices = wlan0,eth1
|
||||
|
||||
# Or let AutoInterface use all suitable
|
||||
# devices except for a list of ignored ones.
|
||||
|
||||
ignored_devices = tun0,eth0
|
||||
|
||||
|
||||
If you are connected to the Internet with IPv6, and your provider will route
|
||||
IPv6 multicast, you can potentially configure the Auto Interface to globally
|
||||
autodiscover other Reticulum nodes within your selected Group ID. You can specify
|
||||
|
|
|
|||
|
|
@ -57,6 +57,7 @@ the same system.
|
|||
-q, --quiet
|
||||
--version show program's version number and exit
|
||||
|
||||
You can easily add ``rnsd`` as an always-on service by :ref:`configuring a service<using-systemd>`.
|
||||
|
||||
The rnstatus Utility
|
||||
====================
|
||||
|
|
@ -205,6 +206,7 @@ Using this methodology avoids potential naming mix-ups where physical devices
|
|||
might be plugged and unplugged in different orders, or when node name
|
||||
assignment varies from one boot to another.
|
||||
|
||||
.. _using-systemd:
|
||||
|
||||
Reticulum as a System Service
|
||||
=============================
|
||||
|
|
|
|||
|
|
@ -148,6 +148,20 @@ don’t use pip, but try this recipe:</p>
|
|||
<p>When you have experimented with the basic examples, it’s time to go read the
|
||||
<a class="reference internal" href="understanding.html#understanding-main"><span class="std std-ref">Understanding Reticulum</span></a> chapter.</p>
|
||||
</div>
|
||||
<div class="section" id="reticulum-on-arm64">
|
||||
<h2>Reticulum on ARM64<a class="headerlink" href="#reticulum-on-arm64" title="Permalink to this headline">¶</a></h2>
|
||||
<p>On some architectures, including ARM64, not all dependencies have precompiled
|
||||
binaries. On such systems, you will need to install <code class="docutils literal notranslate"><span class="pre">python3-dev</span></code> before
|
||||
installing Reticulum or programs that depend on Reticulum.</p>
|
||||
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># Install Python and development packages</span>
|
||||
<span class="n">sudo</span> <span class="n">apt</span> <span class="n">update</span>
|
||||
<span class="n">sudo</span> <span class="n">apt</span> <span class="n">install</span> <span class="n">python3</span> <span class="n">python3</span><span class="o">-</span><span class="n">pip</span> <span class="n">python3</span><span class="o">-</span><span class="n">dev</span>
|
||||
|
||||
<span class="c1"># Install Reticulum</span>
|
||||
<span class="n">python3</span> <span class="o">-</span><span class="n">m</span> <span class="n">pip</span> <span class="n">install</span> <span class="n">rns</span>
|
||||
</pre></div>
|
||||
</div>
|
||||
</div>
|
||||
<div class="section" id="reticulum-on-android">
|
||||
<h2>Reticulum on Android<a class="headerlink" href="#reticulum-on-android" title="Permalink to this headline">¶</a></h2>
|
||||
<p>Reticulum can be used on Android in different ways. The easiest way to get
|
||||
|
|
@ -201,6 +215,7 @@ here at a later point.</p>
|
|||
<li><a class="reference internal" href="#creating-a-network-with-reticulum">Creating a Network With Reticulum</a></li>
|
||||
<li><a class="reference internal" href="#develop-a-program-with-reticulum">Develop a Program with Reticulum</a></li>
|
||||
<li><a class="reference internal" href="#participate-in-reticulum-development">Participate in Reticulum Development</a></li>
|
||||
<li><a class="reference internal" href="#reticulum-on-arm64">Reticulum on ARM64</a></li>
|
||||
<li><a class="reference internal" href="#reticulum-on-android">Reticulum on Android</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
|
|
|
|||
|
|
@ -58,6 +58,7 @@ to participate in the development of Reticulum itself.</p>
|
|||
<li class="toctree-l2"><a class="reference internal" href="gettingstartedfast.html#creating-a-network-with-reticulum">Creating a Network With Reticulum</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="gettingstartedfast.html#develop-a-program-with-reticulum">Develop a Program with Reticulum</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="gettingstartedfast.html#participate-in-reticulum-development">Participate in Reticulum Development</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="gettingstartedfast.html#reticulum-on-arm64">Reticulum on ARM64</a></li>
|
||||
<li class="toctree-l2"><a class="reference internal" href="gettingstartedfast.html#reticulum-on-android">Reticulum on Android</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
|
|
|
|||
|
|
@ -58,7 +58,7 @@ manual.</p>
|
|||
<p>The Auto Interface enables communication with other discoverable Reticulum
|
||||
nodes over UDP. It does not need any functional IP infrastructure like
|
||||
routers or DHCP servers, but will require at least some sort of switching
|
||||
medium between peers (a wired switch, a WiFi access point or similar), and
|
||||
medium between peers (a wired switch, a hub, a WiFi access point or similar), and
|
||||
that link-local IPv6 is enabled in your operating system, which should be
|
||||
enabled by default in almost all OSes.</p>
|
||||
<div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># This example demonstrates a TCP server interface.</span>
|
||||
|
|
@ -75,6 +75,16 @@ enabled by default in almost all OSes.</p>
|
|||
<span class="c1"># specifying different Group IDs.</span>
|
||||
|
||||
<span class="n">group_id</span> <span class="o">=</span> <span class="n">reticulum</span>
|
||||
|
||||
<span class="c1"># You can also select specifically which</span>
|
||||
<span class="c1"># kernel networking devices to use.</span>
|
||||
|
||||
<span class="n">devices</span> <span class="o">=</span> <span class="n">wlan0</span><span class="p">,</span><span class="n">eth1</span>
|
||||
|
||||
<span class="c1"># Or let AutoInterface use all suitable</span>
|
||||
<span class="c1"># devices except for a list of ignored ones.</span>
|
||||
|
||||
<span class="n">ignored_devices</span> <span class="o">=</span> <span class="n">tun0</span><span class="p">,</span><span class="n">eth0</span>
|
||||
</pre></div>
|
||||
</div>
|
||||
<p>If you are connected to the Internet with IPv6, and your provider will route
|
||||
|
|
|
|||
Binary file not shown.
File diff suppressed because one or more lines are too long
|
|
@ -87,6 +87,7 @@ optional arguments:
|
|||
--version show program's version number and exit
|
||||
</pre></div>
|
||||
</div>
|
||||
<p>You can easily add <code class="docutils literal notranslate"><span class="pre">rnsd</span></code> as an always-on service by <a class="reference internal" href="#using-systemd"><span class="std std-ref">configuring a service</span></a>.</p>
|
||||
</div>
|
||||
<div class="section" id="the-rnstatus-utility">
|
||||
<h3>The rnstatus Utility<a class="headerlink" href="#the-rnstatus-utility" title="Permalink to this headline">¶</a></h3>
|
||||
|
|
@ -218,7 +219,7 @@ might be plugged and unplugged in different orders, or when node name
|
|||
assignment varies from one boot to another.</p>
|
||||
</div>
|
||||
<div class="section" id="reticulum-as-a-system-service">
|
||||
<h3>Reticulum as a System Service<a class="headerlink" href="#reticulum-as-a-system-service" title="Permalink to this headline">¶</a></h3>
|
||||
<span id="using-systemd"></span><h3>Reticulum as a System Service<a class="headerlink" href="#reticulum-as-a-system-service" title="Permalink to this headline">¶</a></h3>
|
||||
<p>Instead of starting Reticulum manually, you can install <code class="docutils literal notranslate"><span class="pre">rnsd</span></code> as a system
|
||||
service and have it start automatically at boot.</p>
|
||||
<p>If you installed Reticulum with <code class="docutils literal notranslate"><span class="pre">pip</span></code>, the <code class="docutils literal notranslate"><span class="pre">rnsd</span></code> program will most likely
|
||||
|
|
|
|||
|
|
@ -131,6 +131,22 @@ When you have experimented with the basic examples, it's time to go read the
|
|||
:ref:`Understanding Reticulum<understanding-main>` chapter.
|
||||
|
||||
|
||||
Reticulum on ARM64
|
||||
==============================================
|
||||
On some architectures, including ARM64, not all dependencies have precompiled
|
||||
binaries. On such systems, you will need to install ``python3-dev`` before
|
||||
installing Reticulum or programs that depend on Reticulum.
|
||||
|
||||
.. code::
|
||||
|
||||
# Install Python and development packages
|
||||
sudo apt update
|
||||
sudo apt install python3 python3-pip python3-dev
|
||||
|
||||
# Install Reticulum
|
||||
python3 -m pip install rns
|
||||
|
||||
|
||||
Reticulum on Android
|
||||
==============================================
|
||||
Reticulum can be used on Android in different ways. The easiest way to get
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Auto Interface
|
|||
The Auto Interface enables communication with other discoverable Reticulum
|
||||
nodes over UDP. It does not need any functional IP infrastructure like
|
||||
routers or DHCP servers, but will require at least some sort of switching
|
||||
medium between peers (a wired switch, a WiFi access point or similar), and
|
||||
medium between peers (a wired switch, a hub, a WiFi access point or similar), and
|
||||
that link-local IPv6 is enabled in your operating system, which should be
|
||||
enabled by default in almost all OSes.
|
||||
|
||||
|
|
@ -47,6 +47,17 @@ enabled by default in almost all OSes.
|
|||
|
||||
group_id = reticulum
|
||||
|
||||
# You can also select specifically which
|
||||
# kernel networking devices to use.
|
||||
|
||||
devices = wlan0,eth1
|
||||
|
||||
# Or let AutoInterface use all suitable
|
||||
# devices except for a list of ignored ones.
|
||||
|
||||
ignored_devices = tun0,eth0
|
||||
|
||||
|
||||
If you are connected to the Internet with IPv6, and your provider will route
|
||||
IPv6 multicast, you can potentially configure the Auto Interface to globally
|
||||
autodiscover other Reticulum nodes within your selected Group ID. You can specify
|
||||
|
|
|
|||
|
|
@ -57,6 +57,7 @@ the same system.
|
|||
-q, --quiet
|
||||
--version show program's version number and exit
|
||||
|
||||
You can easily add ``rnsd`` as an always-on service by :ref:`configuring a service<using-systemd>`.
|
||||
|
||||
The rnstatus Utility
|
||||
====================
|
||||
|
|
@ -205,6 +206,7 @@ Using this methodology avoids potential naming mix-ups where physical devices
|
|||
might be plugged and unplugged in different orders, or when node name
|
||||
assignment varies from one boot to another.
|
||||
|
||||
.. _using-systemd:
|
||||
|
||||
Reticulum as a System Service
|
||||
=============================
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue