Current implementation: FD&F and the network path
1. Establish the platform.
A FrogNet node supplies the Linux networking, service and memory machinery. The current FD&F .run packages patch an existing FrogNet installation; they are not proven clean-box installers. Before installation, record the network interfaces, the uplink and the served LAN. Avoid changing the management path without understanding which interface is being reconfigured.
2. Observe local discovery.
Use a small local network to inspect membership, routes, service selection and sensor state. Keep Internet reachability separate from local usefulness. The original installation videos explain the local machinery but include superseded broker steps.
3. Create or join a region.
A region deployment needs a reachable RAM manager, a hub for routed off-mesh traffic, and the operator’s site configuration. The node publishes facts and mappings; the daemon derives and applies the graph. The hub is an actual relay service, even though application participants do not manage it.
Install the manager/hub package before patching the nodes. Use the matching architecture and build tags. The operator on-ramp lists the files and the current limitations.
4. Add a PC or Android device.
The Windows bridge and Android member place themselves from their addresses and the region’s facts. A device already inside a live member’s served /24 is on-mesh and uses that LAN. Off-mesh, it obtains a leaf address and reaches the hub. A change of default-network IPv4 set ends the session so placement can be recomputed.
On Windows, the first run generates identity and keys and creates a Wintun adapter. On Android, VPN consent is required for the VpnService interface. Those are platform mechanics beneath membership.
5. Resolve the application by identity.
The Communicator’s where cell advertises identity-based RAM and media endpoints. The member resolves them in the appropriate pond, using aliases when necessary. A current where cell contains identities, not a hard-coded application IP address.
Start the media and RAM services on a node, open the Communicator from the membership app or the bridge’s resolved server details, and observe the call and diagnostics.
6. Write your own participant.
Pick a truth and its owner. Publish it. Hold the state you need. Test replacement state, distinct records, restart and a changed memory world independently. Keep the application’s evidence separate from the network’s evidence.
Read the complete programming rules →