GitHub - webmeshproj/webmesh: A simple, distributed, zero-configuration WireGuard mesh provider
github.com
A simple, distributed, zero-configuration WireGuard mesh provider - GitHub - webmeshproj/webmesh: A simple, distributed, zero-configuration WireGuard mesh provider

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

  • giacomo@lemmy.world
    1·
    1 year ago

    Very neat! Definitely a project I’d like to follow.

    Makes me wonder if something similar could be implemented using frr, ospf, and ansible.

    • tinyzimmer@sh.itjust.worksOP
      1·
      1 year ago

      Almost certainly. At its core - everything happening could be accomplished with just regular configuration files. It’s just a suite around maintaining the state basically.

      I was considering adding FRR or BGP to the mix at some point - but it hasn’t proven necessary yet.