Hacker News Reader

Comment by curiousgal | Hacker News Reader

I gave up on getting Wireguard to work on an Arch server and an Android client. Algo only supports Ubuntu and *BSD.

> Algo only supports Ubuntu and *BSD.

Algo, also called Algo VPN, is a separate project which is built on-top of Wireguard [0]. Algo claims to support Android [1].

Wireguard works on Arch and Android [2]. Wireguard for Arch has first class support [3]. Wireguard for Android exists in a forked repository [4].

[0] https://github.com/trailofbits/algo

[1] https://github.com/trailofbits/algo/blob/master/docs/client-...

[2] https://www.wireguard.com/install/

[3] https://wiki.archlinux.org/index.php/WireGuard

[4] https://git.zx2c4.com/wireguard-android

I use it on Arch with no issues at all.

Same. I've also set up WireGuard on Ububtu servers and the experience was pretty much identical. Arch doesn't make this any harder.

Works fine for me on Manjaro using wireguard-dkms and the Wireguard app from the F-Droid store.

Copying public keys back and forth via email seemed a bit of a faff so there's probably a better way. Possibly using `qrencode` would let you set up the client configuration...

Perhaps I am misunderstanding the premise of Wireguard as all the tutorials seem to be setting up a client and a server that are on the same network, is not possible to have the server as a VPS and have the client connect via the Internet?

It is really no difference between setting up Wireguard on a local network or via Internet as long as one of the hosts can listen to a public UDP port. If one of your clients are behind a NAT you may need to enable the keep alive option in the client's config

My client is indeed behind a NAT. I'll just wait until Wireguard is more mainstream and extremely detailed guides are up.

Admittedly, I haven't gotten around to actually using WireGuard yet, but I think it's pretty much as simple as Linuskendall said. https://www.wireguard.com/quickstart/#nat-and-firewall-trave...

Also see this guide on using a public VPS with a Wireguard server to share resources behind two different NAT'd networks: https://staaldraad.github.io/2017/04/17/nat-to-nat-with-wire...

Sadly some public networks I had to use were blocking Wireguard, while my IPSec VPN would easily go through each time :(

I wish there was an option to obfuscate the traffic as a plain HTTPS connection, but that would defeat the idea of keeping Wireguard simple.

Reply on news.ycombinator.com