4 ms·
If you have the right config-files setup, it's a matter of typing 'wg-quick up <configname>' ... and then you will have a VPN up. Bring it down again with 'wg-q
by sigio 7y ago
If you have the right config-files setup, it's a matter of typing 'wg-quick up <configname>' ... and then you will have a VPN up. Bring it down again with 'wg-quick down <configname>'.
The configs itself are basically just the IP's used, and the peers and keys used to communicate with those peers.
(Running a 70+ node full-mesh vpn)
- Diederich 7y ago> 70+ node full-mesh vpn ~2^70 VPN connections?
- HideousKojima 7y agoWouldn't it only be 70^2 (or 69^2 or 69*70 maybe?)? Each of the 70 devices has a VPN connection to 69 other devices. So only ~5,000 total
- rnestler 7y agoIt would be (69*70) / 2, since connections are bi-directional, so only ~2500 connections.
- Diederich 7y agoThat's right, I got the two mixed up.
- philsnow 7y agowireguard uses UDP so they're not actual "connections"
- nikisweeting 7y agoYeah this is a critical point that the others are ignoring, it only sends packets when they're actual traffic. Maintaining 5000 connections is pretty easy when they're not big stateful TCP sockets.
- blattimwind 7y agoWireguard is not connection based, so a full-mesh VPN with n nodes essentially just means each node has n-1 peer keys and maintains a routing table with n-1 entries for the VPN.
- mindslight 7y agoThere are still 70x69/2 connections going on under the hood. You can't completely ignore that complexity - if there are underlying connectivity issues, specific host-host traffic will fail (eg due to NAT). My wireguard setup actually has n x (n-1) config files/instances (current n=8), as that's the only way to shuffle default-gateways over it. It's a little unwieldy, but still manageable. Whereas I can't imagine doing the same with OpenVPN.