Date: Thu, 12 Oct 2023 11:38:54 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 274428] net/wireguard-tools: host service restart kldunloads if_wg, taking it away from VNET jails Message-ID: <bug-274428-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D274428 Bug ID: 274428 Summary: net/wireguard-tools: host service restart kldunloads if_wg, taking it away from VNET jails Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: decke@FreeBSD.org Reporter: vedad@kajtaz.net Assignee: decke@FreeBSD.org Flags: maintainer-feedback?(decke@FreeBSD.org) Hello, Under a setup where wireguard is being used both on the host system and VNET jails, doing a `service wireguard stop` or `service wireguard restart` on t= he host system unconditionally kldunload's if_wg, thus taking away wireguard tunnels from jails (the interfaces simply disappear from jails), requiring a manual wireguard restart in jails (as long as if_wg is loaded). On my own systems, i have simply commented the kldunload bit from the host = rc.d script as a workaround, but that's obviously not the right approach for the port. I actually don't know what the right approach would be. Perhaps an rcvar setting could be introduced to prevent the kldunload? Thanks, Kind regards --=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-274428-7788>