You are not logged in.

Pages: 1

#1 2021-05-28 12:51:32

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,322
Website

Kernel panic when connecting with WireGuard on linux-zen-5.12.7.zen1-1

After the update to linux-zen-5.12.7.zen1-1, I can no longer connect to our company's WireGuard network.
As soon as I establish the connection using networkmanager-wireguard, the system freezes and the caps-lock LED starts blinking.
I tried to capture dmesg -w but the file I tee'd into is empty, since the system probably did not sync after the panic.
What I saw last was wg-quick setting up the routing tables. No kernel dumps or traces.
I'll try a downgrade and report back. If you know how I could get any further debug info, let me know.

Update:
So, linux-zen-5.12.6.zen1-1 panics as well. The latest version that works is linux-zen-5.12.5.zen1-1.

Last edited by schard (2021-05-28 13:05:19)

Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#2 2021-05-28 19:15:24

zomzom
Member
Registered: 2019-04-04
Posts: 2

Re: Kernel panic when connecting with WireGuard on linux-zen-5.12.7.zen1-1

I just tried it, between two machines of mine (both 5.12.6), and it seems to work. For context, here is my current installed version of wireguard; and I do not use networkmanager-wireguard

>>> yay -Qi wireguard-dkms
Name            : wireguard-dkms
Version         : 1.0.20210424-2

I could update it to another version and try again, if you wish. This could help to nail down what is causing the issue.

Offline

#3 2021-05-28 19:25:10

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,322
Website

Re: Kernel panic when connecting with WireGuard on linux-zen-5.12.7.zen1-1

Hm. I'm not using wireguard-dkms but the built-in version of the respecive kernels. Do you use the ZEN kernel?

Last edited by schard (2021-05-28 19:28:16)

Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#4 2021-05-28 19:31:45

zomzom
Member
Registered: 2019-04-04
Posts: 2

Re: Kernel panic when connecting with WireGuard on linux-zen-5.12.7.zen1-1

Yes I am using zen as well ( 5.12.6-zen1-1-zen )—I do not even recall why I installed the dkms version back in the day. Wireguard was still fairly new so perhaps no package was available for the zen kernel at the time, but I am not fully sure.

Offline

#5 2021-05-28 20:17:50

loqs
Member
Registered: 2014-03-06
Posts: 18,492

Re: Kernel panic when connecting with WireGuard on linux-zen-5.12.7.zen1-1

Not seeing much network related in 5.12.6 https://cdn.kernel.org/pub/linux/kernel … Log-5.12.6
Can you reproduce the issue not using the zen kernel?

Offline

#6 2021-05-29 13:18:33

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,322
Website

Re: Kernel panic when connecting with WireGuard on linux-zen-5.12.7.zen1-1

linux-5.12.7.arch1-1 panics as well.
linux-lts-5.10.41-1 works fine.
Here's the connection log from linux-lts.5.10.41-1:

