n2n

Nothing about this website really gives a whole lot of confidence. It claims to be "Started from US", but the broken English that's prevalent on every single page says otherwise, there's no information about what company is supposedly behind its creation, and the webserver is behind cloudflare. Both the git repo and the website proper are filled with broken links and errors, text that does exist readably is close to complete nonsense. > Traffic over OmniEdge is end-to-end encrypted by Twofish/AES128/ChaCha20 cipers' P2P MESH network. I'm grasping at straws to find a single thing which looks legitimate about it. You'd have to be completely nuts to even begin looking into this as a solution for anything. If you're interested in what the technology behind this is, it's just a thin veneer of https://github.com/ntop/n2n.

> 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

In theory it's already there on Linux by using some overlay network (like ZeroNet[1] or ntop's n2n [2]) and KDE Connect (it has "Send SMS from desktop" feature) which works between desktops running K too. [1]https://github.com/zerotier/ZeroTierOne [2]https://github.com/ntop/n2n