diff --git a/docs/.vitepress/config.mts b/docs/.vitepress/config.mts index e87b1c0..d908316 100644 --- a/docs/.vitepress/config.mts +++ b/docs/.vitepress/config.mts @@ -98,13 +98,33 @@ function sidebarGuide(): DefaultTheme.SidebarItem[] { collapsed: false, items: [ { text: 'Connecting to the router', link: '/guide/connecting' }, - { text: 'Packages selection', - link: '/guide/packages-selection', + { text: 'Using LimeApp', + link: '/guide/limeapp/', + collapsed: true, + items: [ + { text: 'Overview', link: '/guide/limeapp/' }, + { text: 'Accessing LimeApp', link: '/guide/limeapp/access' }, + { text: 'A tour of the menu', link: '/guide/limeapp/menu' }, + { text: 'Status', link: '/guide/limeapp/status' }, + { text: 'Alignment', link: '/guide/limeapp/alignment' }, + { text: 'Map', link: '/guide/limeapp/map' }, + { text: 'Diagnostics', link: '/guide/limeapp/diagnostics' }, + { text: 'Notes', link: '/guide/limeapp/notes' }, + { text: 'Node configuration', link: '/guide/limeapp/node-config' }, + { text: 'Network configuration', link: '/guide/limeapp/network-config' }, + { text: 'Firmware', link: '/guide/limeapp/firmware' }, + { text: 'Visit neighbor node', link: '/guide/limeapp/visit-node' }, + { text: 'Remote support', link: '/guide/limeapp/remote-support' }, + { text: 'Aligning antennas', link: '/guide/limeapp/aligning-antennas' }, + ] + }, + { text: 'Packages selection', + link: '/guide/packages-selection', collapsed: true, items: [ { text: 'Network Profiles', link: '/guide/network-profiles' } ] }, - { text: 'Build LibreMesh', + { text: 'Build LibreMesh', link: '/build/', collapsed: true, items: [ diff --git a/docs/guide/connecting.md b/docs/guide/connecting.md index 6164d99..95010b5 100644 --- a/docs/guide/connecting.md +++ b/docs/guide/connecting.md @@ -13,6 +13,13 @@ These addresses are available as well: - http://\[fd0d:fe46:8ce8::1\] - default anygw ipv6 - http://\[fd0d:fe46:8ce8::x\:xx\] - node default LAN `br-lan` ipv6 address +The recommended way to access the node on a LibreRouter is through the +**LimeApp** web interface that comes preinstalled. It is a friendlier +alternative to LuCI/SSH for everyday node administration and is the +default UI of LibreRouterOS. See the full +[Using LimeApp](/guide/limeapp/) guide for a tour of its features +(status, alignment, diagnostics, firmware update, etc.). + ![lime-app](/lime-app.png) ## via SSH diff --git a/docs/guide/limeapp/access.md b/docs/guide/limeapp/access.md new file mode 100644 index 0000000..75c7f2d --- /dev/null +++ b/docs/guide/limeapp/access.md @@ -0,0 +1,24 @@ +--- +outline: deep +--- + +# Accessing LimeApp + +The most common way to reach LimeApp is from the **Wi-Fi connection** of the phone or notebook you are using. + +1. Turn off the mobile data connection. +2. Connect your device to the Wi-Fi zone of the LibreRouter. +3. Open a browser (Chrome, Firefox, etc.). +4. Type [`http://minodo.info`](http://minodo.info) in the address bar. + +![Accessing LimeApp from Wi-Fi](/guide/limeapp/images/access_wifi.png) + +You can also reach LimeApp via a **wired connection**: plug a network cable from the LAN port of the LibreRouter (or its PoE injector) into the Ethernet port of your notebook or computer. + +![Accessing LimeApp from a wired connection](/guide/limeapp/images/access_cable.png) + +See also the [Connecting to the router](/guide/connecting) page for the full list of hostnames and IP addresses that can be used to reach a node. + +--- + +> **Attribution.** Translated from [«¿Cómo acceder?»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/como-acceder/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/aligning-antennas.md b/docs/guide/limeapp/aligning-antennas.md new file mode 100644 index 0000000..0dba304 --- /dev/null +++ b/docs/guide/limeapp/aligning-antennas.md @@ -0,0 +1,114 @@ +--- +outline: deep +--- + +# Aligning the antennas of a LibreRouter with LimeApp + +Achieving the best possible alignment on a Wi-Fi link is very important for the proper functioning of the community network and its performance. + +It is **strongly recommended** to aim the antennas as well as possible, even when the perceived usability of the network is acceptable to the people using it. Stacking links of insufficient quality leads to a network with problems that are hard to diagnose, or to diagnostics that cannot be trusted. + +It is a low-complexity task that requires dedication, patience, and time. + +## Contents + +- [🙌 Recommendations before you start](#🙌-recommendations-before-you-start) +- [✅ Verify that the LibreRouters are linked](#✅-verify-that-the-librerouters-are-linked) +- [🎯 Let's align!](#🎯-let-s-align) + - [Using the Alignment tool of LimeApp](#using-the-alignment-tool-of-limeapp) + - [Going for it!](#going-for-it) +- [📌 Things to keep in mind](#📌-things-to-keep-in-mind) + - [Long links](#long-links) + - [Covering an area](#covering-an-area) + +## 🙌 Recommendations before you start + +To work properly, a few prerequisites and materials need to be checked: + +- **Check the weather conditions in advance.** Do not work on windy, drizzly, or extremely hot/cold days. +- **Wear appropriate clothing, footwear, and safety equipment**, especially for work at dangerous heights. +- **Verify the correct installation of the node and its mounting structure.** + - Check that everything is firm, with no pendulum or rotational movement, and that the device is solidly attached to the mast. You can follow this [checklist](https://conectividad.altermundi.net/wp-content/uploads/2021/01/Montaje-Lista-de-control_sin-rulos-y-numeros-en-antenas.png). + - Whenever you are at the height of the node, take the opportunity to inspect the integrity of all its parts: connectors firmly attached, cables and enclosure in good shape, LEDs on, etc. When antennas are out of reach, this task becomes much harder. Whenever possible, place them within reach and in comfortable working positions, even if that is not the highest point. +- **Loosen the antennas a little**, but tight enough that they do not move unless you hold them. This lets you move them during alignment. +- **Confirm a clear line of sight.** The electromagnetic waves of Wi-Fi links weaken significantly when they pass through objects, trees, and other obstacles. For this reason, it is important to verify that there is a clear line of sight between the two mounting points. The [Participatory Mapping of a Free, Community Network](https://conectividad.altermundi.net/documentacion/mapeo-participativo-de-una-red-libre-y-comunitaria/) material can be very useful. +- **Analyse the possible link on a map.** Look at a satellite map in advance, draw the line, and reference the alignment with something close-by that is visible to the naked eye. + ![Satellite map preview](/guide/limeapp/images/aligning_satellite_map.png) +- **Analyse the elevation profile of the terrain and assess the feasibility of the link.** In this profile, pay attention to the exact location of both antennas, the line of sight between them, the curvature of the Earth, and the Fresnel zone. There are link calculators that combine this data automatically — you only need to learn a little about how to use them. Two free options, for example, are [airLink](https://link.ui.com/) and [LigoWave](https://linkcalc.ligowave.com/Account/Login). + ![Elevation profile](/guide/limeapp/images/aligning_elevation_profile.png) + +## ✅ Verify that the LibreRouters are linked + +- **If the LibreRouter nodes are about to be installed:** power them on beforehand to confirm they work and link correctly. Trying to align antennas that are already mounted but do not link can be very frustrating. +- **If the LibreRouter nodes are already installed:** make sure they are powered on and that LimeApp is reachable from both. + +::: warning If the LibreRouter does not see any signal, or does not see the signal of the node you want to point at — i.e. it does not link to the target node: +- LimeApp reports the situation on a screen that reads «This radio is not linked to other nodes». +- Check that you are pointing correctly: + If you are aligning Antenna 1 (Radio1), make sure you are pointing at Antenna 1 of the other node. Same for Antenna 2 (Radio2). You can align 1↔1 and 2↔2 without crossing them. + ![No link warning](/guide/limeapp/images/aligning_no_link_warning.png) +- Try a first *«by eye»* alignment until you obtain a link, even if the signal is poor. +- If you cannot get any link after a while, re-check that both devices power on and reach LimeApp. If the problem persists, re-evaluate the line of sight, inspect the integrity of the node parts, and/or test the devices unmounted at a short distance. +::: + +## 🎯 Let's align! + +### Using the Alignment tool of LimeApp + +All the details about this tool are in the [Alignment](/guide/limeapp/alignment) page. Don't skip it! 🤓 + +1. Open [LimeApp](/guide/limeapp/access) of the base node you are working from. +2. From the menu, go to the [Alignment](/guide/limeapp/alignment) screen. +3. Pick the node you are aligning against, and open the specific, detailed information. + +![Alignment tool](/guide/limeapp/images/aligning_tool.png) + +The goal is to reach a value as close to **0** (zero) as possible. This value represents the quality of the link, measured in dBm (decibel-milliwatts). It is always a negative number, so -65 means a better signal than -72. + +LimeApp uses the colours **green**, **yellow**, and **red** to identify whether a link signal is of good, medium, or low quality. + +![Signal value colour coding](/guide/limeapp/images/aligning_signal_value.png) + +✔ Treat the best value you have repeated several times as valid. +✘ Discard isolated values that represent a sudden jump in the measurement, however good they look, because they are not representative. +🟡 If the best value you can get is a medium-quality link, the community may decide that this link is necessary for the network, even if you cannot improve the signal value. +🔴 Low-quality links provide a very poor user experience and erode the social fabric of the network. It is best to refuse them. + +### Going for it! + +**The key is to move the antenna slowly and millimetre by millimetre**, paying attention to the change of value on the screen. + +![Slow movement](/guide/limeapp/images/aligning_movement.png) + +1. **Move the desired antenna horizontally ↔** until you get the best value. +2. **Do the same vertically ↕** until you reach a value that is the same as or better than the one obtained during the horizontal movement. +3. **Finally, repeat the procedure horizontally**, stopping at the best value you recorded or any improvement on it. +4. **Once the best alignment is achieved:** + - Tighten the antenna to the mast or structure, firmly, so that it does not move in the wind. + - Check that the previously achieved value does not change. It is common for tightening to cause small movements that worsen the result. + - Correct these variations as you tighten, slowly and patiently. +5. **Repeat the same task on the LibreRouter(s) at the other end of the link.** + +## 📌 Things to keep in mind + +### Long links + +On long links, alignment is more sensitive to movement because the illumination angle widens. + +![Long links](/guide/limeapp/images/aligning_long_links.png) + +### Covering an area + +In a mesh network, sometimes you decide to point at, or *illuminate*, an area or several nodes at once, instead of a single specific node. In that case, you can point at the most central node of the area of interest, and check that the signal level is acceptable at every node to be linked. Don't forget that all the involved nodes must use the same radio/antenna. + +![Covering an area](/guide/limeapp/images/aligning_cover_area.png) + +For example, in the image above, the coverage angle aims to reach nodes 1, 2, and 3 with reasonable link quality for each one: + +- Node 2 has the best link quality, being at the centre of the focus. +- Nodes 1 and 3 have lower but still acceptable link quality, thanks to the aperture angle of the LibreRouter's sectorial antennas. +- More distant points, which would link with low quality, should be avoided because they hurt the overall performance of the network, like node 4 in the example. + +--- + +> **Attribution.** Translated from [«Alinear antenas de un Equipo LibreRouter con LimeApp 1.4»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/alinear-antenas-de-un-equipo-librerouter-con-limeapp-1-4/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/alignment.md b/docs/guide/limeapp/alignment.md new file mode 100644 index 0000000..de688e6 --- /dev/null +++ b/docs/guide/limeapp/alignment.md @@ -0,0 +1,66 @@ +--- +outline: deep +--- + +# Alignment + +The alignment screen is a tool for evaluating and improving the quality of the Wi-Fi link between the base node and one or more nodes within its range. It is used both at installation time and during diagnostics and maintenance. + +- [Main screen and associated nodes](#main-screen-and-associated-nodes) +- [Viewing the alignment info of a specific link](#viewing-the-alignment-info-of-a-specific-link) +- [When no possible link is found](#when-no-possible-link-is-found) +- [When a link loses signal](#when-a-link-loses-signal) + +## Main screen and associated nodes + +When you open the screen, this is the main view: + +![Alignment main screen](/guide/limeapp/images/alignment_radios.png) + +1. Two tabs, one for each radio of the LibreRouter. The selected tab is highlighted in bold. + - **Radio 1.** This tab shows the nodes associated with this radio, which corresponds to **Antenna 1** of the device. + - **Radio 2.** This tab shows the nodes associated with this radio, which corresponds to **Antenna 2** of the device. + +2. A list of the associated nodes with a brief summary. + +![Node list with link quality](/guide/limeapp/images/alignment_nodes.png) + + a. **The name of the node and the radio through which the base node is communicating with it.** + b. **Link-quality value.** A number that quantifies the strength of the signal, expressed in dBm (decibel-milliwatts). If the link is lost at some point, a cross is shown. + c. **Coloured line.** A visual reference for link quality: green means good, yellow/orange means medium, red means low. + +## Viewing the alignment info of a specific link + +Tapping a node's name opens a screen with the details of that link. It is useful when you want to point the base node at a specific neighbour, get more information, and avoid being confused by the other links. + +![Specific link details](/guide/limeapp/images/alignment_detail.png) + +1. **Link-quality value** in dBm (decibel-milliwatts). +2. **Signal-read-out speaker.** A voice reads out the current signal. It is useful while aligning: you can hear the value without looking at the screen. Enable or disable it from the same icon 🔈/🔇. +3. **Coloured reference line** for link quality. + ![Quality colour scale](/guide/limeapp/images/alignment_color_scale.png) +4. **The radio from which the base node is pointing.** +5. **The name of the node you are aligning against** and the radio it is on. +6. Best signal. Shows the best alignment achieved, with a seconds reference. + +To return to the main alignment screen, use the back button in the upper-left corner: + +![Back button](/guide/limeapp/images/alignment_back_button.png) + +## When no possible link is found + +If the base node does not see any signal on one of its radios, the screen reads «This radio is not linked to other nodes»: + +![No link found](/guide/limeapp/images/alignment_no_link.png) + +## When a link loses signal + +The following information is displayed: + +![Lost link](/guide/limeapp/images/alignment_lost.png) + +📌 For more information and recommendations, see [Aligning antennas of a LibreRouter with LimeApp](/guide/limeapp/aligning-antennas). + +--- + +> **Attribution.** Translated from [«Alineación»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/alineacion/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/diagnostics.md b/docs/guide/limeapp/diagnostics.md new file mode 100644 index 0000000..1efd6c2 --- /dev/null +++ b/docs/guide/limeapp/diagnostics.md @@ -0,0 +1,52 @@ +--- +outline: deep +--- + +# Diagnostics + +The diagnostics screen provides information and runs several evaluations on the path that the network automatically chooses to connect the base node to the Internet. + +There are two options: + +![Diagnostics options](/guide/limeapp/images/diagnostics_options.png) + +## 1. Only the gateway + +This is the basic diagnostic process that runs automatically when you open the screen. You can repeat it as many times as you want by pressing the button. + +It evaluates the bandwidth and the packet loss between the base node and the device that connects to the Internet (the gateway). + +![Only the gateway](/guide/limeapp/images/diagnostics_gateway.png) + +a. The **name of the base node** from which the evaluation is being run. +b. The path that the network chose the last time it connected the base node to the gateway. +c. The **bandwidth**, measured in megabits per second, and the **packet-loss** percentage, only between the base node and the gateway node (named «lapraviana» in this example). +d. Whether the base node has Internet connectivity through **IPv4**, **IPv6**, and the **DNS** service. + +## 2. Measure the whole path + +Starts an evaluation of the connectivity between the base node and every [intermediate node](https://hackmd.io/@0Rv5Hx8qSFeNy_M3SAM-Xw/SkjJ0Hwxu#Nodos-intermedios), including the gateway node and its Internet connection. + +![Measure the whole path](/guide/limeapp/images/diagnostics_full_path.png) + +a. The **name of the base node** from which the evaluation is being run. +b. The path that the network chose the last time it connected the base node to the gateway. For every [intermediate node](https://hackmd.io/@0Rv5Hx8qSFeNy_M3SAM-Xw/SkjJ0Hwxu#Nodos-intermedios), it shows the **bandwidth** measured between the base node and the intermediate node, plus the **packet loss** during the test. +c. Whether the base node has Internet connectivity through **IPv4**, **IPv6**, and the **DNS** service. + +📌 **Tips** + +- While a measurement is running, three animated dots are shown to indicate that you need to wait for the result. + ![Measurement in progress](/guide/limeapp/images/diagnostics_in_progress.png) +- The coloured bars under the per-node measurements vary in length ↔ according to the bandwidth, and in colour according to the packet loss. They are a graphical reference that, with experience, lets you tell at a glance whether a result is optimal, acceptable, or in clear need of improvement. + ![Diagnostics colour bars](/guide/limeapp/images/diagnostics_color_bars.png) +- If you need to evaluate or re-evaluate a single link along the path, tap the name of any intermediate node. LimeApp will then show the link-specific information between the base node and the node you tapped. + +--- + +If the network breaks and there is no working path between the base node and the gateway, LimeApp evaluates the last path that **did** work. When you select the *measure the whole path* option, the result is striking: the base node evaluates itself against every node of that path that is still in the network. Nodes that are no longer reachable come back with a **(Error)** message. + +![Broken path diagnostics](/guide/limeapp/images/diagnostics_broken_path.png) + +--- + +> **Attribution.** Translated from [«Diagnóstico»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/diagnostico/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/firmware.md b/docs/guide/limeapp/firmware.md new file mode 100644 index 0000000..7981287 --- /dev/null +++ b/docs/guide/limeapp/firmware.md @@ -0,0 +1,89 @@ +--- +outline: deep +--- + +# Firmware + +This screen lets you update the [LibreRouterOS](https://gitlab.com/librerouter/librerouteros/) firmware installed on the device. + +[Firmware](https://en.wikipedia.org/wiki/Firmware) is the collection of small programs (software) that tell the device what to do and how. Without firmware, the device does nothing useful. For LibreRouter to keep working, there is an ongoing development effort behind it. + +LibreRouterOS is based on [LibreMesh](https://libremesh.org), [OpenWrt](https://openwrt.org/), and other non-proprietary software components such as LimeApp. The project considers it important to accompany communities in co-creating their [free, community, and decentralised networks](https://conectividad.altermundi.net/documentacion/redes-libres-comunitarias-y-descentralizadas/), also through technical and development decisions. To learn more, visit the [Free Design](https://librerouter.org/es/libre-design-2/) section of the [LibreRouter](http://librerouter.org) project website. + +## Updating the firmware of a LibreRouter + +There are two options: + +1. One-click safe update. +2. Choose a firmware image from your device. + +![Firmware update options](/guide/limeapp/images/firmware_options.png) + +### Things to keep in mind + +- Access to this tool requires the shared administration password. +- When a new update is available, a notification appears at the top of the screen announcing it and leading to the same screens 👇 + ![New version notification](/guide/limeapp/images/firmware_notification.png) +- The update is performed safely (SafeUpgrade), and in case *something* breaks, the previous configuration is restored automatically. + +## 1. One-click safe update + +### Step-by-step instructions + +1. Press the **Download** button. + + ![Step 1 — download](/guide/limeapp/images/firmware_step1.png) + +2. Wait for the new LibreRouterOS firmware image to download. The button stays disabled until the process finishes. + + ![Step 2 — downloading](/guide/limeapp/images/firmware_step2.png) + +3. Press **Upgrade to LibreRouterOS 1.5**. + + ![Step 3 — upgrade](/guide/limeapp/images/firmware_step3.png) + +4. The upgrade starts. Wait until it finishes without disconnecting the LibreRouter. The estimated time is about 3 minutes. + + ![Step 4 — upgrading](/guide/limeapp/images/firmware_step4.png) + +5. The upgrade is complete. LimeApp needs to be **reloaded**. If it reloads correctly, the process is going well 🙂 + + ![Step 5 — reload](/guide/limeapp/images/firmware_step5.png) + +6. The main LimeApp screen appears with the notification at the top. If everything looks good, confirm the upgrade. First press the **Go** button. + + ![Step 6 — go to confirm](/guide/limeapp/images/firmware_step6.png) + +7. Then press **Confirm**. + + ![Step 7 — confirm](/guide/limeapp/images/firmware_step7.png) + +8. The firmware of the LibreRouter has been updated successfully. To verify, open the **Status** screen of LimeApp. The firmware-version field should now read LibreRouterOS 1.5. + + ![Step 8 — done](/guide/limeapp/images/firmware_step8.png) + +## 2. Choose a firmware image from your device + +Use this option to upgrade from a firmware file that you have already downloaded. + +1. Choose the *«Choose a firmware image from your device»* option. + + ![From file — option](/guide/limeapp/images/firmware_from_file1.png) + +2. Once the file is uploaded, press **Upgrade**. The rest of the process is the same as described above. + + ![From file — upload](/guide/limeapp/images/firmware_from_file2.png) + +## Something went wrong 🙁 + +- If LimeApp does not reload or something unexpected happens, the process is automatically reverted. Wait 10 minutes. +- If the update needs to be reverted, you can do so at step 7 above. + +## More to keep in mind + +- Other options and use cases exist. The [LibreRouter forum](http://foro.librerouter.org) is the place to ask, request help, and learn more. Everyone is welcome to participate! +- A companion document with instructions, recommendations, and procedures for updating community networks is being prepared. Coming soon! + +--- + +> **Attribution.** Translated from [«Firmware»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/firmware/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/index.md b/docs/guide/limeapp/index.md new file mode 100644 index 0000000..c4ac8f1 --- /dev/null +++ b/docs/guide/limeapp/index.md @@ -0,0 +1,44 @@ +--- +outline: deep +--- + +# Using LimeApp + +![LimeApp overview](/guide/limeapp/images/mockup.png) + +[LimeApp](https://github.com/libremesh/lime-app) is a web application that ships preinstalled on LibreRouter devices. It is a [free software](https://en.wikipedia.org/wiki/Free_software) project under constant development, growth, and improvement. + +One of its goals is to bring friendly and accessible tools for self-managing and co-creating pieces of the Internet by building community networks. + +It lets you measure, diagnose, and administer a community network, its nodes, and its links locally, **without an Internet connection**. + +LimeApp is available on every node of the community network as part of the LibreRouterOS operating system. Because it runs locally on each node, it requires neither an Internet connection nor an additional device to be used. + +![LimeApp in the browser](/guide/limeapp/images/minodoinfo_en-el-navegador_2.png) + +::: tip About the screenshots +The screenshots in this guide were captured from the Spanish build of LimeApp 1.4 (the only version published by the upstream project at the time). The buttons and labels described in the text use the **English** equivalents of those Spanish terms (for example, *Ingresar* → **Log in**, *Cambiar* → **Change**, *Descargar* → **Download**), which match the current English build of LimeApp. +::: + +## In this section + +| Page | Description | +| ---- | ----------- | +| [Accessing LimeApp](/guide/limeapp/access) | Steps to reach LimeApp from a Wi-Fi or wired connection. | +| [A tour of the menu](/guide/limeapp/menu) | A complete walkthrough of every screen and tool, with tutorials and videos. | +| [Aligning antennas](/guide/limeapp/aligning-antennas) | Step-by-step recommendations and procedure for aligning the antennas of a LibreRouter with LimeApp. | +| [Glossary](https://hackmd.io/@0Rv5Hx8qSFeNy_M3SAM-Xw/SkjJ0Hwxu) | A collection of terms and their explanations, handy for quick reference. | +| [Full PDF booklet](https://nube.altermundi.net/index.php/s/pkHBQjyj6qr7New) | All of the content compiled into a single printable PDF. | + +## Getting help + +The [LibreRouter forum](https://foro.librerouter.org/) is the place for support, shared experiences, and community help. + +![LimeApp in use — photo 1](/guide/limeapp/images/LimeApp_en-uso_1.jpg) +![LimeApp in use — photo 2](/guide/limeapp/images/LimeApp_en-uso_2.jpg) +![LimeApp in use — photo 3](/guide/limeapp/images/LimeApp_en-uso_3.jpg) +![LimeApp in use — photo 4](/guide/limeapp/images/LimeApp_en-uso_4.jpg) + +--- + +> **Attribution.** This page is a translation of [«Usar LimeApp 1.4»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/map.md b/docs/guide/limeapp/map.md new file mode 100644 index 0000000..37fb896 --- /dev/null +++ b/docs/guide/limeapp/map.md @@ -0,0 +1,32 @@ +--- +outline: deep +--- + +# Map + +The map shows the network that the base node belongs to, with both nodes and links rendered on top of a real-world map. + +![Map overview](/guide/limeapp/images/map_overview.png) + +1. **Zoom.** The **+** and **−** buttons zoom the map in and out. +2. This button can have different functions. + If the node has not been located yet, it reads: + a. **Locate my node.** Tapping the button shows a floating marker that you drag and drop on the map at the correct location. + b. **Confirm location.** Once placed, press this button to apply the change and confirm the node's position on the map. + If the node has already been located, it reads: + c. **Modify location.** Lets you re-position the node. + ![Locate / modify node](/guide/limeapp/images/map_locate_node.png) +3. Alternately, this button lets you choose between: + a. **Show community**, to see the full network on the map. + b. **Hide community**, to hide the links and locations of the other nodes, leaving only the base node on the map. + ![Show / hide community](/guide/limeapp/images/map_toggle_community.png) +4. **Map layers.** Switches the base map used to render the nodes and the network. Three options are available: OpenStreetMap, Google Maps Satellite, and Google Maps Hybrid. + ![Map layer selector](/guide/limeapp/images/map_layers.png) + +There is one more behaviour worth mentioning: tapping the icon of any node displays the name of the selected node. + +![Node tooltip on the map](/guide/limeapp/images/map_node_tooltip.png) + +--- + +> **Attribution.** Translated from [«Mapa»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/mapa/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/menu.md b/docs/guide/limeapp/menu.md new file mode 100644 index 0000000..2a2d106 --- /dev/null +++ b/docs/guide/limeapp/menu.md @@ -0,0 +1,93 @@ +--- +outline: deep +--- + +# A tour of the menu + +The menu icon ☰ sits in the upper-right corner. From there you can reach every screen and tool available in LimeApp. **Let's go through them!** + +![Menu overview](/guide/limeapp/images/menu-1-4.png) + +## Status + +The status screen shows general information about the node and the link. + +![Status screen icon](/guide/limeapp/images/Estado-510x510.png) + +→ See the [Status](/guide/limeapp/status) page for details. + +## Alignment + +A tool for evaluating and measuring the quality of the links. + +![Alignment icon](/guide/limeapp/images/Alineacion-510x510.png) + +→ See the [Alignment](/guide/limeapp/alignment) page for details. + +## Map + +Renders the network that the base node belongs to, with both nodes and links. + +![Map icon](/guide/limeapp/images/Mapa-510x510.png) + +→ See the [Map](/guide/limeapp/map) page for details. + +## Diagnostics + +Performs several evaluations of the path that the network automatically chooses to connect the base node to the Internet. + +![Diagnostics icon](/guide/limeapp/images/Diagnostico-510x510.png) + +→ See the [Diagnostics](/guide/limeapp/diagnostics) page for details. + +## Notes + +Lets you write and read information about the node or anything else the community wants to keep there. + +![Notes icon](/guide/limeapp/images/Notas-510x510.png) + +→ See the [Notes](/guide/limeapp/notes) page for details. + +## Node configuration + +Lets you edit the node's name. + +![Node configuration icon](/guide/limeapp/images/ConfigNodo-510x510.png) + +→ See the [Node configuration](/guide/limeapp/node-config) page for details. + +## Network configuration + +Lets you set a shared administration password for the network. + +![Network configuration icon](/guide/limeapp/images/ConfigRed-510x510.png) + +→ See the [Network configuration](/guide/limeapp/network-config) page for details. + +## Firmware + +Lets you update the firmware version of the node. + +![Firmware icon](/guide/limeapp/images/Firmware-510x510.png) + +→ See the [Firmware](/guide/limeapp/firmware) page for details. + +## Visit neighbor node + +Lets you reach the information of another node in the network. + +![Visit neighbor node icon](/guide/limeapp/images/Visitarnodo-510x510.png) + +→ See the [Visit neighbor node](/guide/limeapp/visit-node) page for details. + +## Remote support + +Gives easy access to the node even when you are outside the local network. + +![Remote support icon](/guide/limeapp/images/SoporteRemoto-510x510.png) + +→ See the [Remote support](/guide/limeapp/remote-support) page for details. + +--- + +> **Attribution.** Translated from [«Un paseo por el Menú 1.4»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/network-config.md b/docs/guide/limeapp/network-config.md new file mode 100644 index 0000000..50874d6 --- /dev/null +++ b/docs/guide/limeapp/network-config.md @@ -0,0 +1,26 @@ +--- +outline: deep +--- + +# Network configuration + +This screen lets you set a shared administration password for the network. + +![Network configuration screen](/guide/limeapp/images/network_config.png) + +1. **Type the desired password.** + It must satisfy the three conditions shown on the screen. Each condition shows a red cross ✘ when unmet and a green tick ✔ when met. +2. **Repeat the same password.** If the message *«The passwords do not match»* appears, re-type it carefully until they match. +3. **Press the Change button.** As confirmation, the message *«The shared password was successfully changed»* is displayed. + +::: warning +This decision should be made together with the people who administer the network. It is not a personal choice: it changes the password used to act upon the entire network. +::: + +::: warning +This is **not** the same as the Wi-Fi password. If you ever set them to the same value, change one of them immediately to improve the security of the node and the network. +::: + +--- + +> **Attribution.** Translated from [«Configuración de la Red»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/configuracion-de-la-red/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/node-config.md b/docs/guide/limeapp/node-config.md new file mode 100644 index 0000000..ea60d17 --- /dev/null +++ b/docs/guide/limeapp/node-config.md @@ -0,0 +1,17 @@ +--- +outline: deep +--- + +# Node configuration + +This screen lets you view and/or edit the name of the node. + +![Node configuration screen](/guide/limeapp/images/node_config.png) + +1. Enter the administration password, then press **Log in**. +2. The current name of the node is shown and can be edited in place. +3. To apply the change, press **Change**. + +--- + +> **Attribution.** Translated from [«Configuración del Nodo»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/configuracion-del-nodo/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/notes.md b/docs/guide/limeapp/notes.md new file mode 100644 index 0000000..81a58a2 --- /dev/null +++ b/docs/guide/limeapp/notes.md @@ -0,0 +1,23 @@ +--- +outline: deep +--- + +# Notes + +The notes screen is an editable text box. It is used to write and read information about the node, or any other information the community decides to add there. + +![Notes screen](/guide/limeapp/images/notes_screen.png) + +::: warning Don't forget to save +Make sure to press the **Save notes** button before leaving the screen, otherwise the changes will be lost. +::: + +Some examples of use that came up in community networks: + +- Recording the history of network maintenance. +- Notes about the characteristics of the node or its installation that need to be highlighted. +- A means of communication to coordinate community actions not directly related to the network. A world of possibilities! + +--- + +> **Attribution.** Translated from [«Notas»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/notas/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/remote-support.md b/docs/guide/limeapp/remote-support.md new file mode 100644 index 0000000..3b87c50 --- /dev/null +++ b/docs/guide/limeapp/remote-support.md @@ -0,0 +1,15 @@ +--- +outline: deep +--- + +# Remote support + +This screen lets you request support and technical assistance remotely. A session is started simply by pressing the **Create session** button. + +![Remote support screen](/guide/limeapp/images/remote_support.jpg) + +More information about how to start and maintain a remote-access session can be found in [this thread on the LibreRouter forum](https://foro.librerouter.org/t/nueva-herramienta-soporte-remoto/219). + +--- + +> **Attribution.** Translated from [«Soporte Remoto»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/soporte-remoto/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/status.md b/docs/guide/limeapp/status.md new file mode 100644 index 0000000..a22e6d2 --- /dev/null +++ b/docs/guide/limeapp/status.md @@ -0,0 +1,37 @@ +--- +outline: deep +--- + +# Status + +The status screen provides basic information about the node's performance. + +![Status screen](/guide/limeapp/images/Estado_num.png) + +1. **Header** + Shows the name of the [base node](https://hackmd.io/@0Rv5Hx8qSFeNy_M3SAM-Xw/SkjJ0Hwxu#Nodo-base) and the menu icon. + +2. **Most active link** + Shows information about the link between the [base node](https://hackmd.io/@0Rv5Hx8qSFeNy_M3SAM-Xw/SkjJ0Hwxu#Nodo-base) and the node it communicates with most directly within the network. + It also indicates the interface used for this link: `wlan1` or `wlan2`. `wlan1` refers to the radio/antenna labelled **1**, and `wlan2` to the one labelled **2**. + Next comes the amount of data, in megabytes (MB), transferred between the two nodes since they were last interconnected (which may be a short or a long time). + On the right it shows the quality of the link between the two devices — a quick way to evaluate whether the antennas of the node need to be re-oriented (see the [Alignment](/guide/limeapp/alignment) screen). + +3. **System** + Shows the uptime of the [base node](https://hackmd.io/@0Rv5Hx8qSFeNy_M3SAM-Xw/SkjJ0Hwxu#Nodo-base), i.e. how long it has been powered on. + This information is useful to detect whether a node reboots on its own, without the network maintainers intending it to. + It also reports the hardware version of the LibreRouter and the firmware version installed on it. + +4. **Internet connection** + Reports the following: + - **IPv4** — whether there is traffic sent and received using the IPv4 address of the node, i.e. whether the node has IPv4 Internet connectivity. + - **IPv6** — same as above, for IPv6. + - **DNS** — whether the node can reach the Domain Name System server, which maps domain names to the IP addresses that host them. + A red cross ✘ means the service is unavailable; a green tick ✔ means it is working. + +5. **IP addresses** + The IP addresses that the [base node](https://hackmd.io/@0Rv5Hx8qSFeNy_M3SAM-Xw/SkjJ0Hwxu#Nodo-base) uses to be identified inside the network. Often useful when monitoring and diagnosing the network. + +--- + +> **Attribution.** Translated from [«Estado»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/estado/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/guide/limeapp/visit-node.md b/docs/guide/limeapp/visit-node.md new file mode 100644 index 0000000..5943fe1 --- /dev/null +++ b/docs/guide/limeapp/visit-node.md @@ -0,0 +1,21 @@ +--- +outline: deep +--- + +# Visit neighbor node + +This option lets you reach the information of another node in the network that is connected to the base node. + +It makes it easy to diagnose other nodes in the network without having to physically visit them. It is also useful to investigate the performance of the network from the perspective of different nodes, allowing for a deeper and more detailed analysis of the shared infrastructure. + +![Visit neighbor node](/guide/limeapp/images/visit_node.png) + +1. Shows the **currently selected node**, i.e. the one you are working from. +2. **Switch selected node.** Provides the list of nodes the base node knows within the network, so you can choose from which node to continue investigating. +3. **Change button.** Pick the node to evaluate and press **Change**. + +This takes you to the **Status** screen of the newly selected node, and you can navigate the entire menu from that node. + +--- + +> **Attribution.** Translated from [«Visitar nodo vecino»](https://conectividad.altermundi.net/documentacion/usar-limeapp1-4/un-paseo-por-el-menu-1-4/visitar-nodo-vecino/) by [AlterMundi](https://altermundi.net/), licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/). diff --git a/docs/public/guide/limeapp/images/Alineacion-510x510.png b/docs/public/guide/limeapp/images/Alineacion-510x510.png new file mode 100644 index 0000000..8061a34 Binary files /dev/null and b/docs/public/guide/limeapp/images/Alineacion-510x510.png differ diff --git a/docs/public/guide/limeapp/images/ConfigNodo-510x510.png b/docs/public/guide/limeapp/images/ConfigNodo-510x510.png new file mode 100644 index 0000000..dab2225 Binary files /dev/null and b/docs/public/guide/limeapp/images/ConfigNodo-510x510.png differ diff --git a/docs/public/guide/limeapp/images/ConfigRed-510x510.png b/docs/public/guide/limeapp/images/ConfigRed-510x510.png new file mode 100644 index 0000000..894f034 Binary files /dev/null and b/docs/public/guide/limeapp/images/ConfigRed-510x510.png differ diff --git a/docs/public/guide/limeapp/images/Diagnostico-510x510.png b/docs/public/guide/limeapp/images/Diagnostico-510x510.png new file mode 100644 index 0000000..921b75d Binary files /dev/null and b/docs/public/guide/limeapp/images/Diagnostico-510x510.png differ diff --git a/docs/public/guide/limeapp/images/Estado-510x510.png b/docs/public/guide/limeapp/images/Estado-510x510.png new file mode 100644 index 0000000..f9e76f7 Binary files /dev/null and b/docs/public/guide/limeapp/images/Estado-510x510.png differ diff --git a/docs/public/guide/limeapp/images/Estado_num.png b/docs/public/guide/limeapp/images/Estado_num.png new file mode 100644 index 0000000..0ac8dbf Binary files /dev/null and b/docs/public/guide/limeapp/images/Estado_num.png differ diff --git a/docs/public/guide/limeapp/images/Firmware-510x510.png b/docs/public/guide/limeapp/images/Firmware-510x510.png new file mode 100644 index 0000000..7d5d8b8 Binary files /dev/null and b/docs/public/guide/limeapp/images/Firmware-510x510.png differ diff --git a/docs/public/guide/limeapp/images/Foro.png b/docs/public/guide/limeapp/images/Foro.png new file mode 100644 index 0000000..a614bfd Binary files /dev/null and b/docs/public/guide/limeapp/images/Foro.png differ diff --git a/docs/public/guide/limeapp/images/LimeApp_en-uso_1.jpg b/docs/public/guide/limeapp/images/LimeApp_en-uso_1.jpg new file mode 100644 index 0000000..3da68d2 Binary files /dev/null and b/docs/public/guide/limeapp/images/LimeApp_en-uso_1.jpg differ diff --git a/docs/public/guide/limeapp/images/LimeApp_en-uso_2.jpg b/docs/public/guide/limeapp/images/LimeApp_en-uso_2.jpg new file mode 100644 index 0000000..c152395 Binary files /dev/null and b/docs/public/guide/limeapp/images/LimeApp_en-uso_2.jpg differ diff --git a/docs/public/guide/limeapp/images/LimeApp_en-uso_3.jpg b/docs/public/guide/limeapp/images/LimeApp_en-uso_3.jpg new file mode 100644 index 0000000..71bb9b9 Binary files /dev/null and b/docs/public/guide/limeapp/images/LimeApp_en-uso_3.jpg differ diff --git a/docs/public/guide/limeapp/images/LimeApp_en-uso_4.jpg b/docs/public/guide/limeapp/images/LimeApp_en-uso_4.jpg new file mode 100644 index 0000000..1560ea4 Binary files /dev/null and b/docs/public/guide/limeapp/images/LimeApp_en-uso_4.jpg differ diff --git a/docs/public/guide/limeapp/images/Mapa-510x510.png b/docs/public/guide/limeapp/images/Mapa-510x510.png new file mode 100644 index 0000000..5951e9e Binary files /dev/null and b/docs/public/guide/limeapp/images/Mapa-510x510.png differ diff --git a/docs/public/guide/limeapp/images/Movimientos-1.png b/docs/public/guide/limeapp/images/Movimientos-1.png new file mode 100644 index 0000000..ec47912 Binary files /dev/null and b/docs/public/guide/limeapp/images/Movimientos-1.png differ diff --git a/docs/public/guide/limeapp/images/Notas-510x510.png b/docs/public/guide/limeapp/images/Notas-510x510.png new file mode 100644 index 0000000..1feb864 Binary files /dev/null and b/docs/public/guide/limeapp/images/Notas-510x510.png differ diff --git a/docs/public/guide/limeapp/images/SoporteRemoto-510x510.png b/docs/public/guide/limeapp/images/SoporteRemoto-510x510.png new file mode 100644 index 0000000..1d9a915 Binary files /dev/null and b/docs/public/guide/limeapp/images/SoporteRemoto-510x510.png differ diff --git a/docs/public/guide/limeapp/images/Usar-LimeApp-1-4_booklet2.png b/docs/public/guide/limeapp/images/Usar-LimeApp-1-4_booklet2.png new file mode 100644 index 0000000..8ff89db Binary files /dev/null and b/docs/public/guide/limeapp/images/Usar-LimeApp-1-4_booklet2.png differ diff --git a/docs/public/guide/limeapp/images/Visitarnodo-510x510.png b/docs/public/guide/limeapp/images/Visitarnodo-510x510.png new file mode 100644 index 0000000..65d0a4e Binary files /dev/null and b/docs/public/guide/limeapp/images/Visitarnodo-510x510.png differ diff --git a/docs/public/guide/limeapp/images/access_cable.png b/docs/public/guide/limeapp/images/access_cable.png new file mode 100644 index 0000000..b53e1bd Binary files /dev/null and b/docs/public/guide/limeapp/images/access_cable.png differ diff --git a/docs/public/guide/limeapp/images/access_wifi.png b/docs/public/guide/limeapp/images/access_wifi.png new file mode 100644 index 0000000..ba4b35a Binary files /dev/null and b/docs/public/guide/limeapp/images/access_wifi.png differ diff --git a/docs/public/guide/limeapp/images/aligning_cover_area.png b/docs/public/guide/limeapp/images/aligning_cover_area.png new file mode 100644 index 0000000..c27bf5c Binary files /dev/null and b/docs/public/guide/limeapp/images/aligning_cover_area.png differ diff --git a/docs/public/guide/limeapp/images/aligning_elevation_profile.png b/docs/public/guide/limeapp/images/aligning_elevation_profile.png new file mode 100644 index 0000000..dec302e Binary files /dev/null and b/docs/public/guide/limeapp/images/aligning_elevation_profile.png differ diff --git a/docs/public/guide/limeapp/images/aligning_long_links.png b/docs/public/guide/limeapp/images/aligning_long_links.png new file mode 100644 index 0000000..1620877 Binary files /dev/null and b/docs/public/guide/limeapp/images/aligning_long_links.png differ diff --git a/docs/public/guide/limeapp/images/aligning_movement.png b/docs/public/guide/limeapp/images/aligning_movement.png new file mode 100644 index 0000000..bd05d41 Binary files /dev/null and b/docs/public/guide/limeapp/images/aligning_movement.png differ diff --git a/docs/public/guide/limeapp/images/aligning_no_link_warning.png b/docs/public/guide/limeapp/images/aligning_no_link_warning.png new file mode 100644 index 0000000..d4f6bb6 Binary files /dev/null and b/docs/public/guide/limeapp/images/aligning_no_link_warning.png differ diff --git a/docs/public/guide/limeapp/images/aligning_satellite_map.png b/docs/public/guide/limeapp/images/aligning_satellite_map.png new file mode 100644 index 0000000..42b8b37 Binary files /dev/null and b/docs/public/guide/limeapp/images/aligning_satellite_map.png differ diff --git a/docs/public/guide/limeapp/images/aligning_signal_value.png b/docs/public/guide/limeapp/images/aligning_signal_value.png new file mode 100644 index 0000000..8c30743 Binary files /dev/null and b/docs/public/guide/limeapp/images/aligning_signal_value.png differ diff --git a/docs/public/guide/limeapp/images/aligning_tool.png b/docs/public/guide/limeapp/images/aligning_tool.png new file mode 100644 index 0000000..599108b Binary files /dev/null and b/docs/public/guide/limeapp/images/aligning_tool.png differ diff --git a/docs/public/guide/limeapp/images/alignment_back_button.png b/docs/public/guide/limeapp/images/alignment_back_button.png new file mode 100644 index 0000000..6fd6924 Binary files /dev/null and b/docs/public/guide/limeapp/images/alignment_back_button.png differ diff --git a/docs/public/guide/limeapp/images/alignment_color_scale.png b/docs/public/guide/limeapp/images/alignment_color_scale.png new file mode 100644 index 0000000..921246c Binary files /dev/null and b/docs/public/guide/limeapp/images/alignment_color_scale.png differ diff --git a/docs/public/guide/limeapp/images/alignment_detail.png b/docs/public/guide/limeapp/images/alignment_detail.png new file mode 100644 index 0000000..6fe2042 Binary files /dev/null and b/docs/public/guide/limeapp/images/alignment_detail.png differ diff --git a/docs/public/guide/limeapp/images/alignment_lost.png b/docs/public/guide/limeapp/images/alignment_lost.png new file mode 100644 index 0000000..48878d1 Binary files /dev/null and b/docs/public/guide/limeapp/images/alignment_lost.png differ diff --git a/docs/public/guide/limeapp/images/alignment_no_link.png b/docs/public/guide/limeapp/images/alignment_no_link.png new file mode 100644 index 0000000..42003b7 Binary files /dev/null and b/docs/public/guide/limeapp/images/alignment_no_link.png differ diff --git a/docs/public/guide/limeapp/images/alignment_nodes.png b/docs/public/guide/limeapp/images/alignment_nodes.png new file mode 100644 index 0000000..852f13a Binary files /dev/null and b/docs/public/guide/limeapp/images/alignment_nodes.png differ diff --git a/docs/public/guide/limeapp/images/alignment_radios.png b/docs/public/guide/limeapp/images/alignment_radios.png new file mode 100644 index 0000000..ed6976d Binary files /dev/null and b/docs/public/guide/limeapp/images/alignment_radios.png differ diff --git a/docs/public/guide/limeapp/images/diagnostics_broken_path.png b/docs/public/guide/limeapp/images/diagnostics_broken_path.png new file mode 100644 index 0000000..ea1d19b Binary files /dev/null and b/docs/public/guide/limeapp/images/diagnostics_broken_path.png differ diff --git a/docs/public/guide/limeapp/images/diagnostics_color_bars.png b/docs/public/guide/limeapp/images/diagnostics_color_bars.png new file mode 100644 index 0000000..a625e6f Binary files /dev/null and b/docs/public/guide/limeapp/images/diagnostics_color_bars.png differ diff --git a/docs/public/guide/limeapp/images/diagnostics_full_path.png b/docs/public/guide/limeapp/images/diagnostics_full_path.png new file mode 100644 index 0000000..8844fee Binary files /dev/null and b/docs/public/guide/limeapp/images/diagnostics_full_path.png differ diff --git a/docs/public/guide/limeapp/images/diagnostics_gateway.png b/docs/public/guide/limeapp/images/diagnostics_gateway.png new file mode 100644 index 0000000..247f320 Binary files /dev/null and b/docs/public/guide/limeapp/images/diagnostics_gateway.png differ diff --git a/docs/public/guide/limeapp/images/diagnostics_in_progress.png b/docs/public/guide/limeapp/images/diagnostics_in_progress.png new file mode 100644 index 0000000..7ee31dd Binary files /dev/null and b/docs/public/guide/limeapp/images/diagnostics_in_progress.png differ diff --git a/docs/public/guide/limeapp/images/diagnostics_options.png b/docs/public/guide/limeapp/images/diagnostics_options.png new file mode 100644 index 0000000..7abaf35 Binary files /dev/null and b/docs/public/guide/limeapp/images/diagnostics_options.png differ diff --git a/docs/public/guide/limeapp/images/firmware_from_file1.png b/docs/public/guide/limeapp/images/firmware_from_file1.png new file mode 100644 index 0000000..85e9924 Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_from_file1.png differ diff --git a/docs/public/guide/limeapp/images/firmware_from_file2.png b/docs/public/guide/limeapp/images/firmware_from_file2.png new file mode 100644 index 0000000..636bc49 Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_from_file2.png differ diff --git a/docs/public/guide/limeapp/images/firmware_notification.png b/docs/public/guide/limeapp/images/firmware_notification.png new file mode 100644 index 0000000..7694fd6 Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_notification.png differ diff --git a/docs/public/guide/limeapp/images/firmware_options.png b/docs/public/guide/limeapp/images/firmware_options.png new file mode 100644 index 0000000..92dd4b0 Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_options.png differ diff --git a/docs/public/guide/limeapp/images/firmware_step1.png b/docs/public/guide/limeapp/images/firmware_step1.png new file mode 100644 index 0000000..8b2f528 Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_step1.png differ diff --git a/docs/public/guide/limeapp/images/firmware_step2.png b/docs/public/guide/limeapp/images/firmware_step2.png new file mode 100644 index 0000000..85060cd Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_step2.png differ diff --git a/docs/public/guide/limeapp/images/firmware_step3.png b/docs/public/guide/limeapp/images/firmware_step3.png new file mode 100644 index 0000000..7cd758f Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_step3.png differ diff --git a/docs/public/guide/limeapp/images/firmware_step4.png b/docs/public/guide/limeapp/images/firmware_step4.png new file mode 100644 index 0000000..d8e8825 Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_step4.png differ diff --git a/docs/public/guide/limeapp/images/firmware_step5.png b/docs/public/guide/limeapp/images/firmware_step5.png new file mode 100644 index 0000000..f951dfb Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_step5.png differ diff --git a/docs/public/guide/limeapp/images/firmware_step6.png b/docs/public/guide/limeapp/images/firmware_step6.png new file mode 100644 index 0000000..85b407e Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_step6.png differ diff --git a/docs/public/guide/limeapp/images/firmware_step7.png b/docs/public/guide/limeapp/images/firmware_step7.png new file mode 100644 index 0000000..5fedd18 Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_step7.png differ diff --git a/docs/public/guide/limeapp/images/firmware_step8.png b/docs/public/guide/limeapp/images/firmware_step8.png new file mode 100644 index 0000000..c87504a Binary files /dev/null and b/docs/public/guide/limeapp/images/firmware_step8.png differ diff --git a/docs/public/guide/limeapp/images/map_layers.png b/docs/public/guide/limeapp/images/map_layers.png new file mode 100644 index 0000000..b2a5c94 Binary files /dev/null and b/docs/public/guide/limeapp/images/map_layers.png differ diff --git a/docs/public/guide/limeapp/images/map_locate_node.png b/docs/public/guide/limeapp/images/map_locate_node.png new file mode 100644 index 0000000..ddba797 Binary files /dev/null and b/docs/public/guide/limeapp/images/map_locate_node.png differ diff --git a/docs/public/guide/limeapp/images/map_node_tooltip.png b/docs/public/guide/limeapp/images/map_node_tooltip.png new file mode 100644 index 0000000..565ea40 Binary files /dev/null and b/docs/public/guide/limeapp/images/map_node_tooltip.png differ diff --git a/docs/public/guide/limeapp/images/map_overview.png b/docs/public/guide/limeapp/images/map_overview.png new file mode 100644 index 0000000..b1bbae1 Binary files /dev/null and b/docs/public/guide/limeapp/images/map_overview.png differ diff --git a/docs/public/guide/limeapp/images/map_toggle_community.png b/docs/public/guide/limeapp/images/map_toggle_community.png new file mode 100644 index 0000000..0e531cc Binary files /dev/null and b/docs/public/guide/limeapp/images/map_toggle_community.png differ diff --git a/docs/public/guide/limeapp/images/menu-1-4.png b/docs/public/guide/limeapp/images/menu-1-4.png new file mode 100644 index 0000000..34058ff Binary files /dev/null and b/docs/public/guide/limeapp/images/menu-1-4.png differ diff --git a/docs/public/guide/limeapp/images/minodoinfo_en-el-navegador_2.png b/docs/public/guide/limeapp/images/minodoinfo_en-el-navegador_2.png new file mode 100644 index 0000000..510cc3e Binary files /dev/null and b/docs/public/guide/limeapp/images/minodoinfo_en-el-navegador_2.png differ diff --git a/docs/public/guide/limeapp/images/mockup.png b/docs/public/guide/limeapp/images/mockup.png new file mode 100644 index 0000000..edbb52f Binary files /dev/null and b/docs/public/guide/limeapp/images/mockup.png differ diff --git a/docs/public/guide/limeapp/images/network_config.png b/docs/public/guide/limeapp/images/network_config.png new file mode 100644 index 0000000..9d7813a Binary files /dev/null and b/docs/public/guide/limeapp/images/network_config.png differ diff --git a/docs/public/guide/limeapp/images/node_config.png b/docs/public/guide/limeapp/images/node_config.png new file mode 100644 index 0000000..8c7bba3 Binary files /dev/null and b/docs/public/guide/limeapp/images/node_config.png differ diff --git a/docs/public/guide/limeapp/images/notes_screen.png b/docs/public/guide/limeapp/images/notes_screen.png new file mode 100644 index 0000000..fbc3610 Binary files /dev/null and b/docs/public/guide/limeapp/images/notes_screen.png differ diff --git a/docs/public/guide/limeapp/images/remote_support.jpg b/docs/public/guide/limeapp/images/remote_support.jpg new file mode 100644 index 0000000..a9fce75 Binary files /dev/null and b/docs/public/guide/limeapp/images/remote_support.jpg differ diff --git a/docs/public/guide/limeapp/images/visit_node.png b/docs/public/guide/limeapp/images/visit_node.png new file mode 100644 index 0000000..940f0b4 Binary files /dev/null and b/docs/public/guide/limeapp/images/visit_node.png differ