121–130 of 189 posts
I can foresee a long, long and mostly pointless discussion/argument about code line length.
There's no next message in this thread? Huh? This mail archive works: https://www.spinics.net/lists/netdev/msg516566.html
Why does this need to be included in the kernel directly and not just as a loadable module?
From the patch:
+ tristate "WireGuard secure network tunnel"
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 acces…
Earlier quoted context omitted.
Adding 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?
Err, sure, I'll have to figure out how to do that first, though. I'm assuming I can't make a pull request somewhere?
$ git commit -s -m "man: add example for bla bla bla"
$ git send-email --to=wireguard@lists.zx2c4.com HEAD~
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.
Earlier quoted context omitted.
My understanding (and experience) is that OpenVPN on windows is structurally capped at about 5-10 MB/s. I was curious of how that compares to WireGuard.
Performance issues with OpenVPN on Windows arise out of the inefficiencies of the TUN/TAP driver, not the OpenVPN software itself.
Earlier quoted context omitted.
Err, sure, I'll have to figure out how to do that first, though. I'm assuming I can't make a pull request somewhere?
It'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.
The biggest issue we’ve encountered with WireGuard is that it doesn’t (yet?) support GRO, which means the kernel doesn’t combine multiple sequential TCP frames inside the tunnel into one before presenting it to a program. This increases RTT by a significant amount.
https://git.zx2c4.com/WireGuard/commit/?id=95951af7249912a43...
Earlier quoted context omitted.
> 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 t…
I 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.
Earlier quoted context omitted.
I 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.
Please do! And can you come back to this thread and let us know?