Date: Wed, 29 Jun 2022 08:27:38 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 264948] net/wireguard: additional interface does not set RUNNING Message-ID: <bug-264948-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264948 Bug ID: 264948 Summary: net/wireguard: additional interface does not set RUNNING 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: matthias.pfaller@familie-pfaller.de Assignee: decke@FreeBSD.org Flags: maintainer-feedback?(decke@FreeBSD.org) I try to setup a second wireguard interface (wg1). While wg0 is working wit= hout problems, a ping to the remote side of wg1 immediatly returns with "No rout= e to host". wg0: flags=3D80c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420 options=3D80000<LINKSTATE> inet 10.33.67.130 netmask 0xffffffff groups: wg nd6 options=3D101<PERFORMNUD,NO_DAD> wg1: flags=3D8081<UP,NOARP,MULTICAST> metric 0 mtu 1420 options=3D80000<LINKSTATE> inet 10.33.64.130 netmask 0xffffffff groups: wg nd6 options=3D109<PERFORMNUD,IFDISABLED,NO_DAD> Why doesn't wg1 have the RUNNING flag set? When I use the wg1 configuration for wg0 (so I have only one wireguard interface) I can ping the remote host. --=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-264948-7788>