-- Journal begins at Sun 2021-01-24 18:17:04 CET. --
Mai 29 15:15:26 envy systemd-timesyncd[500]: Initial synchronization to time server [2001:4ba0:ffa4:1ce::]:123 (2.arch.pool.ntp.org).
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.0311] audit: op="connection-activate" uuid="911da7f1-1363-4b32-873e-6e0989c1c70b" name="HOMEINFO" pid=1128 uid=1000 result="success"
Mai 29 15:15:30 envy audit[599]: USYS_CONFIG pid=599 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=911da7f1-1363-4b32-873e-6e0989c1c70b name="HOMEINFO" pid=1128 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Mai 29 15:15:30 envy kernel: audit: type=1111 audit(1622294130.025:96): pid=599 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=911da7f1-1363-4b32-873e-6e0989c1c70b name="HOMEINFO" pid=1128 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.0402] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",0]: Started the VPN service, PID 1743
Mai 29 15:15:30 envy kernel: tun: Universal TUN/TAP device driver, 1.6
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.0638] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",0]: Saw the service appear; activating connection
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip link add HOMEINFO type wireguard
Mai 29 15:15:30 envy kernel: wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
Mai 29 15:15:30 envy kernel: wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
Mai 29 15:15:30 envy NetworkManager[1748]: [#] wg setconf HOMEINFO /dev/fd/63
Mai 29 15:15:30 envy systemd-udevd[1746]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Mai 29 15:15:30 envy systemd-udevd[1746]: Using default interface naming scheme 'v247'.
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.1189] manager: (HOMEINFO): new WireGuard device (/org/freedesktop/NetworkManager/Devices/5)
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip -4 address add 10.200.200.4/32 dev HOMEINFO
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip link set mtu 1420 up dev HOMEINFO
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.2987] device (HOMEINFO): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3014] device (HOMEINFO): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3022] device (HOMEINFO): Activation: starting connection 'HOMEINFO' (abdf3b46-277e-400c-b239-afb05c60371f)
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3024] device (HOMEINFO): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3028] device (HOMEINFO): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3031] device (HOMEINFO): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3033] device (HOMEINFO): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mai 29 15:15:30 envy NetworkManager[1748]: [#] wg set HOMEINFO fwmark 51820
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip -6 route add ::/0 dev HOMEINFO table 51820
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip -6 rule add not fwmark 51820 table 51820
Mai 29 15:15:30 envy dbus-daemon[505]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.5' (uid=0 pid=599 comm="/usr/bin/NetworkManager --no-daemon ")
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip -6 rule add table main suppress_prefixlength 0
Mai 29 15:15:30 envy systemd[1]: Starting Network Manager Script Dispatcher Service...
Mai 29 15:15:30 envy NetworkManager[1748]: [#] nft -f /dev/fd/63
Mai 29 15:15:30 envy audit[1800]: NETFILTER_CFG table=wg-quick-HOMEINFO:5;?:0 family=10 entries=3 op=nft_register_table pid=1800 comm="nft"
Mai 29 15:15:30 envy audit[1800]: NETFILTER_CFG table=wg-quick-HOMEINFO:5;preraw:1 family=10 entries=0 op=nft_register_chain pid=1800 comm="nft"
Mai 29 15:15:30 envy audit[1800]: NETFILTER_CFG table=wg-quick-HOMEINFO:5;premangle:2 family=10 entries=1 op=nft_register_chain pid=1800 comm="nft"
Mai 29 15:15:30 envy audit[1800]: NETFILTER_CFG table=wg-quick-HOMEINFO:5;postmangle:3 family=10 entries=1 op=nft_register_chain pid=1800 comm="nft"
Mai 29 15:15:30 envy audit[1800]: NETFILTER_CFG table=wg-quick-HOMEINFO:5;postmangle:3 family=10 entries=4 op=nft_register_rule pid=1800 comm="nft"
Mai 29 15:15:30 envy audit[1800]: NETFILTER_CFG table=wg-quick-HOMEINFO:5;premangle:2 family=10 entries=5 op=nft_register_rule pid=1800 comm="nft"
Mai 29 15:15:30 envy audit[1800]: NETFILTER_CFG table=?:0;?:0 family=0 entries=3 op=nft_register_gen pid=1800 comm="nft"
Mai 29 15:15:30 envy dbus-daemon[505]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mai 29 15:15:30 envy systemd[1]: Started Network Manager Script Dispatcher Service.
Mai 29 15:15:30 envy audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3224] device (HOMEINFO): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3226] device (HOMEINFO): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip -4 route add 0.0.0.0/0 dev HOMEINFO table 51820
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.3239] device (HOMEINFO): Activation: successful, device activated.
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip -4 rule add not fwmark 51820 table 51820
Mai 29 15:15:30 envy NetworkManager[1748]: [#] ip -4 rule add table main suppress_prefixlength 0
Mai 29 15:15:30 envy kernel: audit: type=1325 audit(1622294130.308:97): table=wg-quick-HOMEINFO:5;?:0 family=10 entries=3 op=nft_register_table pid=1800 comm="nft"
Mai 29 15:15:30 envy kernel: audit: type=1325 audit(1622294130.308:97): table=wg-quick-HOMEINFO:5;preraw:1 family=10 entries=0 op=nft_register_chain pid=1800 comm="nft"
Mai 29 15:15:30 envy kernel: audit: type=1325 audit(1622294130.308:97): table=wg-quick-HOMEINFO:5;premangle:2 family=10 entries=1 op=nft_register_chain pid=1800 comm="nft"
Mai 29 15:15:30 envy kernel: audit: type=1325 audit(1622294130.308:97): table=wg-quick-HOMEINFO:5;postmangle:3 family=10 entries=1 op=nft_register_chain pid=1800 comm="nft"
Mai 29 15:15:30 envy kernel: audit: type=1325 audit(1622294130.308:97): table=wg-quick-HOMEINFO:5;postmangle:3 family=10 entries=4 op=nft_register_rule pid=1800 comm="nft"
Mai 29 15:15:30 envy kernel: audit: type=1325 audit(1622294130.308:97): table=wg-quick-HOMEINFO:5;premangle:2 family=10 entries=5 op=nft_register_rule pid=1800 comm="nft"
Mai 29 15:15:30 envy kernel: audit: type=1325 audit(1622294130.308:97): table=?:0;?:0 family=0 entries=3 op=nft_register_gen pid=1800 comm="nft"
Mai 29 15:15:30 envy kernel: audit: type=1130 audit(1622294130.308:98): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mai 29 15:15:30 envy NetworkManager[1748]: [#] sysctl -q net.ipv4.conf.all.src_valid_mark=1
Mai 29 15:15:30 envy NetworkManager[1748]: [#] nft -f /dev/fd/63
Mai 29 15:15:30 envy audit[1811]: NETFILTER_CFG table=wg-quick-HOMEINFO:7;?:0 family=2 entries=3 op=nft_register_table pid=1811 comm="nft"
Mai 29 15:15:30 envy audit[1811]: NETFILTER_CFG table=wg-quick-HOMEINFO:7;preraw:1 family=2 entries=1 op=nft_register_chain pid=1811 comm="nft"
Mai 29 15:15:30 envy audit[1811]: NETFILTER_CFG table=wg-quick-HOMEINFO:7;premangle:2 family=2 entries=1 op=nft_register_chain pid=1811 comm="nft"
Mai 29 15:15:30 envy audit[1811]: NETFILTER_CFG table=wg-quick-HOMEINFO:7;postmangle:3 family=2 entries=1 op=nft_register_chain pid=1811 comm="nft"
Mai 29 15:15:30 envy audit[1811]: NETFILTER_CFG table=wg-quick-HOMEINFO:7;preraw:1 family=2 entries=4 op=nft_register_rule pid=1811 comm="nft"
Mai 29 15:15:30 envy audit[1811]: NETFILTER_CFG table=wg-quick-HOMEINFO:7;postmangle:3 family=2 entries=5 op=nft_register_rule pid=1811 comm="nft"
Mai 29 15:15:30 envy audit[1811]: NETFILTER_CFG table=wg-quick-HOMEINFO:7;premangle:2 family=2 entries=6 op=nft_register_rule pid=1811 comm="nft"
Mai 29 15:15:30 envy audit[1811]: NETFILTER_CFG table=?:0;?:0 family=0 entries=4 op=nft_register_gen pid=1811 comm="nft"
Mai 29 15:15:30 envy NetworkManager[1748]: [#] /usr/bin/ip route flush table 51820; /usr/bin/ip -6 route flush table 51820
Mai 29 15:15:30 envy kernel: audit: type=1325 audit(1622294130.318:99): table=wg-quick-HOMEINFO:7;?:0 family=2 entries=3 op=nft_register_table pid=1811 comm="nft"
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4087] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",0]: VPN plugin: state changed: starting (3)
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4087] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",0]: VPN connection: (ConnectInteractive) reply received
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4089] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",0]: VPN connection: (IP Config Get) reply received.
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4092] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: VPN connection: (IP4 Config Get) reply received
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4096] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data: Tunnel Device: "HOMEINFO"
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4096] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data: IPv4 configuration:
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4097] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data:   Internal Address: 10.200.200.4
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4097] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data:   Internal Prefix: 32
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4097] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data:   Internal Point-to-Point Address: 10.200.200.4
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4097] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data:   Static Route: 10.200.200.0/24   Next Hop: 10.200.200.254
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4097] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data:   Static Route: 10.10.0.0/16   Next Hop: 10.10.255.254
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4097] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data:   Static Route: 10.8.0.0/16   Next Hop: 10.8.0.1
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4098] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data:   Internal DNS: 10.200.200.254
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4098] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data:   DNS Domain: '(none)'
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4098] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: Data: No IPv6 configuration
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4098] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: VPN plugin: state changed: started (4)
Mai 29 15:15:30 envy NetworkManager[599]: <info>  [1622294130.4119] vpn-connection[0x562cb72c40b0,911da7f1-1363-4b32-873e-6e0989c1c70b,"HOMEINFO",3:(HOMEINFO)]: VPN connection: (IP Config Get) complete
Mai 29 15:15:35 envy systemd[1]: systemd-localed.service: Deactivated successfully.
Mai 29 15:15:35 envy audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mai 29 15:15:35 envy kernel: kauditd_printk_skb: 7 callbacks suppressed
Mai 29 15:15:35 envy kernel: audit: type=1131 audit(1622294135.606:100): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mai 29 15:15:35 envy systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Mai 29 15:15:35 envy audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mai 29 15:15:35 envy kernel: audit: type=1131 audit(1622294135.626:101): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mai 29 15:15:36 envy audit: BPF prog-id=27 op=UNLOAD
Mai 29 15:15:36 envy audit: BPF prog-id=26 op=UNLOAD
Mai 29 15:15:36 envy audit: BPF prog-id=25 op=UNLOAD
Mai 29 15:15:36 envy kernel: audit: type=1334 audit(1622294136.138:102): prog-id=27 op=UNLOAD
Mai 29 15:15:36 envy kernel: audit: type=1334 audit(1622294136.138:103): prog-id=26 op=UNLOAD
Mai 29 15:15:36 envy kernel: audit: type=1334 audit(1622294136.138:104): prog-id=25 op=UNLOAD
Mai 29 15:15:36 envy audit: BPF prog-id=23 op=UNLOAD
Mai 29 15:15:36 envy audit: BPF prog-id=22 op=UNLOAD
Mai 29 15:15:36 envy audit: BPF prog-id=21 op=UNLOAD
Mai 29 15:15:36 envy kernel: audit: type=1334 audit(1622294136.490:105): prog-id=23 op=UNLOAD
Mai 29 15:15:36 envy kernel: audit: type=1334 audit(1622294136.490:106): prog-id=22 op=UNLOAD
Mai 29 15:15:36 envy kernel: audit: type=1334 audit(1622294136.490:107): prog-id=21 op=UNLOAD
^C

