($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: "Bas Mevissen" <abuse@basmevissen.nl>
To: "Zunzunegui Abad, Mario-Sergio" <mario.zunzunegui@airbus.com>
Cc: Mario Sergio Zunzunegui Abad <szunzunegui@gmail.com>,
	meta-freescale@lists.yoctoproject.org
Subject: Re: Wireguard recipe
Date: Fri, 26 Feb 2021 15:13:35 +0100	[thread overview]
Message-ID: <c134c20e098a35012afbafb92c42669e@basmevissen.nl> (raw)
In-Reply-To: <95d4b020598e46838a8cc30b019a74f1@CD1-4DDAG04-P02.cdmail.common.airbusds.corp>

On 2021-02-26 15:06, Zunzunegui Abad, Mario-Sergio wrote:
> Airbus Amber
> Hello Bas.
> The result is the same.
> I have added to my
> sources/meta-freescale/recipes-fsl/images/fsl-image-core.bb the
> following IMAGE_INSTALL_append = " \
>     kernel-devsrc \
>     wireguard-tools \
>     wireguard-module \
> "
> 

That looks OK to me.

> kernel-devsrc is for adding kernel headers.
> 
> Exactly the same, I can generate private and public keys with command
> "wg genkey . .. ."
> But when I run "modprobe wireguard" the result is
> modprobe: FATAL: Module wireguard not found.
> 

Please check that the package wireguard-module  (in your Yocto build) 
indeed contains a valid kmod for the kernel you actually run.
If so, check that this kmod is on the target for the kernel you actually 
run. If not, install the package manually.

Maybe it is good to share what you are actually using. Yocto version, 
kernel version, board type etc.

Regards,

Bas.

> 
> I think I am not adding the module properly.
> Any other Idea?
> Thank you very much
> 
> 
> 
> -----Mensaje original-----
> De: Bas Mevissen [mailto:abuse@basmevissen.nl] Enviado el: jueves, 25
> de febrero de 2021 15:18
> Para: Mario Sergio Zunzunegui Abad
> CC: Zunzunegui Abad, Mario-Sergio; 
> meta-freescale@lists.yoctoproject.org
> Asunto: Re: [meta-freescale] Wireguard recipe
> 
> 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
>>>> 
>>>> 
>>> 
>>> 
> The information in this e-mail is confidential. The contents may not
> be disclosed or used by anyone other than the addressee. Access to
> this e-mail by anyone else is unauthorised.
> If you are not the intended recipient, please notify Airbus
> immediately and delete this e-mail.
> Airbus cannot accept any responsibility for the accuracy or
> completeness of this e-mail as it has been sent over public networks.
> If you have any concerns over the content of this message or its
> Accuracy or Integrity, please contact Airbus immediately.
> All outgoing e-mails from Airbus are checked using regularly updated
> virus scanning software but you should take whatever measures you deem
> to be appropriate to ensure that this message and any attachments are
> virus free.

  reply	other threads:[~2021-02-26 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 14:06 Wireguard recipe Zunzunegui Abad, Mario-Sergio
2021-02-26 14:13 ` Bas Mevissen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-02-26 14:27 Zunzunegui Abad, Mario-Sergio
2021-02-26 14:20 Zunzunegui Abad, Mario-Sergio
2021-02-22 15:28 Zunzunegui Abad, Mario-Sergio

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=c134c20e098a35012afbafb92c42669e@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).