The Wireguard kernel module is common across linux and some android kernels now and I think it’d be rad to get it in the e/os kernel!
There was a previous post from about 2 years ago here where most people seemed to agree it was a good idea, but nothing seemed to come of it. I can’t see any issues in Gitlab or other posts on the forum.
Wireguard already leads OpenVPN in general performance and simplicity. Adding the protocol to the kernel will theoretically increase the speed even more and give better efficiency (so better battery life) compared to the current userspace implementation.
Let me know what you think!
Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services
4 Likes
afaik the kmod cannot be used unless the app is granted root.
The Wireguard app will still work without it using the Golang userspace implementation.
And if there is a precompiled kernel module it can work without the Golang userspace implementation and even without an app, providing you with a much more reliable connection, especially on the incoming side, noticeably prolonging battery life when under constant load (~2-5 hours on 5AH battery phone), leaving the VPN API accessible for applications that actually need it and all this without forcing you to manually build the module on each new release.
Honestly, i fail to understand why both lineageOS and /e/OS devs are so much against providing out of the box reliable constant two-way VPN connection that practically works only with the module (i use it a lot and can assure you in this). The need to set it as root explains nothing, after all no one is forcing at gunpoint all users to do it.