[Bug 264948] net/wireguard: additional interface does not set RUNNING

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264948

            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 without
problems, a ping to the remote side of wg1 immediatly returns with "No route to
host".

wg0: flags=80c1<UP,RUNNING,NOARP,MULTICAST> metric 0 mtu 1420
        options=80000<LINKSTATE>
        inet 10.33.67.130 netmask 0xffffffff
        groups: wg
        nd6 options=101<PERFORMNUD,NO_DAD>

wg1: flags=8081<UP,NOARP,MULTICAST> metric 0 mtu 1420
        options=80000<LINKSTATE>
        inet 10.33.64.130 netmask 0xffffffff
        groups: wg
        nd6 options=109<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.

-- 
You are receiving this mail because:
You are the assignee for the bug.