Development discussion of WireGuard
 help / color / mirror / Atom feed
From: adam souzis <adam@souzis.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: wireguard@lists.zx2c4.com
Subject: Re: trouble installing on Fedora and CentOS
Date: Tue, 8 Aug 2017 15:49:29 -0700	[thread overview]
Message-ID: <CAJkVDg00xN6YzKTYhPeHC6uJ6KR+bHfPfxznfpa3+8Ma4R9SXg@mail.gmail.com> (raw)
In-Reply-To: <20170808200811.GB7930@wolff.to>

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

OK, you inspired me to try harder to build it from source -- turns out on
both fedora 25 and 26 `uname -r` doesn't match the kernel src installed by
kernel-devel, once I fixed that it builds and installs and appears to work.

thanks!
Adam
ᐧ

On Tue, Aug 8, 2017 at 1:08 PM, Bruno Wolff III <bruno@wolff.to> wrote:

> On Tue, Aug 08, 2017 at 12:58:58 -0700,
>  adam souzis <adam@souzis.com> wrote:
>
>>
>> The bad news is I was unable to get Wireguard working on either CentOS 7,
>> Fedora 26 or Fedora 25 (running these on AWS), it doesn't appear to be
>> installing the kernel module properly.
>>
>
> I run it on rawhide (Fedora 27 effectivel) by building from source.
>
> I have a local clone of the git repo and do the following:
> cd WireGuard/src
> make clean all
> su
> make install
>
> That installs the kernel module in the running kernel. You'll need
> kernel-devel installed and maybe kernel-headers. If you are updating the
> module, you will want to stop wireguard and use rmmod wireguard to remove
> the existing module, so the new one will get loaded (or reboot the system).
>

[-- Attachment #2: Type: text/html, Size: 1955 bytes --]

  reply	other threads:[~2017-08-08 22:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 19:58 adam souzis
2017-08-08 20:08 ` Bruno Wolff III
2017-08-08 22:49   ` adam souzis [this message]
2017-08-08 23:21 ` Jason A. Donenfeld
2017-08-09  1:51 ` Joe Doss
2017-08-09 12:39   ` adam souzis
2017-08-09 14:54     ` Joe Doss

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=CAJkVDg00xN6YzKTYhPeHC6uJ6KR+bHfPfxznfpa3+8Ma4R9SXg@mail.gmail.com \
    --to=adam@souzis.com \
    --cc=bruno@wolff.to \
    --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).