Development discussion of WireGuard
 help / color / mirror / Atom feed
From: adam souzis <adam@souzis.com>
To: wireguard@lists.zx2c4.com
Subject: trouble installing on Fedora and CentOS
Date: Tue, 8 Aug 2017 12:58:58 -0700	[thread overview]
Message-ID: <CAJkVDg1O8SXWtR1cazOMQX6U-sxRVh57MNfTdNGBLpCUdOPnog@mail.gmail.com> (raw)

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

I've been impressed with Wireguard, its design has helped simplify the
implementation of a distributed sandbox app I am building quite a bit. But
I have had mixed results getting it running on different distributions.

The good news is that I can report that I was able to build, install and
run Wireguard on CoreOs.

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.

Here's what I see when install the RPM:

+ dkms add -m wireguard -v 0.0.20170629 -q --rpm_safe_upgrade

+ dkms build -m wireguard -v 0.0.20170629 -q

+ dkms install -m wireguard -v 0.0.20170629 -q

D: %post(wireguard-dkms-1:0.0.20170629-2.fc25.noarch): waitpid(14760) rc
14760 status 100

warning: %post(wireguard-dkms-1:0.0.20170629-2.fc25.noarch) scriptlet
failed, exit status 1

Non-fatal POSTIN scriptlet failure in rpm package wireguard-dkms


Looks like it might have worked:

[fedora@ip-1~]$ sudo dkms status

wireguard, 0.0.20170629: added

BUT:

[fedora@ip-1 ~]$ sudo ip link add dev wg0 type wireguard

RTNETLINK answers: Operation not supported
I tried this on the latest version of the RPM and this earlier version. I
also tried compiling it from source on Fedora but make failed early on.

I disabled selinux, verified the kernel config is good and manually enabled
udp_tunnel for good measure. Any other suggestions? (I did see an earlier
post here recommending using kernel-ml for centos 7 but I need to use the
Atomic Host variant and swapping out the kernel on that is non-trivial. I
was hoping using a recent Fedora would solve the kernel compatibility
issues.)

thank you!
Adam
ᐧ

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

             reply	other threads:[~2017-08-08 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 19:58 adam souzis [this message]
2017-08-08 20:08 ` Bruno Wolff III
2017-08-08 22:49   ` adam souzis
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=CAJkVDg1O8SXWtR1cazOMQX6U-sxRVh57MNfTdNGBLpCUdOPnog@mail.gmail.com \
    --to=adam@souzis.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).