All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Doss <joe@solidadmin.com>
To: Silvan Nagl <mail@53c70r.de>, <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard not available for CentOS Stream
Date: Sun, 03 Jan 2021 19:24:17 -0600	[thread overview]
Message-ID: <176cafeade8.27b6.fd5e59abeac6319e4fe4e8192ea7d08d@solidadmin.com> (raw)
In-Reply-To: <a79af0c5-ad54-2b17-964b-9e7891064335@53c70r.de>

https://copr.fedorainfracloud.org/coprs/jdoss/wireguard/

The official DKMS install method for CentOS has a Stream repo enabled. It 
should work fine. Let us know if you have any issues.

Joe

On January 3, 2021 2:19:30 PM Silvan Nagl <mail@53c70r.de> wrote:

> Hi,
>
> i noticed that no Wireguard installation source currently supports
> CentOS Stream and its newer Kernels.
> Will there be support for it?
>
> Greetings,
>
> Silvan




  parent reply	other threads:[~2021-01-04  1:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 20:17 Wireguard not available for CentOS Stream Silvan Nagl
2021-01-03 21:31 ` Silvan Nagl
2021-01-04  1:24 ` Joe Doss [this message]
2021-01-04 12:47   ` Jason A. Donenfeld
     [not found]     ` <CAL0FmdWzknetT9raQcr_BhJwSWSBKPxXZocHSr2TT6bz2QihSA@mail.gmail.com>
2021-01-04 19:42       ` Joe Doss
2021-01-04 20:25         ` Bruno Wolff III
2021-01-04 21:55     ` Jeffrey Walton
2021-01-05 11:25       ` Jonathan Aquilina
2021-01-05 18:35         ` Joe Doss
2021-01-05 18:14       ` Joe Doss
     [not found]       ` <VE1PR08MB5837188C79F58A014916E123A0D10@53c70r.de>
2021-01-06  9:32         ` Silvan Nagl
     [not found]     ` <CAH8yC8n-fC8MJxR7cA+otkqRyDZwhR7wz2Ni+-YTAgiKz7CRHA@53c70r.de>
2021-01-05 13:06       ` Silvan Nagl
2021-01-05 13:56         ` Jeffrey Walton
2021-01-05 14:58           ` Toke Høiland-Jørgensen
2021-01-12  9:57   ` Christopher Ng

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=176cafeade8.27b6.fd5e59abeac6319e4fe4e8192ea7d08d@solidadmin.com \
    --to=joe@solidadmin.com \
    --cc=mail@53c70r.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.