In a #lora #rns #reticulum #mesh using #lora with long transmission blocks due to a large #spreadingfactor of 12 #sf12 , does one have to change some default settings to make it work better than the defaults? Like time between trying alternative routes to a destination or time to wait for or send a delivery confirmation (to wait for #ismband channel to be free of those long transmissions so that a send operation is possible) ?

Does a #rns #reticulum #mesh continue trying all alternative routes so long as a delivery is not confirmed, even for #radio #rnodes operating under #lora ( #ismband #869decimal525mhz ) ?
#reticulumnetwork

Is there a #simulation of a #lora #reticulum #radio #mesh used with different numbers of #rnode #radio #nodes #rnodes for given #spreadingfactor ( #sf ) & given payload size? Am interested to know what happens to the routing, & likelyhood of #deliveryconfirmation for small LoRa packets (max 2 blocks), for longest transmission times i.e. spreading factor 12 #SF12 . Would like to know if my impressions, that SF 12 is very tricky under #RNS LoRa as compared with #SF10, have a clear explanation.

Mit #Meshtastic #meshcore und #Reticulum verhält es sich wie damals mit #VHS #betamax und #video2000 . Letzteres wurde uns von Industrie Konsortien vorgegeben. Ich finde es traurig, dass bei freien Projekten Leute nicht mehr zusammen finden und an einem Strang ziehen können. Hier wo ich wohne, gibt es von diesen drei Mesh Messengern keinerlei Nutzung. Und die Leute hier sind überfordert, dass es von allem zu viele Varianten gibt. Betrifft auch das Fediverse und Linux. Daher wird es nicht kommen.

Setting a decent #deliverylimit in #reticulum #meshchat for an #rnode interface that matches a given radio parameter set (or sets) (#spreadingfactor #sf etc.) helps avoid the sad scenario that an rnode uses up its 10% maximum legally permitted #dutycycle allowance for that #radio #ismband when trying to send or resend payloads that stand no chance of 100% delivery in a reasonable time frame. https://loramesh.org/SF

With a #RaspberryPiZero2W & #usbhub https://www.waveshare.com/wiki/USB_HUB_HAT_(B) possible to use 4 #lora #radio #rnodes at same #reticulum #meshchat interface. Can use 4 different sets of radio parameters at one #LoRa #radio interface. Can use 1 radio with low #spreadingfactor #sf for short transmissions at high data rate for large payloads like images or accessing #nomadnet #pages and 1 with larger SF for longer range. No need to choose between #meshtasic presets https://meshtastic.org/docs/overview/radio-settings/ ! just use them all ! Magic

I'm honestly kinda tired of people constantly, incessantly only comparing Reticulum to primarily LoRa messaging apps like Meshtastic and Meshcore. :blobcatthink:

For one thing, it’s designed to work over anything and everything (with a focus on nothing in particular), and for another it was never intended to just be a messaging app.

:blobcatbusiness: It's a protocol, similar to B.A.T.M.A.N. with encryption as a hard requirement and a more complete package, designed for scalable and efficient non-homogenous networks.

Practically that means it maxes out at an IP-like 255 hops (not 7, not 64), and you can add multiple layers of backhauls even connecting over the internet without bogging down an entire network when somebody tries to send a 2MB image, which is kinda nice.

If you want to learn more about how it works, do check out my explainer: https://linuxinabit.codeberg.page/blog/reticulum/

And yes, multicast is coming eventually (the conceptual bit is largely figured out now! :blobcattoot: ), and it'll work without using expensive source routing or unaffordable flood routing.

#Reticulum #Meshchat #MeshCore

It seems to be possible to set a message size delivery limit as defined by the parameter lxmf_delivery_transfer_limit_in_bytes
in https://github.com/liamcottle/reticulum-meshchat/blob/b8d388fa56d4528b1e7311e4210edcc0c15ee959/meshchat.py#L3261
to let each #rnode have its own limit suiting its own #spreadingfactor #sf
#reticulum #meshchat

@fasnix

Zurzeit gibt es, nach meinem heutigen Kenntnisstand, drei wichtige #Meshnetzwerke. Zunächst das allseits bekannte #Meshtastic, dann #Reticulum und auch #MeshCore.

Während sich Reticulum hauptsächlich als #Cryptography basierten Netzwerk-Stack sieht, das auch (!) LoRa kann, so tritt MeshCore eher in die Fußstapfen von Meshtastic, vermeidet dabei aber die Konzeptfehler, die gleich zu Anfang bei Meshtastic entstanden sind. Damals konnte ja noch kein Entwickler ahnen, welchen Zulauf und welche Größe MT erreichen wird.

Bei MC wird deshalb von vornherein auf viele Dinge verzichtet, die zwar "nett" sind, aber das Netz belasten und nicht wirklich nötig sind.

Dazu zählt, dass nicht jeder Node auch gleich ein "Repeater" ist, ständig Telemetriedaten über das Mesh geschickt werden und vieles mehr.

