kilo VS wesher

For the particular case of creating a wireguard mesh network in kubernetes, I've been quite happy with Kilo[0]. Does anyone with experience in both kilo and netmaker know how they compare?

[0]: https://kilo.squat.ai/

Then using something like this: https://docs.tigera.io/calico-enterprise/latest/compliance/encrypt-cluster-pod-traffic#value or: https://github.com/squat/kilo

Another one for the alternatives list is Kilo[1]

It's a wireguard based kubernetes network overlay. I use it to access private services in my homelab cluster from my laptop, phone, etc.

[1] https://kilo.squat.ai

Sorry, big typo, I meant "Kilo" and not "Silo"...

Networking: Manually configured wireguard VPN between all nodes. I consider checking out kilo when I find some time though. VPS handles all incoming traffic (with ingress-nginx) but outbound traffic from containers uses regular network, no VPN.

Kilo — Wireguard-based multi-cloud overlay

https://github.com/costela/wesher

Wiresmith: Rust, auto-configs clients into a mesh

Maybe take a look at Wesher https://github.com/costela/wesher

I run a Wireguard mesh network with Wesher, and I am pretty sure that there are other projects to automate this. Is there a reason not to use them?

From a purely networking perspective, there are far better solutions than tailscale.

Have a look at full mesh VPNs like:

https://github.com/cjdelisle/cjdns

https://github.com/yggdrasil-network/yggdrasil-go

https://github.com/gsliepen/tinc

https://github.com/costela/wesher

These build actual mesh networks where every node is equal and can serve as a router for other nodes to resolve difficult network topologies (where some nodes might not be connected to the internet, but do have connections to other nodes with an internet connection).

Sending data through multiple routers is also possible. They also deal with nodes disappearing and change routes accordingly.

tailscale (and similar solutions like netbird) still use a bunch of "proxy servers" for that. You can set them up on intermediate nodes, but that have to be dealt with manually (and you get two kinds of nodes).

There are two factors at play here. The client's public IP actually depends on the gateway they use on accessing the internet. You can disable routing and your clients will keep their public IP and general internet access won't go through the VPS. However, if you want the traffic between "clients" also skip the VPS, then you want a mesh network. wesher and wg-meshconf can help you on configuring them.

Have you considered https://github.com/costela/wesher or does this not fit your use case?

I use Hashicorp Consul and Hashicorp Nomad for service discovery and task scheduling respectively, with wesher for my internal private management network that Consul, Nomad, etc run on to protect the management interfaces. Fabio bridges the gap between the wesher wireguard VPN and the rest of my home network.

How does your solution compare to wesher?

How does it compare to https://github.com/costela/wesher?