Nope. At least, not yet. I am playing with #Meshtastic and to a lesser degree, raw #LoRa packets. I also wrote scripts to set up an 802.11 mesh network using whatever random hardware you have lying around. https://gitlab.com/adam949/guerrilla-radio Right now it is focused on Debian-based distros and tested with various models of Raspberry Pi boards. I haven't been actively working on guerrilla-radio lately on account of other projects taking priority.
Sweet. I'll take a look. I'm working on my nostr over packet HF(and vhf) radio client/server, and also using Reticulum. Have been thinking about switching my dev path from a single use KISS TNC packet directly, to using RN instead.(if I can figure out) That way you could use kiss, lora, tcp, or any other protocol in RN and it would be fully decentralized and robust and have forwarding, etc..
I admit, the idea of hopping across radio frequencies is pretty attractive!
Very much so! Currently I have test the following at my house using the sideband chat app on reticulum. Field Hf radio to my base hf radio from about 70 miles away. Base station sends the packet/message via lora meshtastic device(flashed as rnode) to another rnode in a different room. That rnode is also connected to wifi, and send the message to a device that isn't connected to the internet but on the same wifi. It's insane.
802.11 is like adhoc mode but with optional forwarding if I am correct?
I think that's right. I was able to get the mesh working with B.A.T.M.A.N. pretty easily so I never dug into the details.
If you have BMan running then ensure you turn off 802.11 forwarding (else you making it do double the work)
Yeah, I'll have to do some more packet dumps at some point to see what is really going on It was all very much hacked together, so it's entirely possible there are inefficiencies like this in there. 😆
😎