4 ms·

This article is a year old. Certainly Wireguard setup / config has improved this past year, yes?

esotericn 8y ago
Could you clarify "improved"? It's already absolutely fantastic compared to any other solution I can think of (_especially_ OpenVPN, which requires generating a bunch of x.509 certs). This article has a ton of steps which aren't even WireGuard specific like server firewall rules. The actual configuration of WG is basically 'generate a private and public key on server and client, stick it in a config file, run wg-quick up, done'.
- atonse 8y ago
  I don't know, I really like the idea of wireguard but I had a pretty tough time setting it up (and had to give up after an hour)... more like I didn't have the time. I think I wasn't doing something right, though, since I was getting very weird errors that I wasn't able to google. Also I think my issue was like more with the macOS client rather than the server. I think Wireguard is still at the same level that git was about 10 years ago: powerful, elegant, but absolutely not user-friendly. But nobody is claiming that it is (same with git). I suspect in the next couple of years, you'll see an explosion of really nice tools to make this setup even easier than it is now. Until then, I'll keep fiddling and try to get wireguard running on my macOS client/ubuntu server setup.
  - eximius 8y ago
    Give the instructions on this page a try. If that doesn't work, they're very responsive on IRC
  - mbrock 8y ago
    Try putting something like this on your Mac in /usr/local/etc/wireguard/foo.conf: [Interface] PrivateKey = redacted Address = 10.100.0.3/24 [Peer] PublicKey = redacted AllowedIPs = 10.100.0.0/24 Endpoint = 18.xxx.xxx.xxx:51820 PersistentKeepalive = 25 and then doing sudo wg-quick up foo You should see something like INFO: (utun2) 2018/12/16 18:43:24 Starting wireguard-go version 0.0.20181018 [+] Interface for foo is utun2 [#] wg setconf utun2 /dev/fd/63 [#] ifconfig utun2 inet 10.100.0.3/24 10.100.0.3 alias [#] ifconfig utun2 up [#] route -q -n add -inet 10.100.0.0/24 -interface utun2 [+] Backgrounding route monitor That's assuming you have a matching server config set up on your Ubuntu...
  - esotericn 8y ago
    Oh, right. Yeah, the non-Linux clients are all a faff. It's pretty user friendly on Linux. Everywhere else it's alpha level. IMO.
- JustSomeNobody 8y ago
  > Could you clarify "improved"? > It's already absolutely fantastic compared to any other solution... I don’t think that this means there’s no room for improvement.
tosh 8y ago
i found this interactive script useful for setting up (also generates a qr code to import w/ e.g. wireguard on iOS) https://github.com/Fruxlabs/wireguard-roadwarrior https://github.com/Fruxlabs/wireguard-roadwarrior
- tatoalo 8y ago
  I recently used algo[0] and it worked as advertised, pretty seamless. As someone else stated, the config process is pretty standard procedure so I guess there's not a lot of "improvements" one can do on that side :) [0]: https://github.com/trailofbits/algo https://github.com/trailofbits/algo
eximius 8y ago
Most of the steps here are not really configuring Wireguard, they're configuring the host (server or client) to use Wireguard. WireGuard could certainly present those options as a default and automatically do them, but that would be above and beyond what a tool usually does.

Could you clarify "improved"? It's already absolutely fantastic compared to any other solution I can think of (_especially_ OpenVPN, which requires generating a bunch of x.509 certs). This article has a ton of steps which aren't even WireGuard specific like server firewall rules. The actual configuration of WG is basically 'generate a private and public key on server and client, stick it in a config file, run wg-quick up, done'.

atonse 8y ago
I don't know, I really like the idea of wireguard but I had a pretty tough time setting it up (and had to give up after an hour)... more like I didn't have the time. I think I wasn't doing something right, though, since I was getting very weird errors that I wasn't able to google. Also I think my issue was like more with the macOS client rather than the server. I think Wireguard is still at the same level that git was about 10 years ago: powerful, elegant, but absolutely not user-friendly. But nobody is claiming that it is (same with git). I suspect in the next couple of years, you'll see an explosion of really nice tools to make this setup even easier than it is now. Until then, I'll keep fiddling and try to get wireguard running on my macOS client/ubuntu server setup.
- eximius 8y ago
  Give the instructions on this page a try. If that doesn't work, they're very responsive on IRC
- mbrock 8y ago
  Try putting something like this on your Mac in /usr/local/etc/wireguard/foo.conf: [Interface] PrivateKey = redacted Address = 10.100.0.3/24 [Peer] PublicKey = redacted AllowedIPs = 10.100.0.0/24 Endpoint = 18.xxx.xxx.xxx:51820 PersistentKeepalive = 25 and then doing sudo wg-quick up foo You should see something like INFO: (utun2) 2018/12/16 18:43:24 Starting wireguard-go version 0.0.20181018 [+] Interface for foo is utun2 [#] wg setconf utun2 /dev/fd/63 [#] ifconfig utun2 inet 10.100.0.3/24 10.100.0.3 alias [#] ifconfig utun2 up [#] route -q -n add -inet 10.100.0.0/24 -interface utun2 [+] Backgrounding route monitor That's assuming you have a matching server config set up on your Ubuntu...
- esotericn 8y ago
  Oh, right. Yeah, the non-Linux clients are all a faff. It's pretty user friendly on Linux. Everywhere else it's alpha level. IMO.
JustSomeNobody 8y ago
> Could you clarify "improved"? > It's already absolutely fantastic compared to any other solution... I don’t think that this means there’s no room for improvement.

tosh 8y ago

i found this interactive script useful for setting up (also generates a qr code to import w/ e.g. wireguard on iOS) https://github.com/Fruxlabs/wireguard-roadwarrior https://github.com/Fruxlabs/wireguard-roadwarrior

tatoalo 8y ago
I recently used algo[0] and it worked as advertised, pretty seamless. As someone else stated, the config process is pretty standard procedure so I guess there's not a lot of "improvements" one can do on that side :) [0]: https://github.com/trailofbits/algo https://github.com/trailofbits/algo

eximius 8y ago

Most of the steps here are not really configuring Wireguard, they're configuring the host (server or client) to use Wireguard. WireGuard could certainly present those options as a default and automatically do them, but that would be above and beyond what a tool usually does.