[WireGuard] [LEDE-DEV] Kernel symbol dependencies and KCONFIG usage for kernel packages

Baptiste Jonglez baptiste at bitsofnetworks.org
Sat Jul 2 16:55:28 CEST 2016

On Sat, Jul 02, 2016 at 03:48:36PM +0200, Hauke Mehrtens wrote:
> > However, I have some trouble understanding what KCONFIG does.  Wireguard
> > needs a few kernel options, so I thought that KCONFIG was the place to
> > declare such dependencies:
> > 
> >   https://github.com/zorun/packages-1/blob/wireguard/net/wireguard/Makefile#L90
> Instead of activating the kernel symbols you should add a dependency to
> the packages which are building these models:
> DEPENDS:=+kmod-udptunnel4 +kmod-udptunnel6 +kmod-ipt-hashlimit

Well, actually, this is already there, on the next line :)


So, I can remove the KCONFIG line altogether?  I thought the kernel
symbols activated some necessary machinery in the kernel, in addition to
producing the .ko module.

I think I found the cause of the issue: the packages kmod-udptunnel4.ipk
and kmod-udptunnel6.ipk are generated, but are empty (no .ko file).  When
I activate the kernel symbol in kernel_menuconfig, these packages do
provide the .ko files as expected.

I have attached the empty packages to this email, just in case.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: kmod-udptunnel4_4.4.14-1_mips_34kc.ipk
Type: application/vnd.shana.informed.package
Size: 805 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20160702/ec0a2910/attachment-0002.ipk>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kmod-udptunnel6_4.4.14-1_mips_34kc.ipk
Type: application/vnd.shana.informed.package
Size: 806 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20160702/ec0a2910/attachment-0003.ipk>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20160702/ec0a2910/attachment-0001.asc>

More information about the WireGuard mailing list