From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Pim Zandbergen <pim@zandbergen.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard ceased to work after Fedora 26->27 upgrade
Date: Mon, 4 Dec 2017 18:55:02 +0100 [thread overview]
Message-ID: <CAHmME9ouCkbigR=5TCMPQBoNp-uT8PhmjHBiTs2XbmyJo0CSfA@mail.gmail.com> (raw)
In-Reply-To: <34ce36c3-38fe-96fe-4b2d-22a819272a8d@zandbergen.org>
On Mon, Dec 4, 2017 at 6:54 PM, Pim Zandbergen <pim@zandbergen.org> wrote:
> I was just about to upgrade my f26 router when I read about this issue.
> As a test, I installed wireguard on a f27 host from scratch. It just worked.
> So I suppose, removing before upgrade and installing afterwards should avoid
> Germano's issue.
Might be worth reporting to Fedora that dkms breaks on release upgrades.
next prev parent reply other threads:[~2017-12-04 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 17:12 Germano Massullo
2017-12-01 17:27 ` Jason A. Donenfeld
2017-12-04 17:54 ` Pim Zandbergen
2017-12-04 17:55 ` Jason A. Donenfeld [this message]
2017-12-01 17:51 ` Germano Massullo
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='CAHmME9ouCkbigR=5TCMPQBoNp-uT8PhmjHBiTs2XbmyJo0CSfA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=pim@zandbergen.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).