hyprspace
hyprspace copied to clipboard
alecbcs
Hyprspace README might need an update
I just tonite found out about hyprspace.
The Github README file though said this about Wireguard:
It can be used as a central relay to reach the other nodes in the network. However, this means that all of the traffic for your entire system is going through that one system which can slow down your network and make it fragile in the case that node goes down and you loose the whole network.
I don't think that's totally accurate. There are quite a few Github Repo's covering use of Wireguard for full-mesh network overlays.
Hi @bmullan as far as I understand it (and I could totally be wrong!) unless each Wireguard node has a public IP address, the only other way to access them is by routing your traffic through one that does right? I guess what I was getting at here is that if most of your infrastructure is without public IPs (for example home servers and laptops) then loosing that one public node leaves everything else without a way to talk to each other across NATs.
I think in one sense your description was correct.
This yCombinator thread on Wireguard mesh networks is interesting.
There are quite a few fairly simple wireguard full-mesh solutions today.
One of the tools I found useful is vxWireguard-Generator
I built a mesh to interconnect containers on multiple cloudes with FreeRangeRouter (FRR), BGP w VRFs, Wireguard, VxWireguard-Generator. It worked well and the 10.x.x.x containers on Digital Ocean & Hetzner cloud servers could talk directly via the VPN mesh.
vxWireguard-Generator sounds very interesting! Does this require every client to have a public IP address however or does it also do some sort of NAT hole-punching? I'm guessing that when you created your mesh on the different clouds each VM had a public IP right?
https://github.com/m13253/VxWireguard-Generator/issues/2#issuecomment-498973613 Seems to state that VxWireguard doesn't support NAT hole-punching currently; it only does relaying
