Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: Repo broken?
Date: Sat, 27 May 2017 00:33:02 +0100	[thread overview]
Message-ID: <b632a8f3-987c-3c70-3881-44843f29d5af@york.ac.uk> (raw)
In-Reply-To: <1495832060.1086.1.camel@eggiecode.org>


[-- Attachment #1.1: Type: text/plain, Size: 782 bytes --]

On 26/05/17 21:54, Egbert Verhage wrote:
> Hey Steve,
> 
> That is because in the beging of the ppa repo we only had support for
> kernel >4.1.
> 
> On snapshot: 0.0.20170409 we got support for 3.16, 3.14, 3.12, 3.10.
> And precise has kernel 3.2 (OLD!) and since April 28, 2017 precise is
> eol.

Just to add, the Trusty kernel (3.13) is patched and doesn't build the
modules with DKMS; if you want to run it under Trusty it's possible with
the Xenial backport kernel (4.4). I run this in production (cough) with
a custom package (in one of my PPAs if anyone's interested) and it works
well for me.

I don't expect Wireguard to support that configuration though. :)


> Best way to run wireguard on ubuntu is run xenial or a higher release.

Yup. :)


J


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-05-26 23:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 17:26 Steve Pagan
2017-05-26 17:32 ` Bzzzz
2017-05-26 17:39   ` Steve Pagan
2017-05-26 17:45 ` Jonathon Fernyhough
2017-05-26 17:52   ` Steve Pagan
2017-05-26 18:00     ` Bzzzz
2017-05-26 20:54 ` Egbert Verhage
2017-05-26 23:33   ` Jonathon Fernyhough [this message]

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=b632a8f3-987c-3c70-3881-44843f29d5af@york.ac.uk \
    --to=jonathon.fernyhough@york.ac.uk \
    --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).