Current implementation: the shared-RAM contract and engineering record
Current source.
FawcettJohnW/FrogNet-Living-Network
The repository contains the network, Ribbit, FD&F integration and the current application trees. The October 11 manifest and merge records identify the baseline reviewed for this site. Read that baseline before using an older video or book as an installation guide.
Use matching packages and inspect their build.
| Target | Current package in the source tree | Prerequisite |
|---|---|---|
| Linux x86-64 node | opt/fdf/dist/fdf-install-x86_64.run | Existing FrogNet installation; root, python3, wg, systemctl and tar. |
| Linux ARM64 node | opt/fdf/dist/fdf-install-aarch64.run | Same existing installation requirement; matching architecture. |
| RAM manager + hub | opt/fdf/dist/fdf-droplet.tgz | Operator’s site configuration, reachable service ports and systemd units. |
| Windows x64 | opt/fdf/windows/bridge/ | Administrator terminal; amd64 wintun.dll from its authors. |
| Android | opt/fdf/src/frognet-android/ | Android build environment; membership app includes Communicator. |
The source archive reviewed here is r19-a15. Read the BUILD file and startup logs on the machine you are using. A filename alone does not prove the deployed version. The packages are in the repository tree; this website archive does not contain those large release binaries.
Linux node update.
Have the region operator prepare the RAM manager and hub first. Copy the matching .run file to the node, supply the operator’s site key privately, and run the architecture-specific installer. The installer checks the existing FrogNet path and configures region membership. It prints the installed build and a startup report.
sudo bash /tmp/fdf-install-x86_64.run <SITE_KEY>
# ARM64 node instead:
sudo bash /tmp/fdf-install-aarch64.run <SITE_KEY>These are the existing package invocation forms, not a clean-machine installation promise. The reviewed cleanup plan identifies broker-generated key and installer dependencies that need correction before fresh region installs can be claimed.
Windows bridge.
Copy the bridge folder to the PC. Obtain bin\amd64\wintun.dll from the authors’ Wintun package and put it beside the launcher. Edit etc\ponds.txt, one area=host:port per pond. Open an Administrator terminal in the bridge folder.
fdf-bridge.cmd
# In another terminal:
fdf-bridge.cmd ask status
fdf-bridge.cmd ask resolve w:<GUID>:<PORT>
fdf-bridge.cmd ask comms
fdf-bridge.cmd forward <POND>The first run creates the PC’s identity, key and facts. It places the PC on the mesh or builds the off-mesh hub path. Ctrl-C ends membership and removes the adapter routes and tunnels. Stop any older hand-configured client/tunnel using the same key before starting this bridge.
Android member and Communicator.
Build the current membership app from opt/fdf/src/frognet-android. The reviewed project uses compileSdk 34 and minSdk 29. Configure the ponds, start membership and grant the platform’s VPN consent for its TUN. The Communicator button opens the app’s own Communicator screen using the pond’s resolved RAM and media identities.
The old standalone Android Communicator is superseded. Android r5 combines the current pond-based launch with full-screen call controls, a movable camera inset, fill/fit, stats and camera selection. Keep sources and embedded fdf-tun binaries together.
Observe the network you actually joined.
/opt/fdf/bin/fdf-monitor --once
/opt/fdf/bin/fdf-ls --watch
cat /opt/fdf/BUILDInspect participant facts, planned routes, hub handshake state and the device’s hosts-file name. A successful session is one check; a working packet path is another. The operator controls port exposure and access policy. Read the deployment boundaries.
License.
The project is published under GPLv2-only. The repository’s LICENSE and the notices of included dependencies are the authoritative texts for the software you obtain. Read the project license page.