Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Riccardo Berto <riccardo@rcrdbrt.com>
To: Roman Mamedov <rm@romanrm.net>
Cc: wireguard@lists.zx2c4.com
Subject: Re: [Uber low priority] Linux 4.17.0 on aarch64
Date: Thu, 07 Jun 2018 11:26:32 +0200	[thread overview]
Message-ID: <f324276874bdee86aea4518e16ca34f3@rcrdbrt.com> (raw)
In-Reply-To: <20180607132126.1ceafbfe@natsu>

On 2018-06-07 10:21, Roman Mamedov wrote:
> On Thu, 07 Jun 2018 09:40:08 +0200
> Riccardo Berto <riccardo@rcrdbrt.com> wrote:
> 
>> Just want to report that I can't add a wg interface of type wireguard
>> with linux 4.17.0 on aarch64 (Raspberry Pi 3).
>> 
>> Error message: `RTNETLINK answers: Operation not supported`.
>> 
>> I'm using ArchLinuxARM. Downgrading to 4.16.x makes the issue 
>> dissapear.
>> This is not high-priority so please Jason, if you're reading this
>> message, move this issue further down in your debugging queue as I
>> believe almost nobody is using 4.17.0 on aarch64 right now. Maybe
>> they'll fix the error by themselves in the coming 4.17.x releases.
> 
> Did you actually compile the wireguard kernel module? Or rely on 
> mysterious
> "them" to do so?

I compiled it through a dkms hook of pacman, the ArchLinuxARM pkg 
manager. It runs everytime there is a new kernel installation, being it 
an upgrade or a downgrade.

Those mysterious and shady "them" are the mainline patch submitters LOL

  reply	other threads:[~2018-06-07  9:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07  7:40 Riccardo Berto
2018-06-07  8:21 ` Roman Mamedov
2018-06-07  9:26   ` Riccardo Berto [this message]
2018-06-07 13:06 ` Jaron Kent-Dobias

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=f324276874bdee86aea4518e16ca34f3@rcrdbrt.com \
    --to=riccardo@rcrdbrt.com \
    --cc=rm@romanrm.net \
    --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).