Okay, so about six minutes after I established the connection above under linux-lts, the system panicked again,
Freeze frame + Caps lock LED blinking. WTF is going on here?

Update
When I use wg-quick directly (not networkmanager-wireguard), the system does not panic with any kernel.
So this issue is probably NetworkManager-related.
It still confuses me, why it works with older kernels.

Update 2
I uninstalled networkmanager-wireguard-git and tried to use nmcli directly to connect with the WireGuard network [1][2].
This also results in the kernel panic.
So the issue seems to be a problem with NetworkManager and the latest kernels.

Update 3
Now the system also froze shortly after I connected with wg-quick and set-up DNS in /etc/resolv.conf
I am at a loss here. Maybe it's something DNS related?

Update 4
I can confirm that it's WireGuard+DNS related.
When I connect via wg-quick and SSH via the intranet onto one of our digital signage systems, it works without any issues.
As soon as I add our intranet DNS server to /etc/resolv.conf and connect onto the same system now by its host name instead of its IP address (i.e. trigger DNS resolution), the kernel panic occurs immediately.
Any hints on how I can debug this further are appreciated.

[1] https://wiki.archlinux.org/title/WireGu … orkManager
[2] https://blogs.gnome.org/thaller/2019/03 … rkmanager/

Last edited by schard (2021-05-29 14:21:14)

Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#7 2021-05-29 16:20:11

loqs
Member
Registered: 2014-03-06
Posts: 18,492

Re: Kernel panic when connecting with WireGuard on linux-zen-5.12.7.zen1-1

Try the wireguard mailing list.?

Offline

#8 2021-05-31 08:14:47

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,322
Website

Re: Kernel panic when connecting with WireGuard on linux-zen-5.12.7.zen1-1

I found the culprit. A week ago I re-activated my ISP's dual stack option on my IAD, which I had set to IPv4 only due to issues with my home server (which I no longer operate due to my newly rented VPS).
The kernel panic occurs if and only if I use my ISP's native IPv6 setting with DHCPv6 Rapid Commit enabled.
If I disable the DHCPv6 Rapid Commit option or use an IPv4-only setting, the WireGuard connection does no longer cause a kernel panic
I will investigate this further and leave the topic unsolved until I can rule out that this is not a bug in WireGuard.

Update
Sheesh. Sometiemes it seems to work with IPv6 enabled, but just now it crashed again.
The only reliable setting is to disable IPv6 entirely and use IPv4 only.

Last edited by schard (2021-05-31 08:31:15)

Inofficial first vice president of the Rust Evangelism Strike Force

Offline

Pages: 1

Board footer

Powered by FluxBB