eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

211
active users

#meshchat

1 post1 participant0 posts today
adingbatponder<p><a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/LoRa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LoRa</span></a> <br>It seems that it is important for all <a href="https://fosstodon.org/tags/rnodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnodes</span></a> in a given <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> based <a href="https://fosstodon.org/tags/loramesh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loramesh</span></a> <a href="https://fosstodon.org/tags/mesh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mesh</span></a> to update to the latest <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> version to ensure all rnodes can function as intended. <br><a href="https://newreleases.io/project/github/liamcottle/reticulum-meshchat/release/v2.1.0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">newreleases.io/project/github/</span><span class="invisible">liamcottle/reticulum-meshchat/release/v2.1.0</span></a></p>
adingbatponder<p>Has anyone managed to make a message <a href="https://fosstodon.org/tags/bridge" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bridge</span></a> between different <a href="https://fosstodon.org/tags/spreadingfactor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spreadingfactor</span></a> <a href="https://fosstodon.org/tags/sf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sf</span></a> <a href="https://fosstodon.org/tags/lora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lora</span></a> <a href="https://fosstodon.org/tags/rnodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnodes</span></a> using <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/rns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rns</span></a> : either using the same single computer and two different <a href="https://fosstodon.org/tags/rnode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnode</span></a> radios (on the same frequency), or using two rnode radios on 2 different computers connected by <a href="https://fosstodon.org/tags/wifi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wifi</span></a>? I seem to get this not working "out of the box" because of <a href="https://fosstodon.org/tags/collisions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>collisions</span></a> of lora packets of the two rnodes. Has anyone managed to bridge lora rnodes by putting in a transmission delay in <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> e.g. <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> ?</p>
Richard Wonka<p>Peer-to-peer chat via Bluetooth is the hype with (apparently poorly designed) <a href="https://mas.to/tags/bitchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bitchat</span></a></p><p>Wouldn’t <a href="https://mas.to/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://mas.to/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> (<a href="https://github.com/liamcottle/reticulum-meshchat" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/liamcottle/reticulu</span><span class="invisible">m-meshchat</span></a>) do that, but<br>- mature<br>- well-encrypted <br>- (massively) scalable<br>- without the limitation to Bluetooth</p><p>?</p><p><a href="https://mas.to/tags/askfedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>askfedi</span></a></p>
adingbatponder<p>Getting reports of <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> version 1.22 not being able to message nor ping <a href="https://fosstodon.org/tags/version" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>version</span></a> 1.21 . Anyone else get this? <br><a href="https://fosstodon.org/tags/reticulummeshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulummeshchat</span></a> <a href="https://fosstodon.org/tags/meshchat1dot21" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat1dot21</span></a> <a href="https://fosstodon.org/tags/meshchat1dot22" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat1dot22</span></a><br><a href="https://github.com/liamcottle/reticulum-meshchat" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/liamcottle/reticulu</span><span class="invisible">m-meshchat</span></a></p>
Denton Mesh<p>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.</p><p><a href="https://denton.social/tags/Reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Reticulum</span></a> <a href="https://denton.social/tags/MeshChat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MeshChat</span></a></p>
adingbatponder<p>A first &amp; second <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/rnode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnode</span></a> each on a <a href="https://fosstodon.org/tags/raspberrypizero" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>raspberrypizero</span></a> each providing their own <a href="https://fosstodon.org/tags/wifi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wifi</span></a> <a href="https://fosstodon.org/tags/hotspot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hotspot</span></a> &amp; running <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> on http://&lt;IP_1&gt; :8000 &amp; http://&lt;IP_2&gt;:8000 (different hotspot IP addresses)<br>using these instructions <a href="https://medium.com/@thakuravnish2313/how-to-set-up-a-persistent-raspberry-pi-hotspot-with-dhcp-f2519c3d5898" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">medium.com/@thakuravnish2313/h</span><span class="invisible">ow-to-set-up-a-persistent-raspberry-pi-hotspot-with-dhcp-f2519c3d5898</span></a> &amp; <a href="https://loramesh.org/subpages/pi_install.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">loramesh.org/subpages/pi_insta</span><span class="invisible">ll.html</span></a> &amp; two wifi adapters <a href="https://amzn.eu/d/6SzEJww" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">amzn.eu/d/6SzEJww</span><span class="invisible"></span></a><br>in a <a href="https://fosstodon.org/tags/nixos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nixos</span></a> <a href="https://fosstodon.org/tags/thinkpad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>thinkpad</span></a> 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.</p>
adingbatponder<p>How can <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> on an rnode X suddenly lose the ability to send/receive messages from one particular <a href="https://fosstodon.org/tags/rnode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnode</span></a> A, when all other rnodes B &amp; C continue to work fine and communicate with X? When restarting the rnode X the problem goes away....<br>Never seen this before. Normally either every message route between A &amp; X and C &amp; X and B &amp; X works or nothing works.<br>Is there a routing issue? (Announces were made from all radios and plenty of time taken).</p>
adingbatponder<p>If a <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> instance with a <a href="https://fosstodon.org/tags/lxmf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lxmf</span></a> address on one computing device has 4 identical <a href="https://fosstodon.org/tags/lora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lora</span></a> <a href="https://fosstodon.org/tags/rnodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnodes</span></a> <a href="https://fosstodon.org/tags/rnode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnode</span></a> interfaces, each with same settings of frequency <a href="https://fosstodon.org/tags/spreadingfactor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spreadingfactor</span></a> <a href="https://fosstodon.org/tags/sf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sf</span></a>, each rnode having a <a href="https://fosstodon.org/tags/directional" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>directional</span></a> <a href="https://fosstodon.org/tags/yagi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>yagi</span></a> <a href="https://fosstodon.org/tags/antenna" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>antenna</span></a> in close vicinity, will transmission to a sender of a <a href="https://fosstodon.org/tags/deliveryconfirmation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deliveryconfirmation</span></a> (<a href="https://fosstodon.org/tags/downlink" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>downlink</span></a>) from 1 antenna to the sender's direction, be messed up due to local <a href="https://fosstodon.org/tags/collision" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>collision</span></a> at rnode 1 of different attempted <a href="https://fosstodon.org/tags/acknowledgement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>acknowledgement</span></a> signals of the other 3 near rnodes?</p>
adingbatponder<p>Setting a decent <a href="https://fosstodon.org/tags/deliverylimit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deliverylimit</span></a> in <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> for an <a href="https://fosstodon.org/tags/rnode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnode</span></a> interface that matches a given radio parameter set (or sets) (<a href="https://fosstodon.org/tags/spreadingfactor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spreadingfactor</span></a> <a href="https://fosstodon.org/tags/sf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sf</span></a> etc.) helps avoid the sad scenario that an rnode uses up its 10% maximum legally permitted <a href="https://fosstodon.org/tags/dutycycle" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dutycycle</span></a> allowance for that <a href="https://fosstodon.org/tags/radio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>radio</span></a> <a href="https://fosstodon.org/tags/ismband" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ismband</span></a> when trying to send or resend payloads that stand no chance of 100% delivery in a reasonable time frame. <a href="https://loramesh.org/SF" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">loramesh.org/SF</span><span class="invisible"></span></a></p>
adingbatponder<p>With a <a href="https://fosstodon.org/tags/RaspberryPiZero2W" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RaspberryPiZero2W</span></a> &amp; <a href="https://fosstodon.org/tags/usbhub" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>usbhub</span></a> <a href="https://www.waveshare.com/wiki/USB_HUB_HAT_(B)" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">waveshare.com/wiki/USB_HUB_HAT</span><span class="invisible">_(B)</span></a> possible to use 4 <a href="https://fosstodon.org/tags/lora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lora</span></a> <a href="https://fosstodon.org/tags/radio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>radio</span></a> <a href="https://fosstodon.org/tags/rnodes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnodes</span></a> at same <a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a> interface. Can use 4 different sets of radio parameters at one <a href="https://fosstodon.org/tags/LoRa" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LoRa</span></a> <a href="https://fosstodon.org/tags/radio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>radio</span></a> interface. Can use 1 radio with low <a href="https://fosstodon.org/tags/spreadingfactor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spreadingfactor</span></a> <a href="https://fosstodon.org/tags/sf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sf</span></a> for short transmissions at high data rate for large payloads like images or accessing <a href="https://fosstodon.org/tags/nomadnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nomadnet</span></a> <a href="https://fosstodon.org/tags/pages" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pages</span></a> and 1 with larger SF for longer range. No need to choose between <a href="https://fosstodon.org/tags/meshtasic" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshtasic</span></a> presets <a href="https://meshtastic.org/docs/overview/radio-settings/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">meshtastic.org/docs/overview/r</span><span class="invisible">adio-settings/</span></a> ! just use them all ! Magic</p>
Linux in a Bit<p>I'm honestly kinda tired of people constantly, incessantly <em>only</em> comparing Reticulum to generally LoRa-only messaging apps like Meshtastic and Meshcore. :blobcatthink: </p><p>For one thing, it’s not LoRa-only, nor is it intended to just be a messaging app.</p><p>:blobcatbusiness: It's a protocol, similar to <a href="https://en.wikipedia.org/wiki/B.A.T.M.A.N." rel="nofollow noopener" target="_blank">B.A.T.M.A.N.</a> with encryption as a hard requirement and a more complete package, designed for scalable and efficient non-homogenous networks.</p><p>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 <em>entire</em> network when somebody tries to send a 2MB image, which is kinda nice.</p><p>If you want to learn more about how it works, do check out my explainer: <a href="https://linuxinabit.codeberg.page/blog/reticulum/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">linuxinabit.codeberg.page/blog</span><span class="invisible">/reticulum/</span></a></p><p>And yes, multicast <em>is</em> coming eventually (the conceptual bit is largely figured out now! :blobcattoot: ), and it'll work without using expensive source routing or unaffordable flood routing.</p><p><a href="https://infosec.exchange/tags/Reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Reticulum</span></a> <a href="https://infosec.exchange/tags/Meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Meshchat</span></a> <a href="https://infosec.exchange/tags/MeshCore" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MeshCore</span></a></p>
adingbatponder<p>It seems to be possible to set a message size delivery limit as defined by the parameter lxmf_delivery_transfer_limit_in_bytes<br>in <a href="https://github.com/liamcottle/reticulum-meshchat/blob/b8d388fa56d4528b1e7311e4210edcc0c15ee959/meshchat.py#L3261" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/liamcottle/reticulu</span><span class="invisible">m-meshchat/blob/b8d388fa56d4528b1e7311e4210edcc0c15ee959/meshchat.py#L3261</span></a><br>to let each <a href="https://fosstodon.org/tags/rnode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rnode</span></a> have its own limit suiting its own <a href="https://fosstodon.org/tags/spreadingfactor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spreadingfactor</span></a> <a href="https://fosstodon.org/tags/sf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sf</span></a><br><a href="https://fosstodon.org/tags/reticulum" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reticulum</span></a> <a href="https://fosstodon.org/tags/meshchat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meshchat</span></a></p>
Continued thread

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. reticulum.network/manual/inter
#reticulum is sensational.

reticulum.networkConfiguring Interfaces - Reticulum Network Stack 0.9.4 beta documentation

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 store.rakwireless.com/products
Here is what their site says: proxmox.com/en/products/proxmo
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.

store.rakwireless.comWisBlock Meshtastic Starter Kit | The Basic RAK4631 Meshtastic Kit for LoRa

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
reticulum.network/manual/inter
& will thereby each #rnode #meshchat #gui receive all #lora mediated data from each other #rnode over #lan ?

reticulum.networkConfiguring Interfaces - Reticulum Network Stack 0.9.4 beta documentation
Replied in thread

@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?