A distributed, decentralized network routing protocol for mesh nodes connecting over arbitrary transports.
A new FIPS release is out! v0.5.3 makes your node harder to mess with: OpenWrt routers are no longer open to the whole mesh, gateways serve only their own LAN, and forged or replayed messages can no longer knock over your links or starve discovery. And you can now embed FIPS straight from crates.io as `fips-mesh`.
We've got exciting news for you, another FIPS release! New features, new platforms and many, many bugfixes! We've landed the first version of the native API that lets you interact with other nodes over FIPS directly, without going through IP first. Android and FreeBSD are now supported and much more.
It has been about six weeks since v0.3.0, and the response has been great. We estimate the public test mesh averages 1500-1600 nodes online at a time, with the optional bootstrap nodes peering with hundreds of inbound connections each.
In the months since v0.2.0, a community has crystallized around FIPS. Operators have stood up nodes across regions and run them on the public test mesh; contributors have reviewed patches and reported bugs against real traffic; and developers have landed substantial new features.
A proof-of-concept FIPS node on Android — UDP and TCP transports, TUN adapter, .fips name resolution, Kotlin via UniFFI.
Six protocol features that landed against jmcorgan/fips during SEC-07 weeks 1–3 — automesh, gateways, ACLs, hole punching.
A FIPS-native search engine that indexes services via Nostr events and serves Iris and Jumble over the mesh.
FIPS v0.2.0 is now available. This release includes a major discovery protocol overhaul, Tor transport support, runtime peer management, and 12 bug fixes.
We're happy to announce the first tagged release of FIPS, the Free Internetworking Peering System. FIPS is a transport-agnostic, self-organizing mesh network that lets nodes discover each other and route traffic without any central authority.
