3 ms·
> Wireguard is pure classic hub-and-spoke No it's not. You can do any to any just fine (and any topology in between these extremes).
by megous 3y ago
> Wireguard is pure classic hub-and-spoke
No it's not. You can do any to any just fine (and any topology in between these extremes).
- xoa 3y agoNice job skipping the explicit qualifier of "plain vanilla"? Being able to build your own version on top isn't the same as an existing tested product.
- megous 3y agoNot sure what you mean by "on top". All you need is to configure not just a single endpoint in each node's wireguard config, but all of them. That's still as vanilla and as "tested product" as it gets. It's just a regular wireguard configuration.
- ElectricalUnion 3y agoYou can do any to any just fine [open NAT ports, run your own distributed fallback network of TURN/STUN relays, add the adequate routing entries to your routing tables on both sides, exchange certificates, all of this for every extra N connections], you just probably don't want to do (and then fix if it doesn't work or stops working) that if N is too big.
- megous 3y agoYes. I may also run it on top of IPv6 and not care about all that, except for public key distribution.
- ElectricalUnion 3y agoIPv6 when it works is awesome. However, outside some well-connected datacenters with multiple peering exchanges, I have no clue where in the world you can run everything in IPv6 with even a single nine in availability. On my home I would say assuming single nine availability of IPv6 traffic is too much availability - it's very common that IPv6 is borked for several months in a row.