Re: upgrading raspberry pi required me to re install wireguard

From: Derrick Lyndon Pallas <derrick@pallas.us>
To: wireguard@lists.zx2c4.com
Subject: Re: upgrading raspberry pi required me to re install wireguard
Date: Thu, 21 Feb 2019 15:29:02 -0800	[thread overview]
Message-ID: <9e6f49da-bf09-ab90-dba7-ac5587863a31@pallas.us> (raw)
In-Reply-To: <CAGCGytJE5bzXiXB8Go6aHk5OLT0D-m2AnKbRt=Nv1giEVrpsjA@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 2970 bytes --]

I just use DKMS to do it. Check out WireGuard to /usr/src, ln -s 
WireGuard/src WireGuard-0, dkms add WireGuard/0. If it's not auto 
building, have you tried dkms install WireGuard/0? ~D

On 2/21/19 2:57 PM, Arpit Gupta wrote:
> Ya reboot did not solve this for me. I will read up on how I can 
> execute package pre/post install scripts.
>
> Curious to know if the rebuild the module is the responsibility of the 
> os or the package after a kernel upgrade?
>
> I will try to remember this next time there is a kernel upgrade 😁.
>
>
> --
> Arpit
>
> On Thu, Feb 21, 2019, 4:30 AM <logcabin@fastmail.net 
> <mailto:logcabin@fastmail.net>> wrote:
>
>     Yes, the kernel did get updated, causing the wg module
>     dependencies to get out of sync. A reboot after the update should
>     solve this, otherwise you may need to run the package's preinst
>     script to get the modules back in sync. Should be no need to
>     reinstall the wg packages.
>
>     On Thu, Feb 21, 2019, at 2:14 AM, Arpit Gupta wrote:
>>     Hi All
>>
>>     I am running raspberry pi v3 and ran apt-get update and upgrade
>>     commands to get upto date. It also ended up updating the kernel i
>>     think. I should have paid more attention to what all was getting
>>     updated.
>>
>>     After the update wireguard was not running and upon debugging i
>>     found that the wireguard kernel module was no longer present. So
>>     i uninstalled all wireguard packages and installed them again and
>>     the module showed up and on reboot system was back to normal.
>>     What i was curious was how should one go about doing os/kernel
>>     updates in future in order to avoid this issue?
>>
>>     I am running
>>     Linux raspberrypi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT
>>     2019 armv7l GNU/Linux
>>     No LSB modules are available.
>>     Distributor ID:Raspbian
>>     Description:Raspbian GNU/Linux 9.8 (stretch)
>>     Release:9.8
>>     Codename:stretch
>>
>>     ii  wireguard  0.0.20190123-1               all fast, modern,
>>     secure kernel VPN tunnel (metapackage)
>>     ii  wireguard-dkms 0.0.20190123-1               all fast, modern,
>>     secure kernel VPN tunnel (DKMS version)
>>     ii  wireguard-tools  0.0.20190123-1               armhf fast,
>>     modern, secure kernel VPN tunnel (userland utilities)
>>
>>     --
>>     Arpit
>>     _______________________________________________
>>     WireGuard mailing list
>>     WireGuard@lists.zx2c4.com <mailto:WireGuard@lists.zx2c4.com>
>>     https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
>
>     _______________________________________________
>     WireGuard mailing list
>     WireGuard@lists.zx2c4.com <mailto:WireGuard@lists.zx2c4.com>
>     https://lists.zx2c4.com/mailman/listinfo/wireguard
>
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

[-- Attachment #1.2: Type: text/html, Size: 8238 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard