From: Baptiste Jonglez <baptiste@bitsofnetworks.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: (Unofficial) wireguard packages for Debian Stretch (testing)
Date: Fri, 17 Feb 2017 09:15:32 +0100 [thread overview]
Message-ID: <20170217081532.GA20080@lud.polynome.dn42> (raw)
In-Reply-To: <87y3x5h6vc.fsf@alice.fifthhorseman.net>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
On Thu, Feb 16, 2017 at 09:46:15PM -0500, Daniel Kahn Gillmor wrote:
> On Wed 2017-02-15 16:31:54 -0500, Baptiste Jonglez wrote:
> > On jessie, it worked exactly the same with the 4.9 kernel from
> > jessie-backports:
> >
> > # cat /etc/apt/sources.list
> > deb http://httpredir.debian.org/debian jessie main
> > deb http://httpredir.debian.org/debian jessie-backports main
> > deb http://httpredir.debian.org/debian unstable main
> > # cat /etc/apt/preferences.d/limit-unstable
> > Package: *
> > Pin: release a=unstable
> > Pin-Priority: 200
> > # apt update
> > # apt install -t jessie-backports linux-image-amd64 linux-base
> > # reboot
> > # apt install wireguard-dkms wireguard-tools
> > # ./client.sh
> > # ping 192.168.4.1
> > PING 192.168.4.1 (192.168.4.1) 56(84) bytes of data.
> > 64 bytes from 192.168.4.1: icmp_seq=1 ttl=64 time=15.1 ms
>
> interesting, thanks for testing and reporting back!
>
> are you sure that with this installation on jessie, the wireguard
> packages are the only things that got pulled in from unstable?
Yes, it pulled only dkms and menu (from jessie). Though I probably had
the other dependencies already installed (from jessie or jessie-backports).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-17 8:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 0:23 David Anderson
2017-02-11 9:03 ` Jason A. Donenfeld
2017-02-11 9:49 ` David Anderson
2017-02-11 10:04 ` Jason A. Donenfeld
2017-02-11 10:15 ` David Anderson
2017-02-11 10:17 ` Jason A. Donenfeld
2017-02-11 11:48 ` David Anderson
2017-02-11 13:28 ` Jason A. Donenfeld
2017-02-11 16:27 ` Baptiste Jonglez
2017-02-11 21:38 ` David Anderson
2017-02-11 12:32 ` Jason A. Donenfeld
2017-02-11 21:36 ` David Anderson
2017-02-12 2:40 ` David Anderson
2017-02-12 13:42 ` Jason A. Donenfeld
2017-02-12 23:01 ` Daniel Kahn Gillmor
2017-02-12 23:37 ` Jason A. Donenfeld
2017-02-14 4:55 ` David Anderson
2017-02-14 15:50 ` Daniel Kahn Gillmor
2017-02-15 21:31 ` Baptiste Jonglez
2017-02-17 2:46 ` Daniel Kahn Gillmor
2017-02-17 8:15 ` Baptiste Jonglez [this message]
2017-02-17 13:32 ` Jason A. Donenfeld
2017-02-17 3:14 ` David Anderson
2017-02-17 19:49 ` Daniel Kahn Gillmor
2017-02-20 23:53 ` David Anderson
2017-02-21 0:53 ` Ibrahim Tachijian
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=20170217081532.GA20080@lud.polynome.dn42 \
--to=baptiste@bitsofnetworks.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).