From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Installation instructions for Debian
Date: Sun, 14 May 2017 00:58:37 +0200 [thread overview]
Message-ID: <CAHmME9o=EGWOcTRVtVQVCoJXL6KueX8eM98GWBJUtzEE67tAhw@mail.gmail.com> (raw)
In-Reply-To: <20170513070534.GA22218@tuxmachine.polynome.dn42>
Hey Baptiste,
Spectacular, thanks a bunch. I think I had asked about this same thing
a while back, but somehow I got confused in the ensuing mailing list
thread and eventually I forgot about it. So I'm glad you've brought
this back up. I updated the install page with verbatim what you sent.
Jason
On Sat, May 13, 2017 at 9:05 AM, Baptiste Jonglez
<baptiste@bitsofnetworks.org> wrote:
> Hi Jason,
>
> Could you update the installation instructions for Debian [1]?
>
> Based on the discussion from a few months ago, and given that Wireguard
> now supports Jessie's 3.16 kernel, these instructions should be added:
>
> For Debian jessie or stretch:
> # echo "deb http://deb.debian.org/debian/ unstable main" > /etc/apt/sources.list.d/unstable-wireguard.list
> # cat <<EOF > /etc/apt/preferences.d/limit-unstable
> Package: *
> Pin: release a=unstable
> Pin-Priority: 200
> EOF
> # apt update
> # apt install wireguard-dkms wireguard-tools
>
> I have verified that the resulting setup is functional (with 0.0.20170421-2 on jessie).
>
> Thanks,
> Baptiste
>
> [1] https://www.wireguard.io/install/
--
Jason A. Donenfeld
Deep Space Explorer
fr: +33 6 51 90 82 66
us: +1 513 476 1200
www.jasondonenfeld.com
www.zx2c4.com
zx2c4.com/keys/AB9942E6D4A4CFC3412620A749FC7012A5DE03AE.asc
next prev parent reply other threads:[~2017-05-13 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 7:05 Baptiste Jonglez
2017-05-13 22:58 ` Jason A. Donenfeld [this message]
2017-05-14 8:44 ` Baptiste Jonglez
2017-05-14 12:52 ` Daniel Kahn Gillmor
2017-07-08 14:14 ` Baptiste Jonglez
2017-07-10 0:50 ` Jason A. Donenfeld
2017-07-11 23:36 ` Daniel Kahn Gillmor
2017-07-12 0:00 ` Bzzzz
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='CAHmME9o=EGWOcTRVtVQVCoJXL6KueX8eM98GWBJUtzEE67tAhw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=baptiste@bitsofnetworks.org \
--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).