All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Christian Hesse <mail@eworm.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: FAQ and quickstart
Date: Mon, 16 Jan 2017 14:26:45 +0100	[thread overview]
Message-ID: <CAHmME9rS7+kRyWtOwZMtxzmfrk_vqx2+iGFsNTuO8usrpBfOHA@mail.gmail.com> (raw)
In-Reply-To: <7db96582-c381-9149-8e27-967618a40c92@hamburg.freifunk.net>

Hi Christian,

Should the wireguard Arch package depend on linux-headers? Or the dkms
package on linux-headers? Or is it just the Arch-way that dkms merely
prints a warning but doesn't actually have real package deps?

Jason

On Mon, Jan 16, 2017 at 2:23 PM, lennart <lennart@hamburg.freifunk.net> wro=
te:
> Solved it! (Thanks Jason)
> "linux-headers" was not installed.
> "pacman -S linux headers" did the trick.
>
> Thanks all!
>
> On 01/16/2017 02:13 PM, J=C3=B6rg Thalheim wrote:
>> 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_table=
s,iptable_filter,xt_tcpudp,xt_limit,ip6t_REJECT,ip6table_filter,wireguard,x=
t_conntrack,ip6_tables
>> ipv6                  389120  151 nf_conntrack_ipv6,nf_reject_ipv6,nf_de=
frag_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 woul=
d
>>> 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 t=
o
>>> 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
>>
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard



--=20
Jason A. Donenfeld
Deep Space Explorer
fr: +33 6 51 90 82 66
us: +1 513 476 1200
www.jasondonenfeld.com
www.zx2c4.com
zx2c4.com/keys/AB9942E6D4A4CFC3412620A749FC7012A5DE03AE.asc

  reply	other threads:[~2017-01-16 13:16 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
2017-01-16 13:23   ` lennart
2017-01-16 13:26     ` Jason A. Donenfeld [this message]
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=CAHmME9rS7+kRyWtOwZMtxzmfrk_vqx2+iGFsNTuO8usrpBfOHA@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=mail@eworm.de \
    --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.