Summary: | net-vpn/wireguard-modules: consider checking for NET_FOU instead of NET_UDP_TUNNEL | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | kfm |
Component: | Current packages | Assignee: | Jason A. Donenfeld <zx2c4> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | robin, spiderx |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
kfm
2018-11-25 20:49:27 UTC
Maybe it is because this bug is a bit old now - but the way I see it we could simply strip NET_UDP_TUNNEL (and maybe CRYPTO_ALGAPI as well) from the ebuild. CONFIG_WIREGUARD should select the symbols NET_UDP_TUNNEL and NET_UDP_TUNNEL automatically. I mean it should automatically select NET_UDP_TUNNEL and CRYPTO_ALGAPI according to Kconfig. (In reply to Robin Hallabro-Kokko from comment #1) > Maybe it is because this bug is a bit old now - but the way I see it we > could simply strip NET_UDP_TUNNEL (and maybe CRYPTO_ALGAPI as well) from the > ebuild. > > CONFIG_WIREGUARD should select the symbols NET_UDP_TUNNEL and NET_UDP_TUNNEL > automatically. Indeed, it is more convenient to use >=5.6 but some people might prefer to use a longterm kernel. The 5.4 series will be supported through to the end of 2025. Also, we now have net-vpn/wireguard-modules, so it is valid that the checks continue to be defined there. I think that my request still makes sense but it would obviously need to applied to wireguard-modules at this point. |