Great. This will mean wonders for the short-term adoption of Wireguard, as it's now in a "stable" Linux distro. After Ubuntu 20.04 there's a big gap in new "stable/enterprise" releases.<p>Debian 11 - Mid 2021, probably<p>OpenSUSE Leap/SLES 16 - Mid 2021, probably<p>Ubuntu 22.04 LTS - April 2022<p>Red Hat 9 - probably 2024 ?<p>So if Ubuntu hadn't included this, we would have to wait more than a year to have it in the kernel of a "server-grade" Linux system by default. Most people don't like running more cutting edge distros or fiddling with the kernel on their servers. Defaults matter, so this will be great for Wireguard adoption.
Wireguard needs to put actual logging into the product before anyone should consider using it in production.<p>I have to deal with it via a vendors product and have spend about 4 weeks in the past 6 months trying to fix a flaky connection by guessing and restarting a lot. Just like anything things will go wrong. But, with wireguard you have no idea what it could even be if it's not an obvious thing that you can diagnose with ping.
Wireguard still has this warning on their site:<p>> WireGuard is currently working toward a stable 1.0 release. Current snapshots are generally versioned "0.0.YYYYMMDD" or "0.0.V", but these should not be considered real releases and they may contain security quirks (which would not be eligible for CVEs, since this is pre-release snapshot software). This text will be removed after a thorough audit.
FTR, <i>WireGuard</i> also available in F-Droid repo for all Android 5.0+ devices.[0]<p>> <i>If your device has a custom kernel containing the WireGuard module, then the module will be used for superior battery life and performance. Otherwise a userspace version will work sufficiently on all other devices.</i><p>[0] <a href="https://apt.izzysoft.de/fdroid/index/apk/com.wireguard.android?repo=main" rel="nofollow">https://apt.izzysoft.de/fdroid/index/apk/com.wireguard.andro...</a>
What’s the best “WireGuard as a VPN configuration” doc out there? Many are not clear about what is being set up, why the cidrs are chosen, how it works without DHCP etc. other guides focus on only proxying rfc1918 traffic and not your entire connection. Is my DNS leaking? Is ALL traffic going through it?<p>OpenVPN, with all of its issues, is simple to set up in a way that’s not leaky.
While I love the product and use it in production, debugging is a royal pain in the ass.<p>There is zero logging to help understand when and how a connection is established (or not) server side.<p>Logging that someone tries to conne ct but wrong key, wrong protocol, whatever - that would help tremendously. Today it is tcpdump or wireshark all the way.
Could someone please explain what a meaningful example usage of WireGuard might be? The intro seems to imply something that could be duplicated with a terminal + SSH forwarding + a VPS. How is this better and/or different?
Thank you :-)