Linux

48363 readers

1320 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Webmesh: Yet Another WireGuard Mesh Solution (github.com)

submitted 1 year ago by tinyzimmer to c/[email protected]

4 comments fedilink hide all child comments

Hey all

I wanted to show off my new project, webmesh. It's yet another solution for creating WireGuard mesh networks/VPNs between multiple hosts, most similar to projects like TailScale/ZeroTier. It differs from others in that there is a controller-less architecture that maintains the network state on every node via Raft consensus. This allows for any node to become the "leader" should one go away.

Github in the link above. More infoz in the README and on the project website: https://webmeshproj.github.io

Excited to hear any feedback :)

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago) (1 children)

This sounds super interesting

Will this work in a situation where all clients are behind NAT? (Specifically cases where the Admin has no control of the NAT, like with CGNAT or clients on mobile networks)

And if it does, how do clients find each other without some central server?

[–] tinyzimmer 3 points 1 year ago* (last edited 1 year ago)

So it will work with clients behind NATs. By default the network is a little different from similar solutions in that not everyone is directly connected peer to peer. The default behavior is to branch off from the server you joined (with traffic to the rest of the network routed through them). Then via the admin API (or configuration/RBAC that needs to be better documented) you can tweak the topology by putting "edges" between devices. If there is no direct connectivity between the devices they will use ICE tunnels to connect. One of the APIs that can be exposed on nodes helps with candidate negotiation, and another one can be a TURN server if you want. Sorta demonstrated here https://github.com/webmeshproj/webmesh/tree/main/examples/direct-peerings but it's a fake test because it happens on docker networks.

To your second question, there has to be someone accessible currently. But I've included an idea of a Peer Discovery API server that devices can optionally expose. In that vein you could have a node that just provides peer discovery and nothing else.

It's kinda pointless though because the server running the API has to be a member of the cluster already - so in that way they become a "central server". I want to add more options, such as SRV lookups. Always happy for help and more ideas too :)