Since Charlie replied to the group as a whole, I might as well respond
to the group as a whole. No OGNbase does not use FANET. The text on
that front page on github is from the original developer of OGNbase,
from a while back, and is somewhat misleading regarding the current
version. That's why I suggested starting with the documentation file
that I wrote:
https://raw.githubusercontent.com/moshe-braner/Open-Glider-Network-Groundstation/main/ognbase/documentation/documentation.txt
Some day I'll get around to updating the front page... Been too busy
coding and testing. But did update that text file multiple times.
But yes, "it would not relay to a PI based OGNground station". Both the
"remote" station and the "base" station must run the OGNbase software,
because the two ends of the relay setup need to know how to communicate.
The radio messages between them are invisible to FLARM, and invisible
to other OGN stations even if they are within reception range.
Invisible not because it uses FANET (it doesn't), but because it is
deliberately formatted to not look like a valid FLARM message, and also
is sent on a frequency FLARM is not listening to at that moment. (FLARM
uses a frequency hopping scheme that depends on the *exact* UTC time -
since it has a GNSS (GPS) receiver that is possible.) The relay
messages are also encrypted using a security key, and are thus rejected
if received by other OGNbase stations within range. The relay messages
are private to the pair of OGNbase stations configured in that specific
relay setup. The base station decodes them, and posts the original
FLARM traffic info to the OGN servers.