From: Pim Zandbergen <pim@zandbergen.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard on Centos 7
Date: Tue, 16 May 2017 19:12:23 +0200 [thread overview]
Message-ID: <d2094c41-c535-40d1-6c50-dcbe95171df0@zandbergen.org> (raw)
In-Reply-To: <CAHmME9qZB_YPhp2v34uWZJGAve8f4LbA2G_Kbx73ne48o3KGyA@mail.gmail.com>
Hi Jason,
For RHEL/CentOS 7, I suppose would be something like this
# install elrepo repo
sudo rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
sudo yum install
http://www.elrepo.org/elrepo-release-7.0-2.el7.elrepo.noarch.rpm
# install wireguard repo
sudo wget --timestamping --directory-prefix /etc/yum.repos.d
https://copr.fedorainfracloud.org/coprs/jdoss/wireguard/repo/epel-7/jdoss-wireguard-epel-7.repo
# install elrepo mainline kernel and wireguard
sudo yum --enablerepo=elrepo-kernel install kernel-ml kernel-devel
wireguard-dkms wireguard-tools
You might leave out the elrepo stuff and leave that an exercise to the user.
There's an elrepo for RHEL/CentOS 5 and 6 as well, but I can't test that.
Pim
On 05/12/2017 05:31 PM, Jason A. Donenfeld wrote:
> Hey Pim,
>
> That sounds like a good idea to me. I'm not super qualified to write
> the optimal instructions. Think you could come up with a 2 or 3 line
> command blurb for the new RHEL/CentOS section?
>
> Jason
prev parent reply other threads:[~2017-05-16 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 9:36 Christophe Vanlancker
2017-05-12 9:38 ` Jason A. Donenfeld
2017-05-12 9:47 ` Christophe Vanlancker
2017-05-12 13:15 ` Lucian Cristian
2017-05-12 14:46 ` Christophe Vanlancker
2017-05-12 15:00 ` Pim Zandbergen
2017-05-12 15:31 ` Jason A. Donenfeld
2017-05-16 17:12 ` Pim Zandbergen [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=d2094c41-c535-40d1-6c50-dcbe95171df0@zandbergen.org \
--to=pim@zandbergen.org \
--cc=Jason@zx2c4.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).