Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Baptiste Jonglez <baptiste@bitsofnetworks.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: (Unofficial) wireguard packages for Debian Stretch (testing)
Date: Thu, 16 Feb 2017 21:46:15 -0500	[thread overview]
Message-ID: <87y3x5h6vc.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <20170215213153.GC16102@tuxmachine.polynome.dn42>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Hi Baptiste--

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?

If you have apt-show-versions installed, you might try grepping through
its output to make sure.

Regards,

       --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-02-17  2:48 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 [this message]
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=87y3x5h6vc.fsf@alice.fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --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).