+1
日增长
5,582
stars
218
forks
58
watchers
171
prs
222
issues
47
releases
README
innernet A private network system that uses WireGuard under the hood. See the announcement blog post for a longer-winded explanation. innernet is similar in its goals to Slack's nebula or Tailscale, but takes a bit of a different approach. It aims to take advantage of existing networking concepts like CIDRs and the security properties of WireGuard to turn your computer's basic IP networking into more powerful ACL primitives. innernet is not an official WireGuard project, and WireGuard is a registered trademark of Jason A. Donenfeld. This has not received an independent security audit, and should be considered experimental software at this early point in its lifetime. Usage Server Creation Every innernet network needs a coordination server to manage peers and provide endpoint information so peers can directly connect to each other. Create a new one with sh sudo innernet-server new The init wizard will ask you questions about your network and give you some reasonable defaults. It's good to familiarize yourself with network CIDRs as a lot of innernet's access control is based upon them. As an example, let's say the root CIDR for this network is 10.60.0.0/16. Server initialization creates a special "infra" CIDR which contains the innernet server itself and is reachable from all CIDRs on the network. Next we'll also create a humans CIDR where we can start adding some peers. sh sudo innernet-server add-cidr For the parent CIDR, you can simply choose your network's root CIDR. The name will be humans, and the CIDR will be 10.60.64.0/24 (not a great example unless you only want to support 256 humans, but it works for now...). By default, peers which exist in this new CIDR will only be able to contact peers in the same CIDR, and the special "infra" CIDR which was created when the server was initialized. A typical workflow for creating a new network is to create an admin peer from the innernet-server CLI, and then continue using that admin peer via the innernet client CLI to add any further peers or network CIDRs. sh sudo innernet-server add-peer Select the humans CIDR, and the CLI will automatically suggest the next available IP address. Any name is fine, just answer "yes" when asked if you would like to make the peer an admin. The process of adding a peer results in an invitation file. This file contains just enough information for the new peer to contact the innernet server and redeem its invitation. It should be transferred securely to the new peer, and it can only be used once to initialize the peer. You can run the server with innernet-server serve , or if you're on Linux and want to run it via systemctl, run systemctl enable --now innernet-server@. If you're on a home network, don't forget to configure port forwarding to the Listen Port you specified when creating the innernet server. Peer Initialization Let's assume the invitation file generated in the steps above have been transferred to the machine a network admin w
Top issues
#203Binary packages no longer built (was: 1.5.4 package doesn't work on Debian buster)18 comments · 2022-03-16#137api docs14 comments · 2021-09-01#26Add more protections against OS configurations that allow IP spoofing13 comments · 2021-03-31#19Support Windows13 comments · 2021-03-31#163timeout when simultanious redeeming11 comments · 2021-10-10#25OpenBSD support11 comments · 2021-03-31#216Something like tailscale's "magicdns"?10 comments · 2022-05-05#135Cannot redeem invite on same machine as server10 comments · 2021-08-27
Discussions
#412More user-friendly install options.0 comments · 2026-10-21#403v2.0.00 comments · 2026-07-02#381Slow speed between the innernet "server" and clients1 comments · 2026-02-16#374Auto Deploy Self Healing Innernet0 comments · 2025-11-23#319Additonally export innernet-server as a lib2 comments · 2024-08-26#287design details?2 comments · 2023-09-18#271v1.6.00 comments · 2023-06-14#245Headless deploy for peer innernet2 comments · 2023-01-26
Latest release
v2.0.0 v2.0.0 2026-07-02[!tip] Even though this is a major version release, innernet server and client 2.x is fully compatible with innernet server and client 1.x. In fact the server and client binaries have received only modest improvements/fixes since 1.7.1. We've just made semver-incompatible changes to the Rust libraries (newly introduced innernet-client-core, innernet-server, innernet-shared) that we also publish and these prompted a major version bump. In fact, further changes to the Rust APIs are in the works (https://github.com/tonarino/innernet/pull/391, https://github.com/tonarino/innernet/pull/39