From: Mike O'Connor <mike@pineview.net>
To: Emanuele Bernardi <e.berna@posteo.net>, wireguard@lists.zx2c4.com
Subject: Re: upgrading raspberry pi required me to re install wireguard
Date: Sat, 23 Feb 2019 09:34:11 +1030 [thread overview]
Message-ID: <97e86da6-6ebf-e448-8188-5cc053eb5da8@pineview.net> (raw)
In-Reply-To: <62f9f029-605b-f2a5-5388-658233c2a72b@posteo.net>
On 22/2/19 11:05 pm, Emanuele Bernardi wrote:
> 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
>>
The Wireguard source on github has a file in the src directory called
dkms.conf, this when configured using dkms cli tool will automatically
build a new Wireguard kernel module each time the package management
installs a new kernel.
https://help.ubuntu.com/community/DKMS
Cheers
Mike
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-03-01 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 19:47 upgrading raspberry pi required me to re install wireguard 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
2019-02-22 23:04 ` Mike O'Connor [this message]
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=97e86da6-6ebf-e448-8188-5cc053eb5da8@pineview.net \
--to=mike@pineview.net \
--cc=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).