All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Thalheim" <joerg@higgsboson.tk>
To: wireguard@lists.zx2c4.com
Subject: Re: RTNETLINK answers: Operation not supported
Date: Wed, 1 Mar 2017 09:14:40 +0100	[thread overview]
Message-ID: <b0f40ee5-0683-3a59-39b0-dc5b7fef3b12@higgsboson.tk> (raw)
In-Reply-To: <CAPtYZXijvKABYy35SjHTGNrC4fFkP+9xwyUR8RyUOjMB=mB2WQ@mail.gmail.com>


On 2017-02-28 17:08, William Clark wrote:
> Hello,
>
> So I wanted to try WireGuard but unfortunately I can't get pas this part:
> ip link add dev wg0 type wireguard.
>
> When ever I run the command "ip link add dev wg0 type wireguard"
> I get the output:
> RTNETLINK answers: Operation not supported
>
> This both happens on CentOS 7 and Fedora 25 and Ubuntu 16.04.
>
> CentOS 7 Kernel:
> Linux hostname 3.10.0-514.6.2.el7.x86_64 #1 SMP Thu Feb 23 03:04:39 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> Fedora 25 Kernel:
> Linux hostname 4.9.7-x86_64-X #2 SMP Thu Feb 2 15:43:55 EST 2017 x86_64 x86_64 x86_64 GNU/Linux
>
> I've tried installing Linux headers too, but no luck and I've rebooted after the upgrade too, and still no luck.
>
> Thanks a lot.

If the following commands do not succeed, the wireguard kernel module was not installed correctly:

$ modprobe wireguard
$ lsmod | grep wireguard
wireguard             126976  0
x_tables               28672  2 xt_hashlimit,wireguard
ip6_udp_tunnel         16384  1 wireguard
udp_tunnel             16384  1 wireguard
ipv6                  401408  162 nf_conntrack_ipv6,nf_defrag_ipv6,wireguard,bridge

  parent reply	other threads:[~2017-03-01  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28 16:08 RTNETLINK answers: Operation not supported William Clark
2017-02-28 22:21 ` Lucian Cristian
2017-03-01  8:14 ` Jörg Thalheim [this message]
2017-08-05 19:38 Sahil Gupta
2017-08-06 16:30 ` Sahil Gupta
2017-08-06 16:33   ` Sahil Gupta
2017-08-06 16:34     ` Jason A. Donenfeld
2017-08-06 18:31       ` Sahil Gupta
2017-08-06 18:36         ` Jason A. Donenfeld

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=b0f40ee5-0683-3a59-39b0-dc5b7fef3b12@higgsboson.tk \
    --to=joerg@higgsboson.tk \
    --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.