Development discussion of WireGuard
 help / color / mirror / Atom feed
* Wireguard ceased to work after Fedora 26->27 upgrade
@ 2017-12-01 17:12 Germano Massullo
  2017-12-01 17:27 ` Jason A. Donenfeld
  2017-12-01 17:51 ` Germano Massullo
  0 siblings, 2 replies; 5+ messages in thread
From: Germano Massullo @ 2017-12-01 17:12 UTC (permalink / raw)
  To: joe, WireGuard mailing list

Hi there, some days ago I upgraded my system from Fedora 26 to 27, and
Wireguard ceased to work.


# systemctl status wg-quick@wg0.service
=E2=97=8F wg-quick@wg0.service - WireGuard via wg-quick(8) for wg0
=C2=A0=C2=A0 Loaded: loaded (/usr/lib/systemd/system/wg-quick@.service; e=
nabled;
vendor preset: disabled)
=C2=A0=C2=A0 Active: failed (Result: exit-code) since Fri 2017-12-01 17:5=
5:43 CET;
2min 18s ago
=C2=A0=C2=A0=C2=A0=C2=A0 Docs: man:wg-quick(8)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 man:wg(8)
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 https://www.=
wireguard.com/
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 https://www.=
wireguard.com/quickstart/
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 https://git.=
zx2c4.com/WireGuard/about/src/tools/wg-quick.8
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 https://git.=
zx2c4.com/WireGuard/about/src/tools/wg.8
=C2=A0 Process: 907 ExecStart=3D/usr/bin/wg-quick up wg0 (code=3Dexited,
status=3D1/FAILURE)
=C2=A0Main PID: 907 (code=3Dexited, status=3D1/FAILURE)

dic 01 17:55:43 machine systemd[1]: Starting WireGuard via wg-quick(8)
for wg0...
dic 01 17:55:43 machine wg-quick[907]: [#] ip link add wg0 type wireguard=

dic 01 17:55:43 machine wg-quick[907]: RTNETLINK answers: Operation not
supported
dic 01 17:55:43 machine wg-quick[907]: Unable to get device: Protocol
not supported
dic 01 17:55:43 machine systemd[1]: wg-quick@wg0.service: Main process
exited, code=3Dexited, status=3D1/FAILURE
dic 01 17:55:43 machine systemd[1]: Failed to start WireGuard via
wg-quick(8) for wg0.
dic 01 17:55:43 machine systemd[1]: wg-quick@wg0.service: Unit entered
failed state.
dic 01 17:55:43 machine systemd[1]: wg-quick@wg0.service: Failed with
result 'exit-code'.


# dnf list installed | grep wireguard
wireguard-dkms.noarch=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 1:0.0.20171127-1.fc27=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0
@jdoss-wireguard=C2=A0
wireguard-tools.x86_64=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 1:0.0.20171127-1.fc27=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=

@jdoss-wireguard

# dkms status
returns nothing

kernel packages:
kernel-4.13.16-300.fc27.x86_64
kernel-core-4.13.16-300.fc27.x86_64
kernel-devel-4.13.16-300.fc27.x86_64
kernel-headers-4.13.16-300.fc27.x86_64


Do you have any idea?
Thank you!

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Wireguard ceased to work after Fedora 26->27 upgrade
  2017-12-01 17:12 Wireguard ceased to work after Fedora 26->27 upgrade Germano Massullo
@ 2017-12-01 17:27 ` Jason A. Donenfeld
  2017-12-04 17:54   ` Pim Zandbergen
  2017-12-01 17:51 ` Germano Massullo
  1 sibling, 1 reply; 5+ messages in thread
From: Jason A. Donenfeld @ 2017-12-01 17:27 UTC (permalink / raw)
  To: Germano Massullo; +Cc: WireGuard mailing list

Sounds like dkms isn't kicking in? You might need to remove
wireguard-dkms and reinstall it and see what happens?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Wireguard ceased to work after Fedora 26->27 upgrade
  2017-12-01 17:12 Wireguard ceased to work after Fedora 26->27 upgrade Germano Massullo
  2017-12-01 17:27 ` Jason A. Donenfeld
@ 2017-12-01 17:51 ` Germano Massullo
  1 sibling, 0 replies; 5+ messages in thread
From: Germano Massullo @ 2017-12-01 17:51 UTC (permalink / raw)
  To: WireGuard mailing list

jdoss helped me in #wireguard IRC channel. I post the resolution, it
could be useful for other Fedora users

[18:28] <jdoss> sudo dnf remove wireguard-dkms wireguard-tools; sudo dnf
install wireguard-dkms wireguard-tools
[18:31] <me> jdoss: dnf cannot remove wireguard-dkms, output below

=============
Transazione in corso
  Preparazione in corso                     
:                                                                                                                  
1/1
  Esecuzione scriptlet in corso              :
wireguard-dkms-1:0.0.20171127-1.fc27.noarch                                                                      
1/1
errore: scriptlet %preun(wireguard-dkms-1:0.0.20171127-1.fc27.noarch)
fallita, uscita con stato 3
Error in PREUN scriptlet in rpm package wireguard-dkms
Error in PREUN scriptlet in rpm package wireguard-dkms
wireguard-dkms-1:0.0.20171127-1.fc27.noarch doveva essere eliminato, ma
non lo è stato!
  Verifica in corso                          :
wireguard-dkms-1:0.0.20171127-1.fc27.noarch                                                                      
1/1
 
Non riuscito:
  wireguard-dkms.noarch 1:0.0.20171127-1.fc27
Errore: Transazione non riuscita
=============

[18:32] <jdoss> rpm -qa |grep wireguard
[18:33] <me> jdoss: wireguard-dkms-0.0.20171127-1.fc27.noarch
[18:35] <jdoss> dkms remove -m wireguard -v 0.0.20171127 --all
[18:36] <me> jdoss: Error! There are no instances of module:
wireguard       0.0.20171127 located in the DKMS tree.
[18:37] <jdoss> That's a doozy
[18:37] <me> uh
[18:37] <jdoss> sounds like your dkms went rogue or you removed
wireguard outside of the RPM doing it's job
[18:37] <me> jdoss: no, I have never messed up with that stuff
[18:38] <me> I always used dnf and the copr repo
[18:38] <jdoss> sudo dkms add -m wireguard -v 0.0.20171127
[18:38] <me> jdoss: Creating symlink
/var/lib/dkms/wireguard/0.0.20171127/source ->          
/usr/src/wireguard-0.0.20171127          DKMS: add completed.
[18:39] <jdoss> sudo dkms build -m wireguard -v 0.0.20171127; sudo dkms
install -m wireguard -v 0.0.20171127
[18:40] <jdoss> the upgrade to 27 prob didn't care over well with dkms.
[18:41] <me> jdoss: output below

=============
# dkms build -m wireguard -v 0.0.20171127; dkms install -m wireguard -v
0.0.20171127

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j4 KERNELRELEASE=4.13.16-300.fc27.x86_64 -C
/lib/modules/4.13.16-300.fc27.x86_64/build
M=/var/lib/dkms/wireguard/0.0.20171127/build.......
cleaning build area...

DKMS: build completed.

wireguard:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.13.16-300.fc27.x86_64/extra/
Adding any weak-modules

depmod......

DKMS: install completed.
output below =============

[18:41] <jdoss> dkms status
[18:41] <me> jdoss: wireguard, 0.0.20171127, 4.13.16-300.fc27.x86_64,
x86_64: installed
[18:42] <jdoss> should be good now
[18:42] <me> I suppose that now I have to reinstall the other wireguard
packages
[18:42] <jdoss> yea reinstall wireguard-tools
[18:43] <me> jdoss: yeah, now everything works fine, thank you very much
[18:43] <jdoss> no problem
[18:44] <me> jdoss: I am going to post the resolution to the mailing
list, in case anyone else is affected by the same problem

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Wireguard ceased to work after Fedora 26->27 upgrade
  2017-12-01 17:27 ` Jason A. Donenfeld
@ 2017-12-04 17:54   ` Pim Zandbergen
  2017-12-04 17:55     ` Jason A. Donenfeld
  0 siblings, 1 reply; 5+ messages in thread
From: Pim Zandbergen @ 2017-12-04 17:54 UTC (permalink / raw)
  To: wireguard

I was just about to upgrade my f26 router when I read=C2=A0 about this is=
sue.
As a test, I installed wireguard on a f27 host from scratch. It just work=
ed.
So I suppose, removing before upgrade and installing afterwards should=20
avoid Germano's issue.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Wireguard ceased to work after Fedora 26->27 upgrade
  2017-12-04 17:54   ` Pim Zandbergen
@ 2017-12-04 17:55     ` Jason A. Donenfeld
  0 siblings, 0 replies; 5+ messages in thread
From: Jason A. Donenfeld @ 2017-12-04 17:55 UTC (permalink / raw)
  To: Pim Zandbergen; +Cc: WireGuard mailing list

On Mon, Dec 4, 2017 at 6:54 PM, Pim Zandbergen <pim@zandbergen.org> wrote:
> I was just about to upgrade my f26 router when I read  about this issue.
> As a test, I installed wireguard on a f27 host from scratch. It just worked.
> So I suppose, removing before upgrade and installing afterwards should avoid
> Germano's issue.

Might be worth reporting to Fedora that dkms breaks on release upgrades.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2017-12-04 17:48 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-12-01 17:12 Wireguard ceased to work after Fedora 26->27 upgrade Germano Massullo
2017-12-01 17:27 ` Jason A. Donenfeld
2017-12-04 17:54   ` Pim Zandbergen
2017-12-04 17:55     ` Jason A. Donenfeld
2017-12-01 17:51 ` Germano Massullo

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).