Date: Wed, 12 Dec 2018 11:09:38 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 233955] net/wireguard Occassional hard reboot of FreeBSD 11.2-RELEASE-p6 when used together with setfib(1) Message-ID: <bug-233955-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233955 Bug ID: 233955 Summary: net/wireguard Occassional hard reboot of FreeBSD 11.2-RELEASE-p6 when used together with setfib(1) Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: decke@FreeBSD.org Reporter: manas@bhatnagar.net.in Assignee: decke@FreeBSD.org Flags: maintainer-feedback?(decke@FreeBSD.org) I have experienced multiple hard reboots of my FreeBSD 11.2-RELEASE system which occurs when I try to deactivate a Wireguard interface with wg-quick. This does not always occur, on occasion I am able to activate & deactivate = all interfaces without issue. I am unable to determine which specific conditions cause the hard reboot. After creating/configuring the appropriate keypairs & configuration files, a new interface is created on a specific routing table with: # setfib $FIB route add default $DEFAULTGATEWAY # setfib $FIB wg-quick up wg$N After the connection has been active for a short period, it is deactivated with: # setfib $FIB wg-quick down wg$N The last few messages seen in debug.log prior to the reboot are of the form: Dec 12 10:50:16 $hostname kernel: ifa_maintain_loopback_route: deletion fai= led for interface wg0: 3 The configuration files are simple: [Interface] Address =3D ${PRIVATE_IP}/24 PrivateKey =3D $PRIVATEKEY DNS =3D 127.0.0.1 [Peer] PublicKey =3D $PUBLICKEY Endpoint =3D ${PUBLIC_IP}:51820 AllowedIPs =3D 0.0.0.0/0 PersistentKeepalive =3D 30 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233955-7788>