Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Shen Red <darkranger_red@hotmail.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Re: Update wireguard installation instructions for RHEL7/8-Centos8Stream
Date: Tue, 12 Jul 2022 06:31:47 +0000	[thread overview]
Message-ID: <SYBP282MB046024065A5CB3522AC577F4F2869@SYBP282MB0460.AUSP282.PROD.OUTLOOK.COM> (raw)

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

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.

             reply	other threads:[~2022-07-12  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  6:31 Shen Red [this message]
2022-07-13 16:30 ` Faustin Lammler
  -- 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:
  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=SYBP282MB046024065A5CB3522AC577F4F2869@SYBP282MB0460.AUSP282.PROD.OUTLOOK.COM \
    --to=darkranger_red@hotmail.com \
    --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).