n2n VS gon2n

n2n - - Built on nodes and supernodes. GPL-3.0 license. Written in C.

Repository in Github: n2n

Check out n2n.

n2n - seems easy and maintained, but need to manually compile own binary

Apparently it's "based on n2n", so basically they've put a UI on top of this https://github.com/ntop/n2n, made by ntop by the looks of it.

> Is what makes this a "P2P" VPN [...] that it supports the group/"community" network behavior?

More or less! Compared to say OpenVPN there is no central server that all traffic is routed through (unless you choose to activate TURN of course, see the `--force-relay` flag), so hosting it is much cheaper as the only public part of the infrastructure is the part that exchanges the candidates ^^ Its pretty close to how n2n[1] does it, but has proper NAT hole punching support due to the WebRTC backend.

> When you do that, are you building a full-connected overlay network [...]

Yes! Its a full mesh; it seems to scale pretty well to a fairly large number of nodes, although I haven't tested it with more than ~100 peers in a single community yet. If the overhead of maintaining all of the connections is too much or peering between nodes in an issue, TURN can help to connect those peers with the rest of the mesh. Orchid looks interesting!

[1] https://github.com/ntop/n2n

Not sure if n2n would work for your setup. Apparently, there's a gui now. I haven't tried it on windows.

/skin/edge.exe - This is part of the n2n VPN setup which can be found here: https://github.com/ntop/n2n

Otherwise my plan is to use n2n so I don't need to setup a vpn server and n2n also takes care of the nat firewall. I want to wrap everything up into two shell scrips, one to install the required software, configure everything and start the session and of course one to shut everything down again.

Hi! n2n was a huge inspiration for the project, in fact I wrote Go bindings for n2n before starting it: https://github.com/pojntfx/gon2n

Weron also allows tunneling - just specify a TURN server on `--ice` and enable `--force-relay`, in which case it will probably scale to well over 100 nodes ^^ The signaling servers are fully horizontally scalable, so that you can benefit from a faster backbone on a global scale scenario - Redis coordinates messages, kicks etc. between them and a Postgres database maintains central state, such as credentials for persistent communities and client counts.

In terms of key rotation & encryption - weron heavily depends on DTLS as provided by Pion/WebRTC and thus inherits similar security properties. It is not possible to disable encryption of WebRTC, but tbf the performance benefits of using plain SCTP don't seem to be worth it as the RTT latency and resulting decrease in throughput[1] is the dominant performance bottleneck.

[1] https://tuhat.helsinki.fi/ws/portalfiles/portal/167373638/Es...