Connected and tapping! With the Raspberry Pi Zero W 2, a Waveshare e-paper touch hat and a decent amount of coding, we have a device that can read the announce stream for NomadNet.
#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.
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?
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
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
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 ?
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
@fishingdev @richardwonka @fidepus The idea behind #reticulum is ideal for emergency networking because it has redundancy & your address is kept & works irrespective of device or comms protocol: you are reachable on a unique address like a phone number. Very precious indeed in an emergency. Seamless communication. Also you can use multiple #radio settings & protocols at the same end user device. It also confirms delivery of #lora messages extremely well. #lxmf #meshchat #Notfallkommunikation
To receive by #radio #reticulum #rnode #announces on #lora radio one needs to have the same 4 radio parameters as the announce: #frequency #bandwidth #spreadingfactor SF #codingrate CR
-> #meshchat permits any number of #rnode interfaces !
To hear the most announces, does it make sense & is it possible to set up several e.g. 5 #lora #radios with same frequency: 869.525 MHz
bandwidth: 250 kHz but
each with different SF & CR? Would one be able to receive more announces that way? Would it work?
#lora #radio #reticulum #car #node #rnode
https://www.loramesh.org/subpages/carrnode/carrnode.html
#carrnode #meshchat #toyotaproacecity #geekwormx1206
A #rnode build for #reticulum using a #raspberrypi5 and #geekwormx1206 #ups for a #carnode or #solarnode
https://www.loramesh.org/subpages/upsrnode/upsrnode.html
Running #meshchat , four #liion #21700 5000 mAh batteries seem to run the #rak4631 and Pi for at least 24 hours. The device can be re-charged using #usbc or 9 to 18 V DC at up to 3 A via a jack or other connector. The rnode shuts down cleanly when batteries run out & re-starts when power is back, whereupon the batteries charge at the same time in #passthroughcharging
@mrkaran Great insights & a pleasure to read. I have used #nixos as my main machine for a few years & its main advantage is that it won't let me mess it up because I do not install anything other than via the configuration.nix. Your post has given me a view on how to use it properly.
My big question: how can one #package something to get it into the nixOS https://search.nixos.org/packages
? I am happy to do the work but no micro step by step guide seems available. I am thinking of #reticulum #meshchat
#lora #radio #reticulum using #meshchat
If one #rnode (rnodeA) run by device A, e.g #RaspberryPiZero2W , has is its own #wifi #hotpot (as shown here https://loramesh.org/subpages/pi_install.html#pi_hotspot) (with SSID & password),
& another rnode (rnodeB) run by another device B (any device with wifi) joins the hotspot (SSID & pwd),
& rnodeA & rnodeB both have the 'default interface' activated in their reticulum meshchat GUI,
the wifi hotspot *alone* (without radio) will enable sending messages via reticulum between A and B !
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst