Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Emanuele Bernardi <e.berna@posteo.net>
To: wireguard@lists.zx2c4.com
Subject: Re: upgrading raspberry pi required me to re install wireguard
Date: Fri, 22 Feb 2019 13:35:32 +0100	[thread overview]
Message-ID: <62f9f029-605b-f2a5-5388-658233c2a72b@posteo.net> (raw)
In-Reply-To: <9e6f49da-bf09-ab90-dba7-ac5587863a31@pallas.us>


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

I'm very interesting about make it work with dkms, could you please
explain the process? thanks
Emanuele

On 22/02/19 00:29, Derrick Lyndon Pallas wrote:
>
> 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
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard


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

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

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

  parent reply	other threads:[~2019-02-22 12:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 19:47 Arpit Gupta
2019-02-21 12:28 ` logcabin
2019-02-21 13:10   ` sch0rsch
2019-02-21 22:57   ` Arpit Gupta
2019-02-21 23:29     ` Derrick Lyndon Pallas
2019-02-22  0:23       ` logcabin
2019-02-22  0:27         ` Arpit Gupta
2019-02-22 12:35       ` Emanuele Bernardi [this message]
2019-02-22 23:04         ` Mike O'Connor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62f9f029-605b-f2a5-5388-658233c2a72b@posteo.net \
    --to=e.berna@posteo.net \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).