Hey all!

Dropping my Webmesh project (https://github.com/webmeshproj/webmesh) again as I've just reached a major milestone in my development towards making it a viable product. Webmesh is yet another pass at creating a distributed service/application mesh/VPN using WireGuard. More infoz is on the project website: https://webmeshproj.github.io/

With the new "mesh bridge" capabilities, you can run a bridge node between two or more meshes that serves to forward appropriate traffic between them. It also offers DNS forwarding capabilities to lookup internal names across meshes. This is accomplished by running two or more IPv6 only wireguard interfaces connected to each mesh and sharing routes between them. IPv4 support is planned, but honestly may not even be necessary. You can see a reference example/playground here: https://github.com/webmeshproj/webmesh/tree/main/examples/mesh-to-mesh

Excited for your feedback :)

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 :)

Hiya Folks

Making the rounds again on this project as it is getting closer to being feature-complete (ish) and I've started this website for extended infoz/documentation. Main repository can be found here: https://github.com/webmeshproj/node.

The project aims to be yet another simple WireGuard Meshing/VPN solution. Most similar to TailScale/HeadScale, but with a controller-less architecture governed by Raft consensus.

I'm excited to hear any feedback. Contributions are welcome as well :). Anything from architecture discussion, to issues, to code, to docs is appreciated.

Been slowly stabilizing my new project I'm calling (for lack of a better name at the moment) Webmesh and hitting the rounds on some social networks.

It's yet another mechanism for configuring WireGuard networks, with the core difference from others being that it uses raft-consensus to maintain state between connected instances. This allows for any node to optionally be a "controller server" on top of being a spoke in the network. There is more information in the Github - but tons more documentation is needed for sure.

I'm building a plugin architecture around it as well as potentially looking to build a saas or some other type of offering. Been actively looking for another developer or two who may be interested in embarking on the adventure with me. Feel free to reach out if interested. Also happy to hear any feedback :)