I'd like a tutorial on getting wireguard running with systemd for debian/ubuntu based systems!
Wireguard-docs: Setup, usage, configuration, and a full example
91–96 of 96 posts
Re: Wireguard-docs: Setup, usage, configuration, and a full example
#92Can wireguard be run in docker?
I added a section with some more resources on containerization:
Re: Wireguard-docs: Setup, usage, configuration, and a full example
#93That's awesome!
My suggestions:
* I'd include this research paper. It's the "first mechanised cryptographic proof of WG protocol" : https://hal.inria.fr/hal-02100345/document
Self-plug right here. There are a ton of bash scripts to install and configure WireGuard. Here's mine: https://github.com/SirToffski/WireGuard-Ligase/
It will configure server and clients independent of the OS it's running at. Steps to install WG are provided in the Wiki. On Ubuntu server with pre-installed WG, the quick setup option will make a ready to use server. You can quickly edit the variables to change things up.
Cheers!
Re: Wireguard-docs: Setup, usage, configuration, and a full example
#94Goddamn it, this happens literally every time I post my projects to HN :( I posted the link myself to my repo, 0 points 14 hours later someone else posts it: 260+ points No hate towards you axiomdata316, thanks for posting it, I'm just childishly complaining about the unfairness of fake internet points :p
Lol. I know what you mean. Congrats on all the attention you're getting however. BTW I went to your original post and gave you a point. ;-)
If anyone else wants to... https://news.ycombinator.com/item?id=20031254
Re: Wireguard-docs: Setup, usage, configuration, and a full example
#95>IPSec (IKEv2)/strongSwan: lots of brittle config that's different for each OS, NAT busting setup is very manual and involves updating the central server and starting all the others in the correct order, not great at reconnecting after network downtime, had to be manually restarted often I don't follow, NAT traversal is integral to IKEv2 and pretty much "just works" [1]. Reconnecting after network downtime is not an…
I ran IKEv2 2-3 VPNs for multiple years with a few dozen users, I have to say from experience I disagree with you there (I'm the author of the repo, @pirate). For various reasons, StrongSwan required manual intervention much more frequently than WireGuard has for far. Often I'd have to manually restart the service, or adding a new host would break stuff for all the others. The minimal config required to match my curr…
Initial setup for IKEv2 is convoluted at best, but once it’s setup there are very few problems with it.
I (used to) run L2TP/IPSec and WireGuard on my Edgerouter 4, and both would give “acceptable” speeds (30-40 MBit on a 300/300 connection), but when recreating my firewall in PfSense, I went full IKEv2, and have not regretted it. With my SG-3100 I get ~100 MBit with IKEv2.
On thing I hated about WireGuard is the fact that all clients require configuration on the server.
I do still run it on one of my servers, as a client to Mullvad VPN, which in turn is used by a few docker containers. It could easily be replaced by IKEv2, but sadly most VPN providers only support OpenVPN and WireGuard, or have horrible speeds.
Re: Wireguard-docs: Setup, usage, configuration, and a full example
#96Earlier quoted context omitted.
2: eth0: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 inet 192.168.101.12/24 brd 192.168.101.255 scope global eth0 valid_lft forever preferred_lft forever inet 192.168.1.25/32 scope global eth0 valid_lft forever preferred_lft forever inet 192.168.1.32/31 scope global eth0 valid_lft forever preferred_lft forever Seems to work fine, added a /31 just for fun.
if you remove the /24 you'll have a nice surprise
Not really a surprise. The point is that it is a completely valid address to use, and in this case it just defines a range. /32 are commonly used in routers (even servers in some cases) and /31 for linknets.