Re: Wireguard recipe

* Re: Wireguard recipe
@ 2021-02-26 14:27 Zunzunegui Abad, Mario-Sergio
  0 siblings, 0 replies; 5+ messages in thread
From: Zunzunegui Abad, Mario-Sergio @ 2021-02-26 14:27 UTC (permalink / raw)
  To: Bas Mevissen; +Cc: Mario Sergio Zunzunegui Abad, meta-freescale

Airbus Amber
Yes, that also looks good to me, but when I start configuring wireguard, creating /etc/wireguard/wg0.conf, then I try to start the server with "wg-quick up wg0"
And then the system raises an error
RTNETLINK answers: Operation not supported

That is why I have included kernel-devsrc in IMAGE_INSTALL_append.

My assumption is that wireguard-tools is properly installed in the system, but wireguard-module is nor present.

All Ideas are welcomed.
Thank you very much.

-----Mensaje original-----
De: meta-freescale@lists.yoctoproject.org [mailto:meta-freescale@lists.yoctoproject.org] En nombre de Bas Mevissen Enviado el: viernes, 26 de febrero de 2021 15:14
Para: Zunzunegui Abad, Mario-Sergio
CC: Mario Sergio Zunzunegui Abad; meta-freescale@lists.yoctoproject.org
Asunto: Re: [meta-freescale] Wireguard recipe

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.
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.

^ permalink raw reply	[flat|nested] 5+ messages in thread