Files
fips/docs
Johnathan Corgan 10cd43361b Merge branch 'maint' into master
Brings the tarball upgrade restart, release-candidate Debian versions, the
rekey-disable deprecation note, the interop harness change, and the Ethernet
socket leak, TCP address fallback and gateway NAT retry fixes up from maint.

Resolutions:
- io_linux.rs: keep master's ENODEV/ENXIO absence branch in the bind failure
  arm, without its manual close, since the OwnedFd guard now closes the socket
  on every error return.
- The socket leak test runs without #[ignore] under the FIPS_TEST_PRIVILEGED
  convention, so the privileged CI leg exercises it, and accepts master's
  InterfaceUnavailable for a missing interface.
- tcp/mod.rs: master's connect signature with maint's multi-address
  resolution; maint's tests, less a helper master no longer uses.
- CHANGELOG: maint's entries added under master's areas, with the socket leak
  entry reworded for master, which has no beacon socket reopen.
2026-09-30 18:58:54 +00:00
..
2026-09-30 18:58:54 +00:00
2026-09-29 00:11:14 +00:00
2026-09-29 00:01:53 +00:00
2026-08-30 10:42:59 +00:00

FIPS Documentation

FIPS (Free Internetworking Peering System) is a self-organizing encrypted mesh network built on Nostr identities, capable of operating over arbitrary transports — local networks, the public internet, Tor, Bluetooth, or point-to-point links — without central infrastructure.

With FIPS, your machine becomes a node in the mesh with a self-generated cryptographic identity. There are two ways to deploy it.

As an overlay on top of existing IP networks, FIPS lets your node reach any other FIPS node wherever it sits — behind a NAT, on a different ISP, on a phone over cellular, on a laptop with only Bluetooth in range, or behind a Tor onion. The mesh forwards IPv6 traffic transparently and end-to-end encrypted, with no central VPN concentrator or coordinating server.

From the ground up over raw Ethernet, WiFi, or Bluetooth, FIPS provides a complete permissionless network without any pre-existing IP infrastructure, ISP, or DNS. Any node that joins the link gets routable IPv6 addresses, peer discovery, and a path to every other node automatically.

Either way, existing networking software runs over it unchanged: SSH, HTTP servers, file transfer, anything IPv6-native works the same way it would on a local network.

New to FIPS? Start with the Getting Started guide.

Documentation Sections

Tutorials

If you are starting from scratch and want a guided path to a working mesh, go here.

How-To Guides

If you have a specific task in mind — enabling a feature, deploying a component, diagnosing a problem — go here.

Reference

If you need to look up wire formats, configuration keys, command flags, or counter inventories, go here.

Design

If you want to understand how the mesh self-organizes, why FIPS makes the choices it does, or how the pieces fit together, go here.

Releases

If you want the notes for a particular version — what changed, what broke, and what to do about it on upgrade — go here.