Es werden also wesentlich (!) weniger Daten durch das Netz "gequetscht". MeshCore ist jetzt seit rund vier Monaten online, aber ein absoluter "Senkrechtstarter". In London sind bereits mehr als 100 Nodes online und insgesamt schon mehr als 1.100 Nodes.

Aktuelle Infos und die Möglichkeit zum Austausch zu allen dreien findest du hier:

https://matrix.to/#/#mesh-netzwerke-de:matrix.org

#Notfallkommunikatio #Mesh #WAN #LoRa

@bjoern

Spain power cuts - fortunately we are somewhat prepared with solar electricity, cash supplies, 15000 litres of water storage, fuel in car & about a months worth of dehydrated meals 😆. In case of a zombie apocalypse 🧟‍♂️or natural disaster we also have walkie talkies, LoRa radios & I have been developing off-grid networks (experimenting with #Meshtastic, #Meshcore & #Reticulum) 🤣.

Bit of a wake up call though - prepare for these events no matter how far fetched they seem. They can and do happen.

Can one set the #lxmf #reticulum delivery limit in #reticulum #meshchat on a per #interface basis i.e. per connected #rnode interface? https://github.com/markqvist/LXMF/blob/c426c93cc5d63a3dae18ad2264b1299a7ad9e46c/LXMF/LXMRouter.py#L38
#deliverylimit #DELIVERY_LIMIT
This might help stop #lora #radio channel blocking in case one #rnode of a set of #rnodes at one end-point device use a high #spreadingfactor #sf #lorachannelblocking

In a world where control of #communication networks is increasingly centralized, #DIYnetworks offer an independent alternative. This presentation shows how to build up your own autonomous #meshNetworks with low-cost hardware components and open source tools such as #Reticulum and #MeshChat. We will present practical steps for the construction, configuration and integration of sensors, communication and computing power. We are also discussing how such #networks can be used in #humanitarianCrises, such as the organisation of aid measures through solidarity initiatives.

https://media.ccc.de/v/eh22-97-eggceptional-meshnetworking-#t=950

This workshop offers a detailed journey through the world of do-it-yourself radio networks and #autonomousCommunication structures. Using an exemplary system structure, we show how to realize cost-effective, flexible mesh networks with #LoRa #RNode, Reticulum and MeshChat. In doing so, we not only dedicate ourselves to the technical requirements – such as the optimal hardware selection, antenna adaptation and network planning (keyword “Network Planning 101”) – but also consider how these technologies can be used for #humanitarian purposes, for example at #CADUS.

A friend tested this for 2 VMs with #ubuntu & simply set a #UDP interface in the settings file on #meshchat on each #VM & it works. The spreading factor (SF) 10 #rnode end point meshchat GUI sees the messages arriving at the lora SF 5 rnode via UDP, & vice versa. So the #proxmox setup has both lora SF settings for messaging images & data. The SF 5 rnode is ace for messages of about 60 KB & the SF 10 for longer range text. Both arrive at each VM. https://reticulum.network/manual/interfaces.html
#reticulum is sensational.

Any recommendations for a 64 bit machine for #proxmox to run 8 dedicated #virtualmachines #vm each running minimal #ubuntu for a single #reticulum #meshchat application with 8 single usb-c connections to 8 #lora radio #rnode #nodes like a RAK4613 https://store.rakwireless.com/products/wisblock-meshtastic-starter-kit?variant=4388403462163
Here is what their site says: https://www.proxmox.com/en/products/proxmox-virtual-environment/requirements
Requirements for each VM is not much more than 1 Gb and storage requirements trivial (less than 30 Gb per machine). Any recommendations most welcome.

If I have 10 virtual machines (m1..10) in #proxmox each running #rnode hardware (r1..10), via 10 #meshchat guis (g1..10), over one of 10 respective usb-c connections,
& all 10 virtual machines are on the same local area network #LAN via 1 network card/interface of the 1 computer running proxmox, can I link the virtual machines using #reticulum #rns #autointerface
https://reticulum.network/manual/interfaces.html#auto-interface
& will thereby each #rnode #meshchat #gui receive all #lora mediated data from each other #rnode over #lan ?

@adingbatponder
> Which is the lowest cost, #reticulum compatible, #rnode hardware for #lora radio?

Try the SeeedStudio XIAO WIO combo, 10 euros for the caseless version. I got two on aliexpres for 21Eur and free shipping (took a week to arrive)

Has a ESP32S3 and SX1262 lora module on a board sandwich smaller than your thumb.

https://www.seeedstudio.com/Wio-SX1262-with-XIAO-ESP32S3-p-5982.html

Which is the lowest cost, #reticulum compatible, #rnode hardware for #lora radio?

Host a Webcam on a Reticulum Nomadnet Pageserver

https://mander.xyz/post/28638863

Web #pages , including #webcam #images , can be served by a #lora #radio #rnode using #reticulum #nomadnet over a #lora #radio #mesh , and accessed via #meshchat over the lora reticulum mesh using a mobile rnode :
https://www.youtube.com/watch?v=kSHA_HRBOpI
See the link below for a demonstration of the result of the pages set up in the above Simon Phillips video demo:
https://www.loramesh.org/subpages/webcam/webcam.html