#Tag
Ik zie zojuist in #Nijmegen een repeater van @waag #Amsterdam binnenkomen met #meshcore #lora techniek.
Toch bijzonder hoe we samen een open source netwerk tot stand kunnen brengen.
Next week, students from Radboud University will visit. They’re very interested in mesh communications, and we’ll introduce them to MeshCore—another opportunity to increase the density of our local Nijmegen mesh network. A denser network means stronger connections across the Netherlands (and beyond).
#MeshCore #LoRa #RadboudUniversity #hacking #HackerspaceNijmegen
Ik zie zojuist in #Nijmegen een repeater van @waag #Amsterdam binnenkomen met #meshcore #lora techniek.
Toch bijzonder hoe we samen een open source netwerk tot stand kunnen brengen.
Next week, students from Radboud University will visit. They’re very interested in mesh communications, and we’ll introduce them to MeshCore—another opportunity to increase the density of our local Nijmegen mesh network. A denser network means stronger connections across the Netherlands (and beyond).
#MeshCore #LoRa #RadboudUniversity #hacking #HackerspaceNijmegen
Step 1(b) was securing my digital #Privacy, which meant controlling my home network, which meant... 
I'll be 32 in 4 weeks, and for the first time in my life, I'm living alone in my own apartment. More on this later.
Step 2 is #SelfHosting my own data and services. I'm working on that now, on a #RaspberryPi 5 running #yunohost (much appreciation to @_elena for sharing her journey). I've got some DNS/proxy issues to work out before inviting you into my digital home, but stay tuned.
Step 3 will be expanding my pocket universe to my #Community. I've got some #LoRa communication nodes and will be setting up some repeaters, hopefully sometime soon. Hopefully, I'll also be able to host a #Bonfire instance to serve the area.
( @bonfire Social 1.0 arrived literally as I was putting my Pi 5 together. Thanks for your hard work!)
Working on BLE packet sniffing and transmission for MeshTNC, bc who doesn't want to do APRS or meshcore over BLE advertisements 😉
My quick hack feels promising so I think I'll clean this up and PR it.
Just needed one tweak to the KISS encoder to define our port usage and give myself a way to put BLE data out a different port than LoRa data when in KISS mode.
Planning to also support streaming GPS NMEA over KISS eventually as well as promiscuous mode WiF sniffing.... eventually.
So reserved some values for that stuff.
Working on BLE packet sniffing and transmission for MeshTNC, bc who doesn't want to do APRS or meshcore over BLE advertisements 😉
My quick hack feels promising so I think I'll clean this up and PR it.
First things first, I want to make it so that the ASCII CSV output format for BLE packets roughly matches LoRa packets.
Every packet gets an arrival timestamp, type, RSSI and SNR values. Followed by whatever payload.
In the case of BLE packets there's also a 6 byte MAC so I slap that infront of the payload.
There's no SNR data for BLE so that's always 0.0. But the RSSI is good.
Working on BLE packet sniffing and transmission for MeshTNC, bc who doesn't want to do APRS or meshcore over BLE advertisements 😉
My quick hack feels promising so I think I'll clean this up and PR it.
Most wireless tutorials teach theory. The Wireless Cookbook teaches function.
Learn how Wi-Fi, Bluetooth, and LoRa actually behave in real environments by building working systems with Raspberry Pi and Linux.
From mesh networks to long-range LoRa nodes, every project is designed to perform reliably in the field.
Most wireless tutorials teach theory. The Wireless Cookbook teaches function.
Learn how Wi-Fi, Bluetooth, and LoRa actually behave in real environments by building working systems with Raspberry Pi and Linux.
From mesh networks to long-range LoRa nodes, every project is designed to perform reliably in the field.
3 Handys, 3 LoRa Devices, 2 Raspberrys, 1 PC, 1 Notebook und natürlich der Rootserver in Nürnberg - diese Hardware habe ich gestern genutzt, um ein neues Reticulum Backbone, einen zuverlässigen Propagation Node und einen Collector zu erstellen und zu testen.
Bereits vorhandene (Test) Netze werden gebrückt, sodass kreuz und quer alles und jeder erreichbar ist.
Der Propagation Node ist, wenn er fest eingetragen ist, zuverlässig und Nachrichten, die in Abwesenheit gesendet wurden, können so auch schnell abgefragt werden.
Auf dem Collector Node können, für diejenigen, die es möchten, die eigenen Telemetriedaten gespeichert, und (automatisch) aktualisiert werden und können so auch von anderen Nutzen dort auch abgefragt werden.
Das Backbone kann mit folgenden Daten eingebunden werden:
[[MV2K Reticulum Network]]
type = TCPClientInterface
interface_enabled = true
target_host = reticulum.mv2k.com
target_port = 4847
name = MV2K Reticulum Network
selected_interface_mode = 1
configured_bitrate = None
Der Propagation Node hat folgende Adresse: <2fe1e526b9d91e6a0a5cb48e7dd0f96f>
und der Collector Node ist unter <e3b8303e7e2e8c03694f5546264bc3f9> zu erreichen.
Ich freue mich, dass ich so auch einen kleinen Beitrag für Reticulum leisten kann. :)
#Reticulum #Sideband #Mesh #LoRa #Notfallkommunikation #Backbone
3 Handys, 3 LoRa Devices, 2 Raspberrys, 1 PC, 1 Notebook und natürlich der Rootserver in Nürnberg - diese Hardware habe ich gestern genutzt, um ein neues Reticulum Backbone, einen zuverlässigen Propagation Node und einen Collector zu erstellen und zu testen.
Bereits vorhandene (Test) Netze werden gebrückt, sodass kreuz und quer alles und jeder erreichbar ist.
Der Propagation Node ist, wenn er fest eingetragen ist, zuverlässig und Nachrichten, die in Abwesenheit gesendet wurden, können so auch schnell abgefragt werden.
Auf dem Collector Node können, für diejenigen, die es möchten, die eigenen Telemetriedaten gespeichert, und (automatisch) aktualisiert werden und können so auch von anderen Nutzen dort auch abgefragt werden.
Das Backbone kann mit folgenden Daten eingebunden werden:
[[MV2K Reticulum Network]]
type = TCPClientInterface
interface_enabled = true
target_host = reticulum.mv2k.com
target_port = 4847
name = MV2K Reticulum Network
selected_interface_mode = 1
configured_bitrate = None
Der Propagation Node hat folgende Adresse: <2fe1e526b9d91e6a0a5cb48e7dd0f96f>
und der Collector Node ist unter <e3b8303e7e2e8c03694f5546264bc3f9> zu erreichen.
Ich freue mich, dass ich so auch einen kleinen Beitrag für Reticulum leisten kann. :)
#Reticulum #Sideband #Mesh #LoRa #Notfallkommunikation #Backbone
Screenshot from SDRAngel of a #Meshtastic #LoRa packet on LongFast.
so... when do we get a cheap #LoRa smartwatch which 99.9% reliably gets notifications within a couple city blocks of your phone?
Over the weekend @meph added some mind blowing new features to lorapipe.
- APRS over LoRa
- Ethernet over LoRa
https://social.treehouse.systems/@meph/115365077448221139
#hamraadio #radio #lora #meshcore #meshtastic #lorapipe #aprs #ax25 #kiss #tnc #packetradio #networking #cybersecurity #offgrid
All of @meph 's work on #lorapipe is under MIT license.
Features like APRS over LoRa and Ethernet over LoRa serve some interesting niches we're not likely to monetize.
More than anything we want lorapipe to be a rapid prototyping tool for LoRa solutions. It's key for this to be as free and open as we can make it and I hope these features demonstrate our direction.
We'd appreciate donations towards the effort so we can knockout lorapipe v1.
Finally setup the github builder and now there's pre-release lorapipe firmware available for download!
We're building 79 different variants so testing on your favorite LoRa devices is highly encouraged!
Now that lorapipe has KISS-TNC protocol support for sending and recieving LoRa packets, it means that basically all sorts of ham radio and Linux tooling designed to talk to KISS modems suddenly work over LoRa.
For HAM radio nerds, this means things like APRS -just- work. Follow the instructions in the documentation to get started.
I suspect HAMs can bridge APRS across spectrums to ISM 433/868/915Mhz LoRa now using lorapipe. 😎
https://github.com/datapartyjs/lorapipe?tab=readme-ov-file#aprs-over-lora
Because this KISS-TNC stuff is pretty old, it has really good support on modern Linux.
So we're actually able to setup lorapipe on two different linux boxes and form an ethernet network over LoRa!
The current rev has some MTU limits we can fix, we can also eak out probably another 2x more bandwidth too.
But as is I was able to ping, mosh and ssh over my ethernet-LoRa network between Linux computers!
https://github.com/datapartyjs/lorapipe?tab=readme-ov-file#ethernet-over-lora
A space for Bonfire maintainers and contributors to communicate
