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: Wed, 15 Feb 2017 22:31:54 +0100 [thread overview]
Message-ID: <20170215213153.GC16102@tuxmachine.polynome.dn42> (raw)
In-Reply-To: <87o9y4n555.fsf@alice.fifthhorseman.net>
[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]
On Tue, Feb 14, 2017 at 10:50:14AM -0500, Daniel Kahn Gillmor wrote:
> on a similar system i'm using (stretch, with unstable available but
> pinned low), i see only packages from stretch being installed (aside
> from wireguard itself, clearly)
>
> 0 root@test:~# cat /etc/apt/sources.list.d/unstable.list
> deb http://ftp.us.debian.org/debian/ unstable main
> 0 root@test:~# cat /etc/apt/preferences.d/limit-unstable
> Package: *
> Pin: release a=unstable
> Pin-Priority: 200
Thanks for the hint, it worked fine on my stretch system! Here are the
packages that got pulled:
The following NEW packages will be installed:
dkms linux-compiler-gcc-6-x86 linux-headers-4.9.0-1-amd64
linux-headers-4.9.0-1-common linux-headers-amd64 linux-kbuild-4.9
wireguard-dkms wireguard-tools
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
For the record, it also works fine with the 4.1.34.mptcp kernel from
multipath-tcp.org on jessie :)
Jason, can you write something up on the Wireguard website, since it's so
simple?
Baptiste
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-15 21:31 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 [this message]
2017-02-17 2:46 ` Daniel Kahn Gillmor
2017-02-17 8:15 ` Baptiste Jonglez
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=20170215213153.GC16102@tuxmachine.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).