Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Faustin Lammler <>
To: Shen Red <>
Cc: "" <>
Subject: Re: Update wireguard installation instructions for RHEL7/8-Centos8Stream
Date: Wed, 13 Jul 2022 18:30:00 +0200	[thread overview]
Message-ID: <Ys7zCA9oQH1uiQta@falared> (raw)
In-Reply-To: <SYBP282MB046024065A5CB3522AC577F4F2869@SYBP282MB0460.AUSP282.PROD.OUTLOOK.COM>

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

Hi Shen!

Shen Red <>,
12/07/2022 – 06:31:47 (+0000):

> I think that the wireguard-linux-compat project doesn't officially
> drop CentOS 8 Stream support. The recent commit message just indicates
> that is no longer guaranteed to work, and it doesn't introduce any
> code changes that actually break the compatibility.

My understanding of the commit message and above all of [1] is that the
CI was disabled for C8S and IMO that should be mentioned in the
installation instruction since there is no more guarantee that wireguard
module will install successfully on recent C8S kernel (and that's the
case with 4.18.0-394).

> The recent breakage is caused by a code change in kernel 4.18.0-394
> instead. And that change could also be committed to RHEL8 eventually.

Yes exact.

> There is no proper instruction for C8S for now. The current workaround
> is do not update the kernel to 4.18.0-394. Or, if the kernel has been
> updated, try to build the wireguard module explicitly for the older
> kernel.

This is the kind of thing that I believe should be visible on the
installation instructions, it will save a lot of time to everyone...



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

  reply	other threads:[~2022-07-13 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  6:31 Shen Red
2022-07-13 16:30 ` Faustin Lammler [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-07 17:14 Faustin Lammler

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Ys7zCA9oQH1uiQta@falared \ \ \ \

* 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).