Arch Linux User Repository

@laenco: Either I'm misunderstanding you or I have to disagree.
When digging though lsmod AFTER HAVING USED WIREGUARD (so I assume all the required modules have been loaded), I can't seem to find any specific modules that are NOT in modprobed.db. It seems to me like the part where .config is configured for the kernel compilation process is assembled in a wrong way, missing out on the loaded (!) modules. This doesn't seem to have anything to do with modprobed-db as far as I can tell (?).

@kwe: so it's look like wireguard needs fou module for dkms build/install, but does not load it during routine operations, so modprobed-db did not detect it.

You could try to add fou and fou6 modules to modprobed.db manually and rebuild.

@laenco: Here is my current system state:

$ grep -i fou ~/.config/modprobed.db
$ lsmod | grep -i fou
$ lsmod | grep -i wire
wireguard             233472  0
ip6_udp_tunnel         16384  1 wireguard
udp_tunnel             16384  1 wireguard
$ grep -i tun ~/.config/modprobed.db
ip6_udp_tunnel
tun
udp_tunnel

When I run makepkg to extract the linux-ck src directory, I end up with this .config diff against the current running kernel config:

$ zdiff /proc/config.gz config.last 
1069d1068
< CONFIG_NET_IP_TUNNEL=m
1077,1078c1076
< CONFIG_NET_UDP_TUNNEL=m
< CONFIG_NET_FOU=m
---
> # CONFIG_NET_FOU is not set
1116d1113
< CONFIG_IPV6_FOU=m

@kwe could you check ~/.config/modprobed.db for presence of "fou"/"fou6" modules?

The question is "If localmodconfig is unable to detect fou or is it a modprobed-db detection problem"?.

@graysky I am building linux-ck with modprobed-db, and for some reason, I always end up with those configuration options being disabled. I have to re-enable them manually every single time.

% uname -r
5.3.8-1-ck

% zgrep CONFIG_NET_FOU /proc/config.gz
CONFIG_NET_FOU=m
CONFIG_NET_FOU_IP_TUNNELS=y

Should be there as a module. Building wireguard-dkms on CK works for me:

# pacman -S wireguard-dkms
resolving dependencies...
looking for conflicting packages...

Packages (2) dkms-2.7.1-1  wireguard-dkms-0.0.20191012-1

Total Download Size:   0.24 MiB
Total Installed Size:  1.75 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 wireguard-dkms-0.0.20191012-1-x86_64            245.7 KiB  3.43 MiB/s 00:00 [############################################] 100%
(2/2) checking keys in keyring                                               [############################################] 100%
(2/2) checking package integrity                                             [############################################] 100%
(2/2) loading package files                                                  [############################################] 100%
(2/2) checking for file conflicts                                            [############################################] 100%
:: Processing package changes...
(1/2) installing dkms                                                        [############################################] 100%
Optional dependencies for dkms
    linux-headers: build modules against the Arch kernel [installed]
    linux-lts-headers: build modules against the LTS kernel
    linux-zen-headers: build modules against the ZEN kernel
    linux-hardened-headers: build modules against the HARDENED kernel
(2/2) installing wireguard-dkms                                              [############################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Install DKMS modules
==> dkms install wireguard/0.0.20191012 -k 5.3.7-arch1-2-ARCH
==> dkms install wireguard/0.0.20191012 -k 5.3.8-1-ck

FWIW, I'm also setting that option manually, hence I'd support @air-g4p's request. Thx again for maintaining this btw !

Cheers !

@graysky - wireguard-dkms failed to build on CK with this output:

http://ix.io/20kT

I asked the devs at #wireguard about this failure, and was told I needed to enable: CONFIG_NET_FOU

(FOU = foo over udp)

After enabling that and rebuilding linux-ck --> Success.

Per Jason's (zx2c4), the lead wireguard dev, suggestion, can you please enable CONFIG_NET_FOU by default on linux-ck?

Thanks graysky

@timo - OK... that is likely because your .config got tweaked due to your CC= line. I opened a flyspray shown below. See it for a solution: https://bugs.archlinux.org/task/64315