11 Jan
2020
11 Jan
'20
9:33 p.m.
There is definitely an overlap of functionality between APRS and DR’s goals. The reason
APRS works is because of the large volunteer army of hams. I wouldn’t say APRS does
“mesh”, but with the right path settings it does multihop to get to an igate and on to the
internet. APRS has a significant RF and internet infrastructure. I would hope DR could
be lighter weight than that.
I think that since DR's application layer is using TCP/IP, the NET and Link layers
could be more akin to 6LoWPAN <https://en.wikipedia.org/wiki/6LoWPAN> and meshing
via RPL <https://en.wikipedia.org/wiki/RPL_(IPv6_Routing_Protocol_for_LLNs)>.
Projects like RiotOS <https://www.riot-os.org/> or Thread
<https://github.com/openthread/openthread> might provide a foundation.
!!Dean
On Jan 3, 2020, at 11:06 PM, Michael D
<digitalpig(a)protonmail.com> wrote:
I just had the thought, and then the thought to see what you folks would think of it..
The title sort of says it all. I had been thinking of LoRa mesh gizmos and fiddling with
designing a mesh transport layer. Ive come as far as two nodes essentially swapping
simple json. But I kept thinking about an APRS node I made w a baofeng and an RPi3. And
how all of this was basically another way of doing what the APRS net and AX.25 already do
in the amateur radio slice of things.
So what? So why not just stuff ax.25 and aprs 'digipeating' over LoRa? It
literally meets every 2-way and mesh-way transport requirement. Message relay and
broadcast, 'callsign'/node id destination addresses, etc etc.
A route for this might be micropython and https://github.com/sjlongland/aioax25/
<https://github.com/sjlongland/aioax25/>
Anywho, whats anyone's thoughts on this? Completely nuts / totally hopeless / maybe
possibly interesting?
_______________________________________________
DisasterRadio mailing list
DisasterRadio(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/disasterradio