From: "Jörg Thalheim" <joerg@higgsboson.tk>
To: wireguard@lists.zx2c4.com
Subject: Re: FAQ and quickstart
Date: Mon, 16 Jan 2017 14:13:42 +0100 [thread overview]
Message-ID: <a24740cf-1d98-8e63-1b20-1424fcb45724@higgsboson.tk> (raw)
In-Reply-To: <af514aab-0c3a-1a10-17a8-4a538464651f@hamburg.freifunk.net>
The kernel module is most likely not loaded.
Make sure the following command returns something.
$ lsmod | grep wireguard
wireguard 126976 0
ip6_udp_tunnel 16384 1 wireguard
udp_tunnel 16384 1 wireguard
x_tables 28672 12 xt_hashlimit,xt_LOG,ipt_REJECT,ip_tables,iptable_filter,xt_tcpudp,xt_limit,ip6t_REJECT,ip6table_filter,wireguard,xt_conntrack,ip6_tables
ipv6 389120 151 nf_conntrack_ipv6,nf_reject_ipv6,nf_defrag_ipv6,wireguard,nf_nat_ipv6
Since you are on archlinux, did you reboot after kernel upgrade?
On 2017-01-16 12:31, lennart wrote:
> Hi,
>
> I'm trying to wireguard via the quickstart [0].
> But I get this error:
> $ sudo ip link add dev wg0 type wireguard
> RTNETLINK answers: Operation not supported
>
> I know it has something to do with kernel configurations, but that would
> be a whole new topic to me.
> What do I need to do? Isn't this a good question for a FAQ?
>
> I'm on a archlinux:
> $ uname -r
> 4.8.13-1-ARCH
>
> Second:
> How can a search the hole list archive? I'm just used to an interface to
> do that.
>
> [0] https://www.wireguard.io/quickstart/
>
> Thanks a lot!
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2017-01-16 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 11:31 FAQ and quickstart lennart
2017-01-16 11:32 ` Jason A. Donenfeld
2017-01-16 13:13 ` Jörg Thalheim [this message]
2017-01-16 13:23 ` lennart
2017-01-16 13:26 ` Jason A. Donenfeld
2017-01-16 13:33 ` Christian Hesse
2017-01-16 13:34 ` 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=a24740cf-1d98-8e63-1b20-1424fcb45724@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.