Heltec RNodes updated as is my Sideband. Unfortunately still can’t make calls in Sideband (it’s grayed out). Also, trying to find RNode Transport Node software for the Lilygo T-Echo and I see none. Me sad 🥹 #RNode #Reticulum #Sideband #TEcho

@sacha @screwlisp @dougmerritt @zagebo @vavakado I'm trying to figure out how to maintain a wireless terminal connection with my home computer up to 10km away (further's edge of town)

Via #Reticulum over #LoRa (#rnode) or another #MeshNetwork. #PacketRadio, #MANET, #BATMAN, #SDR, etc

I'm not sure where this is going if anywhere ¯\_(ツ)_/¯
—
https://reticulum.network
https://unsigned.io/rnode/
https://en.wikipedia.org/wiki/Wireless_ad_hoc_network
https://en.wikipedia.org/wiki/B.A.T.M.A.N.

Today, @itsyndikat's #Reticulum #RNode got upgraded to a #heltecv4.

#reticulum #rnode #firmware now has support for #heltecv4 which has high #power #28dbm version !! https://github.com/markqvist/RNode_Firmware/releases/tag/1.84 #rnodes #lora https://heltec.org/project/wifi-lora-32-v4/ #rns

@ff7

Klar sollte das TCP unabhängig sein.

Aber zumindest ist eine weit entfernte Verbindung möglich.

An den Anfängen von #meshtastic warteten ja auch viele Monate bis sich mal einer meldete.

Aber in den Niederlanden gibt es ein 2W #Reticulum #rnode

Problem dabei ist, dass dieser nur von der #Amateurfunk Abteilung angefunkt werden darf.

@leinelab

Has anyone managed to make a message #bridge between different #spreadingfactor #sf #lora #rnodes using #reticulum #rns : either using the same single computer and two different #rnode radios (on the same frequency), or using two rnode radios on 2 different computers connected by #wifi? I seem to get this not working "out of the box" because of #collisions of lora packets of the two rnodes. Has anyone managed to bridge lora rnodes by putting in a transmission delay in #reticulum e.g. #meshchat ?

A first & second #reticulum #rnode each on a #raspberrypizero each providing their own #wifi #hotspot & running #meshchat on http://<IP_1> :8000 & http://<IP_2>:8000 (different hotspot IP addresses)
using these instructions https://medium.com/@thakuravnish2313/how-to-set-up-a-persistent-raspberry-pi-hotspot-with-dhcp-f2519c3d5898 & https://loramesh.org/subpages/pi_install.html & two wifi adapters https://amzn.eu/d/6SzEJww
in a #nixos #thinkpad allows both rnodes' meshchat GUI interfaces to be used at the same time on one laptop. Useful for monitoring multiple rnode radios outside or in the attic.

Can report that, as google search also reports, the TP-Link Archer T3U Plus AC1300 USB Stick https://amzn.eu/d/aLwsXvF works plug & play on #Ubuntu 22.04 LTS & #NixOS 25.05 (amazing) so can have multiple #wifi interfaces simultaneously. Intend to test multiple ones & make gadget (KVM + pi zero + several such dongles) to de-dongle this & just call up the pi zero desktop by KVM to view the various pages :8000 served by the plural #rnode raspberry pi radio hotspots to which each dongle is connects.

How can #reticulum #meshchat on an rnode X suddenly lose the ability to send/receive messages from one particular #rnode A, when all other rnodes B & C continue to work fine and communicate with X? When restarting the rnode X the problem goes away....
Never seen this before. Normally either every message route between A & X and C & X and B & X works or nothing works.
Is there a routing issue? (Announces were made from all radios and plenty of time taken).

If a #reticulum #meshchat instance with a #lxmf address on one computing device has 4 identical #lora #rnodes #rnode interfaces, each with same settings of frequency #spreadingfactor #sf, each rnode having a #directional #yagi #antenna in close vicinity, will transmission to a sender of a #deliveryconfirmation (#downlink) from 1 antenna to the sender's direction, be messed up due to local #collision at rnode 1 of different attempted #acknowledgement signals of the other 3 near rnodes?

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.

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

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

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

Some interesting info about the effect of #spreadingfactor (#SF) in #lora #radio #mesh is in papers about SF https://pmc.ncbi.nlm.nih.gov/articles/PMC8512894 SF12 in #lora & lora https://pmc.ncbi.nlm.nih.gov/articles/PMC5038744

Can one influence the effectiveness of using multiple #rnode interfaces , in one single end-point location, with different SF by setting the #LXMF delivery limit #DELIVERY_LIMIT down https://github.com/markqvist/LXMF/blob/c426c93cc5d63a3dae18ad2264b1299a7ad9e46c/LXMF/LXMRouter.py#L38 from the default 1 MB for those #rnodes, of a set, with higher SF values?

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