From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, HTML_MESSAGE,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 30695C43381 for ; Fri, 22 Feb 2019 00:23:51 +0000 (UTC) Received: from krantz.zx2c4.com (krantz.zx2c4.com [192.95.5.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4D57E2080F for ; Fri, 22 Feb 2019 00:23:49 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=fastmail.net header.i=@fastmail.net header.b="h4TZidt+"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=messagingengine.com header.i=@messagingengine.com header.b="tfw2RwxZ" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4D57E2080F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=fastmail.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=wireguard-bounces@lists.zx2c4.com Received: from krantz.zx2c4.com (localhost [IPv6:::1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 1c7667b8; Fri, 22 Feb 2019 00:14:41 +0000 (UTC) Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 27620ccb for ; Fri, 22 Feb 2019 00:14:39 +0000 (UTC) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 15f8a37d for ; Fri, 22 Feb 2019 00:14:39 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5037B22081 for ; Thu, 21 Feb 2019 19:23:30 -0500 (EST) Received: from imap6 ([10.202.2.56]) by compute4.internal (MEProxy); Thu, 21 Feb 2019 19:23:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.net; h= message-id:in-reply-to:references:date:from:to:subject :content-type; s=fm2; bh=GIDV/4X1h3mxCRXfapXEu4ts9u6RxGgCPrtWnOZ vDdg=; b=h4TZidt+f982OGWtI/dd5imPhdGlZOk8ubdNrJgx6gopnmCHAp+Ngej lH09qJ59THkWIKTFpGqpOo/pcp8VMgTSopy0sljaBExoKADcKWiLeUAoWXGw02eN /Ep9qBNBj485WLEutsphf+o3879zeXB5VjFv58rwRfFPpRk9Ye2PjCdEdA6HufP5 4O0C679mmm0WMzbNrFFvkpI2L+lIGq+Fw08GBjA46DOXCFUPj+l3dTMBz5dhVNK6 QTrBfcOZu+qkP080lacuPXS43uLoQT3DmFhJNUx2EsySzuQ9Usl5NPZFqhXbsgdC RZlKYmgXpaYDBUdhCvyGVcNS5qhL8eg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=GIDV/4X1h3mxCRXfa pXEu4ts9u6RxGgCPrtWnOZvDdg=; b=tfw2RwxZ3OHjHoPYHk4yMhvSYiaqkJ9aC JJ0Co3opc14N4Dn5f/5WHWuXOr16qjQJIJI3xYK0OT0woTieKcZpsBKIfPqljWEW nRx+rbKzVGoUols+WMXVwb6VJOU8u2QUii8vGViKi928OSEo39moo3tVhnPVXlCU iCKcsMz7f5Q0719JCivbRLGDrIwrPutmwIC709fdGaXOqHi1mq7UQj9FpXqqB8UL P2uEvWPBhQ98hfki7b1w8ZmDIeFhlvxgib9F3xcUi0l/qIvoSGubzYiPxixByZpw K6fkX7OIE95Ml9dkeLY8kySnYE5AI05YWizR+arjyhOHIRfNDe/Xg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrtdelgddvtdculddtuddrgedtledrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomheplhhoghgtrggsihhnsehfrghsthhmrghilhdrnhgvthenucff ohhmrghinhepiiigvdgtgedrtghomhenucfrrghrrghmpehmrghilhhfrhhomheplhhogh gtrggsihhnsehfrghsthhmrghilhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id CC28182678; Thu, 21 Feb 2019 19:23:29 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.5-895-g0d23ba6-fmstable-20190213v1 X-Me-Personality: 15697833 Message-Id: In-Reply-To: <9e6f49da-bf09-ab90-dba7-ac5587863a31@pallas.us> References: <9e6f49da-bf09-ab90-dba7-ac5587863a31@pallas.us> Date: Thu, 21 Feb 2019 19:23:29 -0500 From: logcabin@fastmail.net To: wireguard@lists.zx2c4.com Subject: Re: upgrading raspberry pi required me to re install wireguard X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.15 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0444523939657318413==" Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" --===============0444523939657318413== Content-Type: multipart/alternative; boundary=29e98e42171e4d35b93863803fd4efdb --29e98e42171e4d35b93863803fd4efdb Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable If you want to build/install wg from source, you can do what I do (autom= ation is easy): Download the source xz file and unpack it using xzcat and tar. Navigate = to the src directory and build the module and tools using the "make" com= mand. Then use "sudo make install" to get the wg .ko file replaced with = the latest one and install any updates to the tools and wg executable. I= f you do this after a kernel upgrade, you'll need to reboot the pi befor= e you install the wg kernel module, otherwise it won't find the right ke= rnel headers.=20 A simple shell script can be made to do all this stuff for you.=20 On Thu, Feb 21, 2019, at 6:30 PM, Derrick Lyndon Pallas wrote: > I just use DKMS to do it. Check out WireGuard to /usr/src, ln -s WireG= uard/src WireGuard-0, dkms add WireGuard/0. If it's not auto building, h= ave you tried dkms install WireGuard/0? ~D >=20 > 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 exec= ute package pre/post install scripts.=20 >>=20 >> Curious to know if the rebuild the module is the responsibility of th= e os or the package after a kernel upgrade? >>=20 >> I will try to remember this next time there is a kernel upgrade =F0=9F= =98=81. >> =20 >> =20 >>=20 >> -- >> Arpit >>=20 >> On Thu, Feb 21, 2019, 4:30 AM 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, otherwi= se you may need to run the package's preinst script to get the modules b= ack in sync. Should be no need to reinstall the wg packages. >>>=20 >>> On Thu, Feb 21, 2019, at 2:14 AM, Arpit Gupta wrote: >>>> Hi All >>>>=20 >>>> I am running raspberry pi v3 and ran apt-get update and upgrade com= mands 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. >>>>=20 >>>> After the update wireguard was not running and upon debugging i fou= nd that the wireguard kernel module was no longer present. So i uninstal= led all wireguard packages and installed them again and the module showe= d 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? >>>>=20 >>>> I am running >>>> Linux raspberrypi 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27:48 GMT 201= 9 armv7l GNU/Linux >>>> No LSB modules are available. >>>> Distributor ID: Raspbian >>>> Description: Raspbian GNU/Linux 9.8 (stretch) >>>> Release: 9.8 >>>> Codename: stretch >>>>=20 >>>> ii wireguard 0.0.20190123-1 all fast, modern, secure kernel VPN tun= nel (metapackage) >>>> ii wireguard-dkms 0.0.20190123-1 all fast, modern, secure kernel VP= N tunnel (DKMS version) >>>> ii wireguard-tools 0.0.20190123-1 armhf fast, modern, secure kernel= VPN tunnel (userland utilities) >>>>=20 >>>> -- >>>> Arpit >>>> _______________________________________________ >>>> WireGuard mailing list >>>> WireGuard@lists.zx2c4.com >>>> https://lists.zx2c4.com/mailman/listinfo/wireguard >>>>=20 >>>=20 >>> _______________________________________________ >>> WireGuard mailing list >>> WireGuard@lists.zx2c4.com >>> https://lists.zx2c4.com/mailman/listinfo/wireguard >>=20 >> _______________________________________________ WireGuard mailing list >> WireGuard@lists.zx2c4.com >> https://lists.zx2c4.com/mailman/listinfo/wireguard >>=20 > _______________________________________________ > WireGuard mailing list > WireGuard@lists.zx2c4.com > https://lists.zx2c4.com/mailman/listinfo/wireguard >=20 --29e98e42171e4d35b93863803fd4efdb Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable
If you want to build/install wg from source, you can do wh= at I do (automation is easy):

Download the source xz file= and unpack it using xzcat and tar.  Navigate to the src directory = and build the module and tools using the "make" command. Then use "sudo = make install" to get the wg .ko file replaced with the latest one and in= stall any updates to the tools and wg executable. If you do this after a= kernel upgrade, you'll need to reboot the pi before you install the wg = kernel module, otherwise it won't find the right kernel headers.

A simple shell script can be made to do all this stuff for you.=

On Thu, Feb 21, 2019, at 6:30 PM, Derrick Lyndon Pallas= wrote:

I j= ust 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 thi= s 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 tim= e there is a kernel upgrade =F0=9F=98=81.



--
Arpit

On Thu, Feb 21, 2019, 4:30 AM <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 rasp= berry 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.

Af= ter 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 ru= nning
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
Des= cription: Raspbian GNU/Linux 9.8 (stretch)
Release:= 9.8
Codename= : stretch
ii  wireguard          &n= bsp;            0.0.20190123-1      &nb= sp;        all          fast, modern, secure kernel VPN tunnel (metapackage)
ii  wiregua= rd-dkms                  0.0.20190123-1        &n= bsp;      all          fast, modern, secure kernel VPN tunnel (DKMS= version)
ii  wireguard-to= ols                 0.0.20190123-1      &nb= sp;        armhf        fast, modern, secure kernel VPN tunnel (userland utilities)
--
<= div style=3D"font-family:Arial;">Arpit
=
___________________________________________= ____
WireGuard mailing list


__________= _____________________________________
WireGuard mailing list
<= a rel=3D"noreferrer noreferrer" href=3D"https://lists.zx2c4.com/mailman/= listinfo/wireguard">https://lists.zx2c4.com/mailman/listinfo/wireguard

______________=
_________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/l=
istinfo/wireguard
____________________________________________= ___
WireGuard mailing list
WireGuard@lists.z= x2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguar= d


--29e98e42171e4d35b93863803fd4efdb-- --===============0444523939657318413== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard --===============0444523939657318413==--