Weil wireguard mit dem heute gekommenen Kernel f\u00fcr Ubuntu 18.04 nicht durch den Compiler ging<\/p>\n
Unpacking wireguard-dkms (1.0.20200520-0ppa1~18.04) over (1.0.20200520-0ppa1~18.04) ...\r\nSetting up wireguard-dkms (1.0.20200520-0ppa1~18.04) ...\r\nLoading new wireguard-1.0.20200520 DKMS files...\r\nBuilding for 4.15.0-106-generic\r\nBuilding initial module for 4.15.0-106-generic\r\nError! Bad return status for module build on kernel: 4.15.0-106-generic (x86_64)\r\nConsult \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/make.log for more information.\r\nSetting up wireguard (1.0.20200513-1~18.04) ...<\/pre>\nund dann in \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/make.log<\/em> Derartiges hinterlie\u00df<\/p>\n
DKMS make.log for wireguard-1.0.20200520 for kernel 4.15.0-106-generic (x86_64)\r\nWed Jun 10 07:49:21 CEST 2020\r\nmake: Entering directory '\/usr\/src\/linux-headers-4.15.0-106-generic'\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/main.o\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/noise.o\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/device.o\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/peer.o\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/timers.o\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/queueing.o\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/send.o\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/receive.o\r\n CC [M] \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/socket.o\r\nIn file included from <command-line>:0:0:\r\n\/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/socket.c: In function \u2018send6\u2019:\r\n\/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/compat\/compat.h:102:42: error: \u2018const struct ipv6_stub\u2019 has no member named \u2018ipv6_dst_lookup\u2019; did you mean \u2018ipv6_dst_lookup_flow\u2019?\r\n #define ipv6_dst_lookup_flow(a, b, c, d) ipv6_dst_lookup(a, b, &dst, c) + (void *)0 ?: dst\r\n ^\r\n\/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/socket.c:139:20: note: in expansion of macro \u2018ipv6_dst_lookup_flow\u2019\r\n dst = ipv6_stub->ipv6_dst_lookup_flow(sock_net(sock), sock, &fl,\r\n ^~~~~~~~~~~~~~~~~~~~\r\nscripts\/Makefile.build:330: recipe for target '\/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/socket.o' failed\r\nmake[1]: *** [\/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/socket.o] Error 1\r\nMakefile:1577: recipe for target '_module_\/var\/lib\/dkms\/wireguard\/1.0.20200520\/build' failed\r\nmake: *** [_module_\/var\/lib\/dkms\/wireguard\/1.0.20200520\/build] Error 2\r\nmake: Leaving directory '\/usr\/src\/linux-headers-4.15.0-106-generic'<\/pre>\nwollte ich pr\u00fcfen, ob ich um den Bug herumkomme, wenn ich den Server mit dem alten Kernel starte.<\/p>\n
Ich dachte, das geht so:<\/p>\n
Ein<\/p>\n
grub-mkconfig | grep -E 'submenu |menuentry '<\/pre>\nliefert den Men\u00fceintrag f\u00fcr den \u00e4lteren Kernel<\/p>\n
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-18a21bc3-6dd4-4d7a-a538-c7d935a00a63' {\r\nsubmenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-18a21bc3-6dd4-4d7a-a538-c7d935a00a63' {\r\n menuentry 'Ubuntu, with Linux 4.15.0-106-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-106-generic-advanced-18a21bc3-6dd4-4d7a-a538-c7d935a00a63' {\r\n menuentry 'Ubuntu, with Linux 4.15.0-106-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-106-generic-recovery-18a21bc3-6dd4-4d7a-a538-c7d935a00a63' {\r\nFound linux image: \/boot\/vmlinuz-4.15.0-101-generic\r\nFound initrd image: \/boot\/initrd.img-4.15.0-101-generic\r\n menuentry 'Ubuntu, with Linux 4.15.0-101-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-101-generic-advanced-18a21bc3-6dd4-4d7a-a538-c7d935a00a63' {\r\n menuentry 'Ubuntu, with Linux 4.15.0-101-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.15.0-101-generic-recovery-18a21bc3-6dd4-4d7a-a538-c7d935a00a63' {<\/pre>\nder dann beim Boot via \/etc\/default\/grub<\/em> (vorher wegsichern!) ausgew\u00e4hlt wird<\/p>\n
GRUB_DEFAULT=\"Advanced options for Ubuntu>Ubuntu, with Linux 4.15.0-101-generic\"<\/pre>\nnachdem ein<\/p>\n
update-grub<\/pre>\nfehlerfrei durchl\u00e4uft.<\/p>\n
Doof gedacht: wireguard-dkms<\/em> baut nat\u00fcrlich trotzdem f\u00fcr den neueren Kernel. Weil? Weil er da ist. So simpel.<\/p>\n
Das Ergebnis ist also das gleiche wie oben: wireguard-dkms<\/em> f\u00e4llt beim Modulbau auf die Nase – obwohl der Server mit dem \u00e4lteren Kernel l\u00e4uft.<\/p>\n
Eigentlich total klar – aber die Finger auf den Tasten sind manchmal schneller als das Hirn dazu.<\/p>\n
Einfacher – und dazu noch fehlerfreier bei den Nacharbeiten mit DKMS zu handhaben – ist ein simpler apt-get purge<\/em> auf den neueren Kernel.<\/p>\n
apt-get purge linux-image-4.15.0-106-generic\r\napt-get clean ; apt-get autoremove<\/pre>\nDann evtl. noch die alten \/etc\/default\/grub<\/em> Inhalte wiederherstellen (falls mensch so bl\u00f6d wie ich war), ein update-grub<\/em> und nach einem Neustart ist wireguard<\/em> wieder brav am Start.<\/p>\n
Update<\/h2>\n
Was hier bez\u00fcglich Wireguard wunderbar funktioniert hat:<\/p>\n
apt-get install --install-recommends linux-generic-hwe-18.04\r\napt-get install --reinstall wireguard-dkms wireguard-tools linux-headers-$(uname -r)<\/pre>\nIch hoffe, das h\u00e4lt nun eine Weile.<\/p>\n","protected":false},"excerpt":{"rendered":"
Weil wireguard mit dem heute gekommenen Kernel f\u00fcr Ubuntu 18.04 nicht durch den Compiler ging Unpacking wireguard-dkms (1.0.20200520-0ppa1~18.04) over (1.0.20200520-0ppa1~18.04) … Setting up wireguard-dkms (1.0.20200520-0ppa1~18.04) … Loading new wireguard-1.0.20200520 DKMS files… Building for 4.15.0-106-generic Building initial module for 4.15.0-106-generic Error! Bad return status for module build on kernel: 4.15.0-106-generic (x86_64) Consult \/var\/lib\/dkms\/wireguard\/1.0.20200520\/build\/make.log for more information. […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,5,18],"tags":[315,612],"class_list":["post-5446","post","type-post","status-publish","format-standard","hentry","category-familie","category-linux","category-memo","tag-kernel","tag-wireguard"],"_links":{"self":[{"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=\/wp\/v2\/posts\/5446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5446"}],"version-history":[{"count":10,"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=\/wp\/v2\/posts\/5446\/revisions"}],"predecessor-version":[{"id":5456,"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=\/wp\/v2\/posts\/5446\/revisions\/5456"}],"wp:attachment":[{"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bdjl.de\/localhost\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}