From: Stefan Tatschner <rumpelsepp@sevenbyte.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard in systemd-networkd
Date: Fri, 12 Jan 2018 08:40:46 +0100 [thread overview]
Message-ID: <CAB=oiXb4D+KsaY-2muX=wTXu3q22Mtf3dM-ANbBZcvV=WrYW5g@mail.gmail.com> (raw)
In-Reply-To: <87k1wo1pfu.fsf@fifthhorseman.net>
On Thu, Jan 11, 2018 at 2:43 PM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> Hi Stefan--
>
> Matthias was suggesting a simply-named meta-package: just "wireguard",
> which would ensure that both wireguard-dkms and wireguard-tools are
> installed. The advantage there is that you can tell people to do:
>
> apt install wireguard
>
> and apt make sure the system has the common setup by default :)
Awesome! Thanks for clarifying this.
>
>> I just do
>>
>> # ifup wg0
>> # ifdown wg0
>>
>> and it's fine.
>
> i'm glad it works for you, it's always nice to have positive feedback :)
:)
Stefan
>
> happy hacking,
>
> --dkg
next prev parent reply other threads:[~2018-01-12 7:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 13:49 Jason A. Donenfeld
2018-01-09 14:59 ` Matthias Urlichs
2018-01-09 15:20 ` Daniel Kahn Gillmor
2018-01-09 17:38 ` Jason A. Donenfeld
2018-01-10 7:09 ` Daniel Kahn Gillmor
2018-01-10 8:50 ` Matthias Urlichs
2018-01-10 22:30 ` Daniel Kahn Gillmor
2018-01-11 6:37 ` Stefan Tatschner
2018-01-11 13:43 ` Daniel Kahn Gillmor
2018-01-11 15:02 ` Jason A. Donenfeld
2018-01-11 23:38 ` Daniel Kahn Gillmor
2018-01-12 15:50 ` Egbert Verhage
2018-01-12 19:45 ` Jason A. Donenfeld
2018-01-12 7:40 ` Stefan Tatschner [this message]
2018-01-10 8:59 ` Jonathon Fernyhough
2018-01-11 15:00 ` Jason A. Donenfeld
2018-01-09 17:19 ` Germano Massullo
2018-01-13 16:30 ` Some gossip M. Dietrich
2018-01-13 21:25 ` Jason A. Donenfeld
2018-01-30 12:07 ` WireGuard in systemd-networkd Jörg Thalheim
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='CAB=oiXb4D+KsaY-2muX=wTXu3q22Mtf3dM-ANbBZcvV=WrYW5g@mail.gmail.com' \
--to=rumpelsepp@sevenbyte.org \
--cc=dkg@fifthhorseman.net \
--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).