RNS_Over_Meshtastic

[sharp wind]

https://github.com/landandair/RNS_Over_Meshtastic
Port Reticulum network stack over meshtastic networks to augment the features reticulum provides onto a meshtastic network that can take it

Made an interface for Reticulum which allows you to use Reticulum utilities like secure file transfers, secure code execution, an early internet esc Page system, and a couple client applications be able to utilize an existing high speed meshtastic network to push data

[tall lichen]

This is really cool

[sharp wind]

If you have any questions, hit me up

[tall lichen]

Ive never used reticulum or meshchat. Where does the file go?

[sharp wind]

I’ve wanted to make a distributed file server for a while, and this is one step to get there

[sharp wind]

.reticulum/Interfaces

Usually in your home directory

The config file is in the .reticulum directory

Also meshchat is weird about python libraries and won’t necessarily use the correct python you have installed, if it gives a library error, simply start reticulum with rnsd in the terminal

Also the docs for reticulum give good info about how to set up a custom interface and how to run the actual service or set it to auto-run as a service in the background

[tall lichen]

Wait so I need to install reticulum?

[sharp wind]

Yeah, just follow the docs for that

[tall lichen]

Is there any way this can also function on mobile?

[sharp wind]

You’ll also need two computers to test it easily so they can talk

[tall lichen]

for the lxmf thing?

[sharp wind]

On android yeah

They don’t have an iPhone one because they need it to function as a constant service and iPhone doesn’t allow that

[sharp wind]

The issue is that reticulum shares the actual interfaces with every application using reticulum, so launching 2 instances won’t let you connect to two radios at once

You’ll just talk over the shared interface proving nothing but your loop back repeater is working as intended

[slow current]

does this mean that this can be run on a raspi with radio hat, even though reticulum currently doesnt support that? because meshtastic is handling the interface side for it?

[sharp wind]

Yeah

Though I do t have the Python interface for that, it’s a simple code change

Just add a connection option to open interface section

And add an option for it in the ifconfig

I think it uses the http interface right?

The code as it is supports serial and BLE connections just because that’s what I use

Do keep in mind that this is a slower option all things considered since there’s additional network overhead

[slow current]

yeah

[slow current]

serial and bt are only either/or for meshtasticd<>radio so anything else with python is forced to use tcp to connect to the api via meshtasticd

[slow current]

right. but it should allow better data transfer than just meshtastic right? or as its using meshtastic as its interface, is this irrelevant and its just another way for reticulum to propagate but doesnt actually have potential benefits for meshtastic per se?

either way is still great, just want to make sure i understand what it can and cant do in tandem

[sharp wind]

Oh yeah, it’s better and more reliable than just Meshtastic for data transfer

[sharp wind]

Yeah, exactly, you’d just need to add that option in the code for it to work