9 ms·
I started using Wireguard two days ago to access my home LAN and love it, I can access everything with one command, as if I'm home. The only problem I have with
by StavrosK 8y ago
I started using Wireguard two days ago to access my home LAN and love it, I can access everything with one command, as if I'm home. The only problem I have with it is the complete lack of documentation. The tutorial refers to a configuration file, but nowhere on the site does it tell you how to write one.
It also took me days to set up what I think is a common use case, logging in to a server/router at home and accessing the rest of the computers in the LAN. I I couldn't find how to forward/masquerade traffic, and it took some help from the good people at #linux to get it set up. I think it would be a great help if they had a configuration file on their site detailing how to set that up.
Lacking that, I'll write an article with my config so the info is at least out there, but I believe Wireguard is held back by its lack of documentation.
- ryanlol 8y agoI've been using wg for over a year now and never had any difficulty finding documentation. `man wg` works just fine as does `man wg-quick` https://www.wireguard.com/quickstart/ https://www.wireguard.com/quickstart/ also shows you how to make a config file
- ZoomZoomZoom 8y agoThe problem is that a regular user [some of them] can follow documentation, set up a server and a client, use wg to connect them and may be even ping the connection. That's it, congratulations. How is this connection can be used? Which IPs should be used to establish a useful connection? How can a user see their LAN resources through it? How can a user route his web browsing through this connection (here we at least have wg-quick)? And so on. This information is lacking, and WG documentation is not the sole offender.
- weavie 8y agoThat's the thing with a vpn - it is just a single component of a fully setup network. The vpn documentation generally just covers how to setup the vpn connection. The routing and rest of the network setup, as per the questions you are asking, generally falls out of its domain and into general networks.. which is quite a huge area!
- kazen44 8y agothis is a very good point. Also, from a network design perspective, the difference between a tunnel, GRE interface or VPN is nonexistant. They all accomplish the same objective with different technical methods.
- tssva 8y agoThis is certainly not true. Tunneling and VPN protocols have distinct characteristics and capabilities which greatly affect network design. The reason for this is that they are not all designed to accomplish the same objective.
- Hello71 8y agoOnly if you're using the ridiculous IPsec protocol and its ridiculous modes. Nobody actually needs a mode that authenticates the header but doesn't encrypt it, and nobody can understand this mode anyways. Nobody needs ECB or 3DES or any of the other zillions of IPsec methods. The great thing about WireGuard is that it removes all the crap and has one mode: Fast and Secure.
- tialaramex 8y agoThe slightly dated TLS 1.3 talk from Rescorla talks about this briefly, this is not a situation with easy answers and the approach taken in WG, which is also the approach in TLS 1.3, may yet turn out to be a bad idea. In TLS 1.3 they have left themselves a fire exit they can run out of, hair ablaze, but it's not clear to me whether WG has a way out. From an API point of view, "Fast and secure" sounds pretty good. It maybe infantalizes the Software Engineer, which we're not really ready for yet‡, but we get more ready all the time, so I'll let that go. It's certainly better than "No real security unless you're an expert" which was historically what such APIs tend to offer. On the implementation side "fast and secure" is just a wish, not a fact. Individual elements, picked for being "fast and secure" may turn out not to be as fast as we'd like on tomorrow's hardware, or they may not turn to be as "secure" as we'd have liked. IPsec's Chinese Menu approach lets the software engineer pick something else, but WG's approach doesn't permit this. So, the entire protocol must perhaps be re-designed. ‡ Twenty years ago, we had no good "This just works" answers for a great many things software engineers expect from cryptography. Today we have good answers for many of them, e.g. AEAD modes for block ciphers do roughly what a non-expert software engineer foolishly thought the encryption did anyway. But for others we're still in the dark. Padding for example. For privacy we should pad lengths to hide the true nature of the data being transferred. But... how much should we pad? Today our answer is that hopefully the software engineer using the API knows. In almost all cases they do not.
- throwaway2048 8y agoAfter that point it works exactly like any other network connection. I'm not sure what you feel needs to be documented here.
- pas 8y agoCommon use cases. People will hear about WireGuard the new OpenVPN, and they'll want to "just set up a quick VPN" with it, to "hide their IP address" or whatever. Of course it's up to WG to decide if they want to deal with this kind of community education/outreach.
- deleted 8y ago[deleted]
- ryanlol 8y agoFWIW Openvpn did just fine without doing that.
- alias_neo 8y agoI agree. I've been using Wireguard for about 6 months now. The quick start is great for getting a quick overview but it doesn't really document properly how a configuration file should be made. There is no real detail about how a wg-quick config differs from a wg one, and they're not compatible; it'll complain about unknown keys/values or something if you use a wg-quick config with extra firewall rules and the like with plain wg. I also saw nothing anywhere about how if you modify your config file and down/up with wg-quick it'll delete anything you entered in your config as the 'down' will write back the current state of the interface. It's not a big deal, but it messes with the usual workflow of editing the config file of a service (you don't want to down it while updating your config, which could take time). otherwise, wg has been great, it is generally quite reliable on Android but I'd like to see an easier way of doing the exclusions, inverse CIDRs are not my forte.
- StavrosK 8y ago> it'll complain about unknown keys/values or something if you use a wg-quick config with extra firewall rules and the like with plain wg. Really? I didn't even know that, thanks. > if you modify your config file and down/up with wg-quick it'll delete anything you entered in your config Ouch. Yeah, these things definitely need to be documented, I had no idea about this either. I would also like to see an easier way to configure authentications, having them in the same file as the config means I can't version control it, share it easily, etc.
- alias_neo 8y ago> I would also like to see an easier way to configure authentications Agreed. I like the way home assistant does it with a secrets.yml and you refer to your secrets by !secret <name of secret>
- Hello71 8y ago> I would also like to see an easier way to configure authentications, having them in the same file as the config means I can't version control it, share it easily, etc. The config file is designed to be very straightforward and contain only the bare minimum required configuration stanzas. If you want to separate the keys, or use a higher level key negotiation protocol (e.g. TLS), you can write your own script that calls the lower level "wg" command instead of "wg-quick". Alternatively, you can write a script that generates a wg-quick configuration file.
- louiskottmann 8y agoI actually gave up after trying for a while. They mention an "easy" way to do traditional VPN usage, but it never worked, and various blogs have differing opinions on how to properly do that. I wish there was better hands-on documentation for WG, but I guess it really is an addition to iptables and thus restricted to people versed in that area. Which I am not. I do intend to try again though.
- StavrosK 8y agoHere you go, plug and play: https://www.pastery.net/gvfyub+hacbne/#gvfyub https://www.pastery.net/gvfyub+hacbne/#gvfyub Use with `wg-quick up <configfile.conf>` and you're done. I don't know why this isn't in the documentation, it strikes me as what 99% of users want, and the other 1% knows how to do whatever they need.
- zx2c4 8y agoAdding the masquerade rules and forward rules as an example in the wg-quick(8) man page sounds like a good idea. Want to send a patch to the mailing list?
- StavrosK 8y agoErr, sure, I'll have to figure out how to do that first, though. I'm assuming I can't make a pull request somewhere?
- zx2c4 8y agoIt's even easier than that: $ git commit -s -m "man: add example for bla bla bla" $ git send-email --to=wireguard@lists.zx2c4.com HEAD~ And that's it! This is also, by the way, how submissions to the kernel itself work, so if you're ever interested in doing that and want to get used to the process in a smaller environment, this could be a place to learn.
- StavrosK 8y ago
- deleted 8y ago[deleted]
- Foxboron 8y agoI assume this is what you want? https://wiki.archlinux.org/index.php/WireGuard#Setup_a_VPN_server https://wiki.archlinux.org/index.php/WireGuard#Setup_a_VPN_s...
- tobbyb 8y agoWe have a guide [1] up on using Wireguard and go into some detail on the configuration and how it works. But we mainly use it to build container networks. [1] https://www.flockport.com/guides/build-wireguard-networks.html https://www.flockport.com/guides/build-wireguard-networks.ht...
- eximius 8y agoThe lack of a forum for discussion is also a problem. (Or maybe I'm just spoiled by github.) There is one feature that I want that should be trivial to add that I don't know how to voice it. There is an AllowIPs config directive, but not an ExcludeIPs directive.
- zx2c4 8y agoThere's the mailing list: https://lists.zx2c4.com/mailman/listinfo/wireguard https://lists.zx2c4.com/mailman/listinfo/wireguard And there's the IRC channel: #wireguard on Freenode And in both of these there is quite a bit of discussion. > There is an AllowIPs config directive, but not an ExcludeIPs directive. I think you're mostly just tripped up by the naming here. Everything is excluded by default. Add things to AllowedIPs to have packets sent to those IP get encrypted for that peer.
- eximius 8y agoLike I said, spoiled by github. I need to get back into IRC. Never felt comfortable on mailing lists. I want everything included except my local LAN. I can probably do something stupid to generate a config that works (i.e., such that I manually include 0.0.0.0/8, 1.0.0.0/8, ... etc excluding 192.168.0.0/16) or do something smart outside of wg/wg-quick, but I lack the expertise.
- zx2c4 8y ago> but I believe Wireguard is held back by its lack of documentation. Indeed having good documentation is super important. I'm not so arrogant as to proclaim, "I don't have time to write docs! Understand it yourself!", but I am stretched super thin, and I suspect that often times documentation from somebody who _isn't_ the creator winds up being a bit better, because exterior perspectives are useful. So it's my hope that somebody can chip in and help out writing tutorials and docs and walkthroughs and whatnot. We really do need it. From the sound of your message, though, I wonder if maybe you haven't found the man pages (primary documentation source): https://git.zx2c4.com/WireGuard/about/src/tools/man/wg.8 https://git.zx2c4.com/WireGuard/about/src/tools/man/wg.8 https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick.8 https://git.zx2c4.com/WireGuard/about/src/tools/man/wg-quick...
- StavrosK 8y agoI had, indeed, not found the man pages, thank you. I also intend to write up how to deploy Wireguard with a simple "access the home LAN from the outside" configuration in the next few days, which will hopefully be useful to people.
- lighttower 8y agoPlease do! And can you come back to this thread and let us know?
- deleted 8y ago[deleted]