This is great! I love seeing Wireguard spread. I just spent three weeks traveling abroad and installed wireguard on my home server right before I left. It saved me a lot of trouble when I need to get work done "in the US", but even moreso, it was great so that my kids could continue to watch PBS while we traveled, and it was so easy to use on iOs that everyone in the family could make it work for them.
Looks like it's also now available for windows: <a href="https://hn.algolia.com/?query=https:%2F%2Flists.zx2c4.com%2Fpipermail%2Fwireguard%2F2019-May%2F004126.html&sort=byPopularity&prefix&page=0&dateRange=all&type=story" rel="nofollow">https://hn.algolia.com/?query=https:%2F%2Flists.zx2c4.com%2F...</a><p>super exciting. can't wait to see where it goes from here.
The final part of the article mentions this "What is particularly neat is that WireGuard on iOS supports Always-on."<p>I can only agree. I have WG installed on my iPhone, iPad and use the WG service provided by Mullvad VPN. And it is on all the time since a few months back. I don't experience any connectivity issues, lack of performance or degradation in battery/power consumption. It really just works. Huge thanks to Jason for developing WG as protocol, server implementation and clients.
If I have a Wireguard server at home, can I use it on my phone in "always-on" mode? Would it cause problem when I connect to my home's wifi?<p>It's been a while but I tried to do that with ipsec or something like that in the past and I think it was causing problems. With the routing maybe.
FWIW, there is a NetBSD kernel implementation work in progress that might be useful (at least as a starting place) for OpenBSD:<p><a href="https://github.com/ozaki-r/netbsd-src/tree/wireguard" rel="nofollow">https://github.com/ozaki-r/netbsd-src/tree/wireguard</a><p>No activity since March, though.