From: "Bas Mevissen" <abuse@basmevissen.nl>
To: Mario Sergio Zunzunegui Abad <szunzunegui@gmail.com>
Cc: "Zunzunegui Abad, Mario-Sergio" <mario.zunzunegui@airbus.com>,
meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Wireguard recipe
Date: Thu, 25 Feb 2021 15:18:22 +0100 [thread overview]
Message-ID: <2f749831722d9974e7fc537c33fb5d0c@basmevissen.nl> (raw)
In-Reply-To: <CAC7JUO+YqLwioG=r2_s+PwtXnzt=90Q2FkZW1vU9Ca0Cz-MLQQ@mail.gmail.com>
On 2021-02-25 15:12, Mario Sergio Zunzunegui Abad wrote:
> Hello Bas.
> I am afraid I havent realised I had to do that action.
> Could you please tell me how to include this module kmod-wireguard?
> Thank you very much
>
Sorry, got the name wrong. That is how it is called in OpenWRT. :-)
What you need is "wireguard-module" and you can add it to
IMAGE_INSTALL_append like wireguard-tools.
Bas.
> El jue., 25 feb. 2021 15:09, Bas Mevissen <abuse@basmevissen.nl>
> escribió:
>
>> On 2021-02-22 16:28, Zunzunegui Abad, Mario-Sergio wrote:
>>
>>> [Edited Message Follows]
>>>
>>> Hello.
>>>
>>> I am trying to install WireGuard in Yocto.
>>>
>>> I have included the code and recipe and compiled all with bitbake and
>>> generated an image.
>>>
>>> I have added the code provided by NXP in folder
>>> sources/meta-openembedded/meta-networking/recipes-kernel.
>>>
>>> Also added "wireguard-tools" in IMAGE_INSTALL_append in
>>> meta-freescale/recipes-fsl/images/fsl-image-core.bb, then run
>>> "bitbake
>>> fsl-image-core"
>>>
>>> I can generate public and private keys with wg command.
>>>
>>> But when I try to configure WireGuard, it seems that it is not loaded
>>> the module.
>>>
>>> root@vpx3-152:~# modprobe wireguard
>>>
>>> modprobe: FATAL: Module wireguard not found.
>>>
>>> root@vpx3-152:~#
>>>
>>> What I am doing wrong?
>>>
>>
>> Aren't you missing the kmod-wireguard package in your image?
>>
>>> Regards.
>>>
>>> #Yocto-wireguard
>>>
>>>
>>
>>
next prev parent reply other threads:[~2021-02-25 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Groupsio.2.9e195d21fc264317be075273f03cba3a@CD1-4DDAG04-P02.cdmail.common.airbusds.corp>
2021-02-25 14:08 ` [meta-freescale] Wireguard recipe Bas Mevissen
2021-02-25 14:12 ` szunzunegui
2021-02-25 14:18 ` Bas Mevissen [this message]
[not found] <Groupsio.1.9e195d21fc264317be075273f03cba3a@CD1-4DDAG04-P02.cdmail.common.airbusds.corp>
2021-02-26 0:54 ` Christian Betz
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=2f749831722d9974e7fc537c33fb5d0c@basmevissen.nl \
--to=abuse@basmevissen.nl \
--cc=mario.zunzunegui@airbus.com \
--cc=meta-freescale@lists.yoctoproject.org \
--cc=szunzunegui@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).