With OpenVPN you have all the bells and whistles, and it's easy to get tripped up in the myriad of configuration options. With WireGuard you start with the fundamentals: establishing the tunnel interface. Then you start adding routing, DNS etc. to suite your specific scenario.
You're 100% correct about this, but I think it's easy to miss that you could say very similar things about all sorts of very well designed, low-level technologies, that for years no one has bothered to build the necessary high level tooling around! Magic Wormhole is another great example: it's a brilliant system, it's even very easy to use from the terminal, but nobody has bothered to build a GUI around it or create any of the more complicated (but awesome!) tooling that the wormhole protocol allows. (At least as of the last time I looked into this.)
So maybe people knowledgeable enough to build it just waited for it, or went to apply PAKE like rdv on top of webrtc.
https://www.stavros.io/posts/how-to-configure-wireguard/
It takes hours to set up if you don't know how (and the docs aren't amazing), but it should take you ten minutes using my article.
This comes out in, for example, the "Accessing your home LAN" part of your article. It has a bunch of iptables magic that I understand, but presumably shouldn't have to in order to use WireGuard. Actually, the device that makes the most sense to use as a WireGuard server is my router, which is based on BSD; so presumably I'd need modify your commands to get this working on my OS! With OpenVPN, on the other hand, I can literally install a package for my firewall (OPNsense) and it's all done for me with a few clicks. That's what I mean by robustness: I'm capable of getting OpenVPN working on just about any computer, including my GUI based BSD router. WireGuard just doesn't have that yet.
I did, however, make it harder for myself by setting it up on a Unifi gateway. Where every push of an invalid config would put the gateway in a boot loop, bricking my internet connection for a few minutes.
For the interested: https://github.com/Lochnair/vyatta-wireguard
You might be interested in https://github.com/FossoresLP/vyatta-wireguard (no associaton, just a repo that I've found has the newer releases).
There seems to be a installer script (https://github.com/mafredri/vyatta-wireguard-installer) that will persist the deb between updates. This issue https://github.com/mafredri/vyatta-wireguard-installer/issue... will switch it to the port you suggest.
Perhaps I'll set that up. Given recent global events I've got some time, but not much need for a remote access solution right now!
For what it's worth this did seem easy to follow, I just know that when I tried to follow a guide similar to this one a while back I couldn't get it to work for a windows client.
I used StavrosK's guide (thank you!) to put together two scripts a while back, one for generating a new server config file, and one to generate a new client config, outputting the config to a file as well as to a QR code on stdout. You can copy the client.conf file over to the Windows machine and import the configuration via the "Import tunnel(s) from file..." option in the Wireguard client, or scan the QR code output from the mobile device clients via "Create from QR code".
Here's my script for generating a client cert: https://cdn.seedno.de/txt/wireguard-certgen. It assumes Wireguard is already configured on the server on interface wg0, and is using the default port of 51820/UDP, though both are configurable via variables. For reference, the accompanying setup script is https://cdn.seedno.de/txt/wireguard-setup. Both scripts require a bit of customization to match your environment (you may want to be particularly careful with the iptables firewall PostUp/PostDown commands), but hopefully they can serve as a starting point to figure out any issues you encountered last time you tried.
[0]: https://www.henrychang.ca/how-to-setup-wireguard-vpn-server-...
It always sends me down a rabbit hole of watching and listening to recordings of people shouting perkele. I always trying to think of a similar word in US English but never can think of anything.
So I looked up the meaning and went on a long ride on the train of distraction.
At first I honestly thought it was some state actor level prank because of how everyone insisted it was impossible to translate.
Most of the sites being sketchy top5 looking sites really played into my suspicion. Or lots of good beer.
Edit: fixed something.
What's missing for me: * a good "connected" indicator * session tracking/logging
Pretty sure I can solve the tracking problem with iptablea or some not very clever network monitoring software.
Wireguard is (sort of) stateless by design, so this would be tough.
> It is not very hard for me to conclude that WireGuard is not ready - yet.
> It has been drafted as a lightweight and fast solution to some problems of the existing solutions. Unfortunately it has sacrificed many features that will be relevant for many users and therefore will not be able to replace IPsec and OpenVPN.
> For that we need to add at least IP address assignment, pushing configuration like DNS servers and routes.
This has certainly been the case for me. My use case for a VPN is a typical road warrior set-up. In my experience Wireguard seems like it's probably great for people who are accustomed to setting up custom VPN configurations already, and in fact probably simplifies the steps in doing so. But as someone who just needs a set-it-and-forget-it configuration to remote in and forward my connections that just consistently works, trying to get Wireguard working was hours of misery.
There's enough tooling built around OpenVPN that you can generate a simple .ovpn configuration that just works and does everything you want in a few minutes. You don't need to be a professional network admin or have a lot of experience configuring VPNs. I hope Wireguard gets to that point because I really do believe in its technical superiority.