From: raul <raulbe@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Debian-based configuration for wireguard
Date: Tue, 11 Jul 2017 01:44:15 +0530 [thread overview]
Message-ID: <CAOLRk5=eXFMcrtg6jcr6XyNT1mJiSR0EgrqTURH4SPdHT3ktXQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
>
> On Sun, Jul 09, 2017 at 11:30:20PM +0200, Baptiste Jonglez wrote:
> >* Hi,
> *> >* I wrote up some configuration I use for Wireguard on Debian:
> *> >* https://wiki.debian.org/Wireguard#Configuration_on_Debian <https://wiki.debian.org/Wireguard#Configuration_on_Debian>
> *> >* The goal is to reuse functionalities from /etc/network/interfaces, which
> *>* is quite natural on Debian. Simple use-cases like the point-to-point
> *>* tunnel don't need wg-quick at all.
> *
> Terrific, thanks! Indeed, having nice integration into OSs' native
> configuration interfaces is preferred.
>
> Jason
>
>
Just to offer another POV a utility like wg-quick is very useful when
orchestrating across Linux distributions by offering a standardized
interface to manage Wireguard networks.
It's user friendly and sets up routes automatically depending on the
/etc/wireguard/configuration. In a dynamic changing environment that's
useful to have or you will have to manage the routes manually.
Raul
[-- Attachment #2: Type: text/html, Size: 1311 bytes --]
next reply other threads:[~2017-07-10 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 20:14 raul [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-09 21:30 Baptiste Jonglez
2017-07-09 23:17 ` jomat+wireguard.io
2017-07-10 2:53 ` Jason A. Donenfeld
2017-07-10 19:53 ` Egbert Verhage
2017-07-10 21:20 ` Daniel Kahn Gillmor
2017-07-11 1:59 ` Jason A. Donenfeld
2017-07-11 10:22 ` Egbert Verhage
2017-07-11 13:04 ` jomat+wireguard.io
2017-07-11 22:19 ` Daniel Kahn Gillmor
2017-07-11 22:48 ` Jason A. Donenfeld
2017-07-11 23:12 ` Daniel Kahn Gillmor
2017-07-10 2:51 ` Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOLRk5=eXFMcrtg6jcr6XyNT1mJiSR0EgrqTURH4SPdHT3ktXQ@mail.gmail.com' \
--to=raulbe@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).