jacob.eva/opencom_xl_firmware
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'master' of https://git.unsigned.io/markqvist/RNode_Firmware

Browse Source
This commit is contained in:
Mark Qvist 2023-01-13 16:53:52 +01:00
commit 779c62d714
12 changed files with 29 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Console/assets/css/water.css
View File

@ -766,6 +766,9 @@ img,
video {
max-width: 100%;
height: auto;
display: block;
margin-left: auto;
margin-right: auto;
}
hr {

BIN
Console/assets/gfx/nn.webp
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 24 KiB

After

Width:  |  Height:  |  Size: 9.9 KiB

BIN
Console/assets/gfx/sideband.webp
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 57 KiB

After

Width:  |  Height:  |  Size: 17 KiB

2
Console/build.py
View File

@ -24,7 +24,7 @@ document_start = """
<!DOCTYPE html>
<html>
<head>
<link rel="stylesheet" href="{ASSET_PATH}css/water.css?v=2">
<link rel="stylesheet" href="{ASSET_PATH}css/water.css?v=4">
<link rel="shortcut icon" type="image/x-icon" href="{ASSET_PATH}gfx/icon.png">
<meta charset="utf-8"/>
<title>{PAGE_TITLE}</title>

2
Console/source/builds/handheld.md
View File

@ -1,6 +1,6 @@
[date]: <> (2023-01-14)
[title]: <> (Handheld RNode)
[image]: <> (gfx/rnode_iso.png)
[image]: <> (gfx/rnode_iso.webp)
[excerpt]: <> (This RNode is suitable for mobile and handheld operation, and offers both wireless and wired connectivity to host devices. A good all-round unit. It is also suitable for permanent installation indoors.)
<div class="article_date">{DATE}</div>
## Handheld RNode Recipe

2
Console/source/guides/install_firmware.md
View File

@ -1,4 +1,4 @@
[date]: <> (2022-01-25)
[date]: <> (2023-01-12)
[title]: <> (Installing RNode Firmware on Supported Devices)
[image]: <> (images/a801c7a0-b75b-48c5-8ce7-8cb07012fc96-400x275.jpg)
[excerpt]: <> (If you have a T-Beam or LoRa32 device handy, it is very easy to get it set up for all the things that the RNode firmware allows you to do.)

2
Console/source/guides/2022_03_26.md → Console/source/guides/loracomms.md
View File

@ -1,4 +1,4 @@
[date]: <> (2022-03-26)
[date]: <> (2023-01-14)
[title]: <> (Private, Secure and Uncensorable Messaging Over a LoRa Mesh)
[image]: <> (images/g1p.jpeg)
[excerpt]: <> (Or: How to set up a completely private, independent and encrypted communication system in half an hour, using stuff you can buy for under $100.)

2
Console/source/guides/make_rnodes.md
View File

@ -1,4 +1,4 @@
[date]: <> (2022-01-26)
[date]: <> (2023-01-10)
[title]: <> (How To Make Your Own RNodes)
[image]: <> (images/e4261dcb-49e5-4cd3-856e-c44fb7522b32-400x275.jpg)
[excerpt]: <> (This article will outline the general process, and provide the information you need, for building your own RNode from a few basic modules. The RNode will be functionally identical to a commercially purchased board.)

2
Console/source/guides/tnc_mode.md
View File

@ -1,4 +1,4 @@
[date]: <> (2020-05-03)
[date]: <> (2023-01-07)
[title]: <> (Using RNodes With Amateur Radio Software)
[image]: <> (images/xastir2-e1643321757361-400x275.jpg)
[excerpt]: <> (If you want to use an RNode with amateur radio applications, like APRS or a packet radio BBS, you will need to put the device into TNC Mode. In this mode, an RNode will behave exactly like a KISS-compatible TNC, which will make it usable with any amateur radio software.)

2
Console/source/index.md
View File

@ -10,7 +10,7 @@ The tools and information contained in this RNode will allow you to replicate th
This repository also contains tools, software and information necessary to bootstrap networks and communications systems based on RNodes and Reticulum.
</td>
<td width="33%" style="vertical-align:middle;padding-right: 0;">
<img src="{ASSET_PATH}gfx/rnode_iso.png" width="100%"/></td>
<img src="{ASSET_PATH}gfx/rnode_iso.webp" width="100%"/></td>
</tr>
</tbody>
</table>

17
Console/source/qa.md
View File

@ -1,3 +1,18 @@
[title]: <> (Get Help)
[title]: <> (Questions & Answers)
## Questions & Answers
This section contains a list of common questions, and associated answers.
- **What are the system requirements for running Reticulum?**
Practically any system that can run Python3 can also run Reticulum. Any computer made since the early 2000's should work, provided it has a reasonably up-to-date operating system installed. Even low-power embedded devices with 256 megabytes of RAM will run Reticulum.
- **Does Reticulum work without the Internet?**
Yes. Reticulum *is* itself both a networking, and an inter-net protocol. A key difference between Reticulum and IPv4/v6, however, is that Reticulum does not require any central coordination or authority to work. As soon as two devices running Reticulum can talk to each other, they form a network. That network can dynamically grow to planetary-scale nets, split up, re-connect and heal in any number of ways, while still continuing to function. As long as there is *some sort of physical way* for two or more devices to communicate, Reticulum will allow them to form a secure and reliable network.
- **Who owns and controls the addresses I use on a Reticulum network?**
You do. Every address is in complete ownership and control of the person that created it.
- **If nobody centrally controls the addresses, will my address still be globally reachable?**
Yes. Reticulum ensures end-to-end connectivity. All addresses are globally and directly reachable. Reticulum has no concept of "private address spaces" and NAT, as you might be suffering from with IPv4.
- **Is communication over Reticulum encrypted?**
Yes. All traffic is end-to-end encrypted. Reticulum *is fundamentally unable to route unencrypted traffic*. Links established over Reticulum networks offer forward secrecy, by using ephemeral encryption keys.
- **Could you build a global Internet with Reticulum instead of IP?**
Yes. In theory this is completely possible, but it will take a lot of refinement, development, hardware support and adoption to transition the global base-layer for communication to Reticulum. Please [help us]({ASSET_PATH}contribute.html) towards this goal!
- **Is Reticulum as fast and optimised as my favorite TCP/IP stack?**
Currently not, but we are working towards being much faster than IP. The primary focus of Reticulum has been to build an understandable and well-documented *reference implementation*, that works exceptionally well over medium-bandwidth to extremely low-bandwidth forms of communication. This focus is very valuable, since it allows people to build secure communications networks that span vast areas, with very simple hardware, and very little cost.

2
Console/source/s_sideband.md
View File

@ -1,4 +1,4 @@
[title]: <> (Nomad Network)
[title]: <> (Sideband)
## Sideband
Sideband is an LXMF client for Android, Linux and macOS. It has built-in support for communicating over RNodes, and many other mediums, such as Packet Radio, WiFi, I2P, or anything else Reticulum supports.