Distributed peering about fastd HOT 3 OPEN

Something similar has been implemented in OpenWrt on top of WireGuard
https://forum.openwrt.org/t/new-wireguard-based-openwrt-vpn-implementation-unetd/136028
https://openwrt.org/docs/techref/unetd

from fastd.

Actually...I realized that this is very familiar to a tool that I used to use...Which is called flannel: flannel-io/flannel: flannel is a network fabric for containers, designed for Kubernetes (github.com)

As a Kubernetes engineer myself I obviously know how the CNI is built upon various tunneling tech (Calico use a mix of VXLAN and BGP to make EVPN), but I was never told what the specific implementation details are, and right here it is actually quite similar. 

For flannel, etcd is indeed being used as a DHT to share peering details, and I couldn't believe what I thought was already done by others for a long time.

Maybe I should close this issue for now, let me get some time to sort out my mind.

from fastd.

I'd rather not add additional complexity to fastd - it is meant to be small with a reduced feature set to work on the cheapest embedded Linux hardware, not to cover all possible use cases of VPN tunnels (for a long time OpenWrt devices with 4MiB storage and 32MiB RAM for the whole system were fastd's primary target, although unfortunately OpenWrt has outgrown that class of device by now...)

In any case, C would not be my programming language of choice for less constrained environments and a lot of the feature ideas you mention.

from fastd.