ziti-doc VS n2n

OpenZiti vs BoringProxy has some similarities for sure. The simplest OpenZiti deployment is similar to a boring proxy deployment. The main differences will be that the listening ports "on the network" are going to be from the OpenZiti edge-router which will authenticate before allowing any connection using a strong x509 identity (not a token) and then after that the same identity can be authorized to access one or more services. That's one killer difference to me. There are lots of other things OpenZiti is doing that boringproxy isn't trying to as well. I filed an issue to do a comparison to that some day https://github.com/openziti/ziti-doc/issues/176 thanks for the idea! :)

Use our open source solution, OpenZiti, and host/manage it all yourself - https://openziti.github.io/

You can definitely read more about what OpenZiti is over on the docs page if you're looking for more info about the project https://openziti.github.io/

If you're interested in it, you can find it over at github - https://openziti.github.io. It's one more thing to setup and maintain so maybe that's a dealbreaker but since this is selfhosted - maybe not ;)

If you want to go fully open source and self-hosted, use an OpenZiti quickstart - https://openziti.github.io/ - while ignoring steps 1, 2, 3, and 5 ... i.e., step 4 is where you deploy an OpenZiti tunneler on an OpenWRT box.

I not long ago discovered OpenZiti, and to be honest I fell in love with it. I also have a dinamic IP, and I have even some other cases wheren from my place some IoT devices need to find my laptop wherever I may go (I travel a lot).

https://openziti.github.io/ - gives a good intro

More details: What I'm trying to do is setup a Zero Trust Host Access on my Kubernetes cluster using OpenZiti. Ziti has 4 binaries (controller, router, tunneler and admin console), configuring all these to work together is kinda complex, that's why I thought about making custom modules.

Probably overkill for your need, but you can give access to your VM without requiring a bastion or VPN, only outbound ports on a NAT gateway using opensource OpenZiti - https://openziti.github.io/. The user would load a client on their device and get access only the the specific resources you define (IP, DNS, port etc). This also means you don't need to assign the IP of the users home (added benefit they can access when not at home).

Create the identity for the Hosting workstation. You can assign as many attributes as you want. Openziti works with an "attribute-enabled role-based access control (ARBAC) model. So, if you have used hashtags, you’re probably familiarized with it.

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.